Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < f6093ff67ea6e347574819ed23e96e0f82a25ffc
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < 59a5c7dd331a3dab48100e1ef8e9bb4f9132a2b2
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < f56e54fd24f05e9de528fcb77f6084f80c8066ce
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < 5c3bff6cf26e6a54fbf8b893a879c32824d2d50d
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < b2113dcd8238bf00ce37a34e67b29cf31d32a545
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < e7c69c6695d84220847cca62a45e879e71e79e9d
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < 9be10f49dfc2e4b472b3a5f346483b67374774b8
    • affected 64aa348edc617dea17bbd01ddee4e47886d5ec8c – < 7577e00b9ab506202b9f1a33de3cc8cc6413a4db
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93261 badge
[![CVE-2026-93261](https://cveledger.app/badge/CVE-2026-93261.svg)](https://cveledger.app/cve/CVE-2026-93261)

Record last updated .