In the Linux kernel, the following vulnerability has been resolved: char: tlclk: fix use-after-free in tlclk_cleanup() This patch impro…
CVE-2026-80622 · published 28 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-80622?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 2.6.15
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
char: tlclk: fix use-after-free in tlclk_cleanup()
This patch improves the module cleanup process in the tlclk driver to
prevent potential use-after-free and race conditions.
Currently, the file_operations structure does not specify the .owner
field, which could allow the module to be unloaded while user-space
processes are still interacting with the device. Additionally, the
tlclk_cleanup() function frees the alarm_events memory before ensuring
that blocked processes in the waitqueue are fully awakened and that the
switchover_timer has completed.
To address these cases, this patch:
- Sets '.owner = THIS_MODULE' in tlclk_fops to safely defer module
unloading while the device is in use.
- Updates tlclk_cleanup() to explicitly wake up all blocked readers
(wake_up_all), properly release hardware I/O regions, and safely
delete the timer (timer_delete_sync) prior to freeing memory.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/09d8d2a46a9ec9ff728f3159a174a2ab25dd0f0a
- git.kernel.org/stable/c/166dd1d5265e067459e674c11688919901813ec2
- git.kernel.org/stable/c/3d5e4cc0d9dce79b0429da3134ac7b072ab9009f
- git.kernel.org/stable/c/42223445607a9a5df3cb1c4729abfe3a5085e7ce
- git.kernel.org/stable/c/764723bd67a6c8f53a8d8309211fb039e2ebcf49
- git.kernel.org/stable/c/96902299a22d126ef5eb3f45cd5d8ceea9e6a735
- git.kernel.org/stable/c/bbf003b7794d6ad6f939fdd29f1f1bde8ac554c1
- git.kernel.org/stable/c/c3f0cd76561ae611c2d247ee96dfd559e4197cb7
Merged from NVD. Last updated 24 Oct 2026. All vulnerabilities · RSS · JSON