CVE-2026-93261 — locking/lockdep: Fix NULL pointer dereference in __lock_set_class()
In the Linux kernel, the following vulnerability has been resolved: locking/lockdep: Fix NULL pointer dereference in __lock_set_class() register_lock_class() can return NULL when the lock class pool is exhausted, graph_lock() fails, or key validation fails. However, __lock_set_class() uses the return value directly in pointer arithmetic without a NULL check: class = register_lock_class(lock, subclass, 0); hlock->class_idx = class - lock_classes; If class is NULL, this computes a wild offset that corrupts hlock->class_idx. The subsequent reacquire_held_locks() call will invoke hlock_class() with this corrupted index, leading to a NULL or out-of-bounds pointer dereference. Add the missing NULL check, consistent with how __lock_acquire() already handles this case at the same call site.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < f6093ff67ea6e347574819ed23e96e0f82a25ffc≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < 59a5c7dd331a3dab48100e1ef8e9bb4f9132a2b2≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < f56e54fd24f05e9de528fcb77f6084f80c8066ce≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < 5c3bff6cf26e6a54fbf8b893a879c32824d2d50d≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < b2113dcd8238bf00ce37a34e67b29cf31d32a545≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < e7c69c6695d84220847cca62a45e879e71e79e9d≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < 9be10f49dfc2e4b472b3a5f346483b67374774b8≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c and < 7577e00b9ab506202b9f1a33de3cc8cc6413a4db and 1 moreversion 2.6.27 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/f56e54fd24f05e9de528fcb77f6084f80c8066ce
- git.kernel.org/stable/c/7577e00b9ab506202b9f1a33de3cc8cc6413a4db
- git.kernel.org/stable/c/f6093ff67ea6e347574819ed23e96e0f82a25ffc
- git.kernel.org/stable/c/e7c69c6695d84220847cca62a45e879e71e79e9d
- git.kernel.org/stable/c/9be10f49dfc2e4b472b3a5f346483b67374774b8
- git.kernel.org/stable/c/5c3bff6cf26e6a54fbf8b893a879c32824d2d50d
- git.kernel.org/stable/c/59a5c7dd331a3dab48100e1ef8e9bb4f9132a2b2
- git.kernel.org/stable/c/b2113dcd8238bf00ce37a34e67b29cf31d32a545
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93261 is "locking/lockdep: Fix NULL pointer dereference in __lock_set_class()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.