Kernel memory corruption via stale LLC wait queue
Published Mar 6, 2024 · Updated Aug 5, 2026
A use-after-free in the LLC socket release path in Linux before 6.8 allows local users with CAP_NET_RAW to crash or corrupt the kernel. The release path omits sock_orphan(), leaving sk_wq pointing into a freed socket inode when queued data completes transmission. Exploitation requires local AF_LLC system calls and CAP_NET_RAW; successful triggering permits kernel memory access, control-flow corruption, or a system panic.
Summary
What happened
A use-after-free in the LLC socket release path in Linux before 6.8 allows local users with CAP_NET_RAW to crash or corrupt the kernel. The release path omits sock_orphan(), leaving sk_wq pointing into a freed socket inode when queued data completes transmission. Exploitation requires local AF_LLC system calls and CAP_NET_RAW; successful triggering permits kernel memory access, control-flow corruption, or a system panic.
The record
- CVE
- CVE-2024-26625
- Published
- Mar 6, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=2.6.35
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <3151051b787f7cd7e3329ea0016eb9113c248812
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <64babb17e8150771c58575d8f93a35c5296b499f
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <6b950c712a9a05cdda4aea7fcb2848766576c11b
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <8e51f084b5716653f19e291ed5f026791d4b3ed4
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <9c333d9891f34cea8af1b229dc754552304c8eee
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <aa2b2eb3934859904c287bf5434647ba72e14c1c
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <d0b5b1f12429df3cd9751ab8b2f53729b77733b7
- Affected versionversion=43815482370c510c569fd18edb57afcb0fa8cab6 <dbc1b89981f9c5360277071d33d7f04a43ffda4a
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
Public exploit references
- syzbot AF_LLC use-after-free reproducerproof of concept · demonstrated
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