CVE-2026-72069

published 15 Aug 2026 · updated 19 Oct 2026

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

9.8CriticalCVSS 9.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 1f0d56d3f1e88f20f6e46109402f8c15d59bac37, Kernel 3cfaac77b3c32ac3940df28866de263c3f45d24c, Kernel 633cadbc0b8323f5cc140a285d2432089dbb534e and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.15, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <1f0d56d3f1e88f20f6e46109402f8c15d59bac37, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <3cfaac77b3c32ac3940df28866de263c3f45d24c, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <633cadbc0b8323f5cc140a285d2432089dbb534e, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <83f9fb561c1c3917e19f95523dd933c7d30291aa, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <89038cc87d80c77e7aa6f42a64b2573b74af339f, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <9d1fcd64ab81200e02b7a6db5eb1da8e244e8289, >=0f383b6dc96e976dfbf2721b0bf10bd96103b341 <af28d801cd2db4cc7378554499bd4a5d84a5517e1f0d56d3f1e88f20f6e46109402f8c15d59bac37, 3cfaac77b3c32ac3940df28866de263c3f45d24c, 633cadbc0b8323f5cc140a285d2432089dbb534e, 83f9fb561c1c3917e19f95523dd933c7d30291aa, 89038cc87d80c77e7aa6f42a64b2573b74af339f, 9d1fcd64ab81200e02b7a6db5eb1da8e244e8289, af28d801cd2db4cc7378554499bd4a5d84a5517e

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-72069 severity on Zeptric[![CVE-2026-72069](https://zeptric.io/badge/cve/CVE-2026-72069.svg)](https://zeptric.io/cve/CVE-2026-72069)