Kernel use-after-free via premature tlclk cleanup
Published Aug 28, 2026 · Updated Aug 28, 2026
Use-after-free in the tlclk driver in affected Linux kernels allows attackers to trigger stale-memory access during module removal. The tlclk_cleanup() path frees alarm_events before blocked readers are fully awakened and before the switchover timer is synchronously deleted, while tlclk_fops lacks an owner reference that prevents unloading during use. Reachability requires tlclk hardware, an open device reader, and concurrent privileged module unload; published material does not establish a crash, memory corruption, or code execution consequence.
Summary
What happened
Use-after-free in the tlclk driver in affected Linux kernels allows attackers to trigger stale-memory access during module removal. The tlclk_cleanup() path frees alarm_events before blocked readers are fully awakened and before the switchover timer is synchronously deleted, while tlclk_fops lacks an owner reference that prevents unloading during use. Reachability requires tlclk hardware, an open device reader, and concurrent privileged module unload; published material does not establish a crash, memory corruption, or code execution consequence.
The record
- CVE
- CVE-2026-80622
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <09d8d2a46a9ec9ff728f3159a174a2ab25dd0f0a
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <166dd1d5265e067459e674c11688919901813ec2
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <3d5e4cc0d9dce79b0429da3134ac7b072ab9009f
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <42223445607a9a5df3cb1c4729abfe3a5085e7ce
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <764723bd67a6c8f53a8d8309211fb039e2ebcf49
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <96902299a22d126ef5eb3f45cd5d8ceea9e6a735
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <bbf003b7794d6ad6f939fdd29f1f1bde8ac554c1
- Affected versionversion=1a80ba88273097933f93b1f40537337416798c70 <c3f0cd76561ae611c2d247ee96dfd559e4197cb7
- Affected versionversion=2.6.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo