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-72069

locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()

Description

In the Linux kernel, the following vulnerability has been resolved: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() rt_spin_unlock() releases the RCU protection before unlocking the lock. That opens the door for the following UAF scenario: T1 T2 spin_lock(&p->lock); rcu_read_lock(); invalidate(p); p = rcu_dereference(ptr); rcu_assign_pointer(ptr, NULL); if (!p) return; spin_unlock(&p->lock); spin_lock(&p->lock) lock(&lock->lock); rcu_read_lock(); kfree_rcu(p); rcu_read_unlock(); .... spin_unlock(&p->lock) rcu_read_unlock(); // Ends grace period rcu_do_batch() kfree(p); UAF -> rt_mutex_cmpxchg_release(&lock->lock...) Regular spinlocks keep preemption disabled accross the unlock operation, which provides full RCU protection, but the RT substitution fails to resemble that. Same applies for the rwlock substitution. Move the rcu_read_unlock() invocation past the unlock operations to match the non-RT semantics. This makes it asymmetric vs. rt_xxx_lock(), but that's harmless as the caller needs to hold RCU read lock across the lock operation. The migrate_enable() call stays before the unlock operation because there is no per CPU operation in the unlock path which would require migration to be kept disabled.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 months 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

CVSS scores of CVE-2026-72069, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.73% · top 45% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < af28d801cd2db4cc7378554499bd4a5d84a5517e
    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < 9d1fcd64ab81200e02b7a6db5eb1da8e244e8289
    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < 3cfaac77b3c32ac3940df28866de263c3f45d24c
    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < 1f0d56d3f1e88f20f6e46109402f8c15d59bac37
    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < 633cadbc0b8323f5cc140a285d2432089dbb534e
    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < 83f9fb561c1c3917e19f95523dd933c7d30291aa
    • affected 0f383b6dc96e976dfbf2721b0bf10bd96103b341 – < 89038cc87d80c77e7aa6f42a64b2573b74af339f
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .