locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.217, 6.1.184, 6.6.148, 6.12.101, 6.18.40, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in af28d801cd2db4cc7378554499bd4a5d84a5517e; From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in 9d1fcd64ab81200e02b7a6db5eb1da8e244e8289; From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in 3cfaac77b3c32ac3940df28866de263c3f45d24c; From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in 1f0d56d3f1e88f20f6e46109402f8c15d59bac37; From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in 633cadbc0b8323f5cc140a285d2432089dbb534e; From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in 83f9fb561c1c3917e19f95523dd933c7d30291aa; From 0f383b6dc96e976dfbf2721b0bf10bd96103b341 · fixed in 89038cc87d80c77e7aa6f42a64b2573b74af339f
- Linux Linux
5.15
- KernelLinux
From 5.15.0 · fixed in 5.15.217; From 5.16.0 · fixed in 6.1.184; From 6.2.0 · fixed in 6.6.148; From 6.7.0 · fixed in 6.12.101; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 7
git.kernel.org
- stable/c/af28d801cd2db4cc7378554499bd4a5d84a5517e
- stable/c/9d1fcd64ab81200e02b7a6db5eb1da8e244e8289
- stable/c/3cfaac77b3c32ac3940df28866de263c3f45d24c
- stable/c/1f0d56d3f1e88f20f6e46109402f8c15d59bac37
- stable/c/633cadbc0b8323f5cc140a285d2432089dbb534e
- stable/c/83f9fb561c1c3917e19f95523dd933c7d30291aa
- stable/c/89038cc87d80c77e7aa6f42a64b2573b74af339f