Kernel crash via unchecked lock-class registration failure
Published Sep 24, 2026 · Updated Sep 24, 2026
NULL pointer dereference in Linux lockdep allows attackers to crash the kernel through a failed lock-class registration. __lock_set_class() subtracts the lock_classes base from a NULL register_lock_class() result, corrupting hlock->class_idx before reacquire_held_locks() dereferences the invalid entry. The published record identifies no attacker-controlled path to exhaust the class pool or cause the other registration failures, so practical reachability is undisclosed.
Summary
What happened
NULL pointer dereference in Linux lockdep allows attackers to crash the kernel through a failed lock-class registration. __lock_set_class() subtracts the lock_classes base from a NULL register_lock_class() result, corrupting hlock->class_idx before reacquire_held_locks() dereferences the invalid entry. The published record identifies no attacker-controlled path to exhaust the class pool or cause the other registration failures, so practical reachability is undisclosed.
The record
- CVE
- CVE-2026-93261
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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.27
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <59a5c7dd331a3dab48100e1ef8e9bb4f9132a2b2
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <5c3bff6cf26e6a54fbf8b893a879c32824d2d50d
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <7577e00b9ab506202b9f1a33de3cc8cc6413a4db
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <9be10f49dfc2e4b472b3a5f346483b67374774b8
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <b2113dcd8238bf00ce37a34e67b29cf31d32a545
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <e7c69c6695d84220847cca62a45e879e71e79e9d
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <f56e54fd24f05e9de528fcb77f6084f80c8066ce
- Affected versionversion=64aa348edc617dea17bbd01ddee4e47886d5ec8c <f6093ff67ea6e347574819ed23e96e0f82a25ffc
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started