Skip to main content
VulnerabilityPublished Updated

CVE-2026-93261: Linux kernel · locking/lockdep: Fix NULL pointer dereference in __lock_set_class()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f6093ff67ea6e347574819ed23e96e0f82a25ffc : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f6093ff67ea6e347574819ed23e96e0f82a25ffc, f56e54fd24f05e9de528fcb77f6084f80c8066ce, e7c69c6695d84220847cca62a45e879e71e79e9d +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c, < f6093ff67ea6e347574819ed23e96e0f82a25ffc
Fixed in
  • f6093ff67ea6e347574819ed23e96e0f82a25ffc
LinuxLinuxAffected
  • ≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c, < f56e54fd24f05e9de528fcb77f6084f80c8066ce
Fixed in
  • f56e54fd24f05e9de528fcb77f6084f80c8066ce
LinuxLinuxAffected
  • ≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c, < e7c69c6695d84220847cca62a45e879e71e79e9d
Fixed in
  • e7c69c6695d84220847cca62a45e879e71e79e9d
LinuxLinuxAffected
  • ≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c, < b2113dcd8238bf00ce37a34e67b29cf31d32a545
Fixed in
  • b2113dcd8238bf00ce37a34e67b29cf31d32a545
LinuxLinuxAffected
  • ≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c, < 7577e00b9ab506202b9f1a33de3cc8cc6413a4db
Fixed in
  • 7577e00b9ab506202b9f1a33de3cc8cc6413a4db
LinuxLinuxAffected
  • ≥ 64aa348edc617dea17bbd01ddee4e47886d5ec8c, < 59a5c7dd331a3dab48100e1ef8e9bb4f9132a2b2
Fixed in
  • 59a5c7dd331a3dab48100e1ef8e9bb4f9132a2b2

Description

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.

References

Community reviews

Loading reviews…