Kernel crash via stale LLC send checks
Published Mar 18, 2024 · Updated May 11, 2026
Improper locking in the Linux kernel allows local users to crash the system by racing LLC message sends against bonding changes. llc_ui_sendmsg releases its socket lock while allocating an skb, then reacquires the lock without repeating device checks or reserving Ethernet-header headroom. Exploitation requires local low-privileged access and a changing bonded device; the demonstrated outcome is an skb underflow panic and kernel crash.
Summary
What happened
Improper locking in the Linux kernel allows local users to crash the system by racing LLC message sends against bonding changes. llc_ui_sendmsg releases its socket lock while allocating an skb, then reacquires the lock without repeating device checks or reserving Ethernet-header headroom. Exploitation requires local low-privileged access and a changing bonded device; the demonstrated outcome is an skb underflow panic and kernel crash.
The record
- CVE
- CVE-2024-26636
- Published
- Mar 18, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 18, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <04f2a74b562f3a7498be0399309669f342793d8c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d53b813ff8b177f86f149c2f744442681f720e4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <84e9d10419f6f4f3f3cd8f9aaf44a48719aa4b1b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b643d0defcbacd7fe548bc65c3e4e6f17dc5eb2d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c22044270da68881074fda81a7d34812726cb249
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c451c008f563d56d5e676c9dcafae565fcad84bb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cafd3ad3fe03ef4d6632747be9ee15dc0029db4b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dad555c816a50c6a6a8a86be1f9177673918c647
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
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