locking/rt: Fix the incorrect RCU protection in rt_spin_unlock()
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.
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before af28d801cd2db4cc7378554499bd4a5d84a5517eaffected · git
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before 9d1fcd64ab81200e02b7a6db5eb1da8e244e8289affected · git
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before 3cfaac77b3c32ac3940df28866de263c3f45d24caffected · git
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before 1f0d56d3f1e88f20f6e46109402f8c15d59bac37affected · git
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before 633cadbc0b8323f5cc140a285d2432089dbb534eaffected · git
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before 83f9fb561c1c3917e19f95523dd933c7d30291aaaffected · git
- 0f383b6dc96e976dfbf2721b0bf10bd96103b341 and later · before 89038cc87d80c77e7aa6f42a64b2573b74af339faffected · git
- before 5.15not affected · semver
- 5.15.217 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1f0d56d3f1e88f20f6e46109402f8c15d59bac37 | Vendor (CNA) |
| Linux Linux | 3cfaac77b3c32ac3940df28866de263c3f45d24c | Vendor (CNA) |
| Linux Linux | 633cadbc0b8323f5cc140a285d2432089dbb534e | Vendor (CNA) |
| Linux Linux | 83f9fb561c1c3917e19f95523dd933c7d30291aa | Vendor (CNA) |
| Linux Linux | 89038cc87d80c77e7aa6f42a64b2573b74af339f | Vendor (CNA) |
| Linux Linux | 9d1fcd64ab81200e02b7a6db5eb1da8e244e8289 | Vendor (CNA) |
| Linux Linux | af28d801cd2db4cc7378554499bd4a5d84a5517e | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/1f0d56d3f1e88f20f6e46109402f8c15d59bac37
- git.kernel.org/stable/c/3cfaac77b3c32ac3940df28866de263c3f45d24c
- git.kernel.org/stable/c/633cadbc0b8323f5cc140a285d2432089dbb534e
- git.kernel.org/stable/c/83f9fb561c1c3917e19f95523dd933c7d30291aa
- git.kernel.org/stable/c/89038cc87d80c77e7aa6f42a64b2573b74af339f
- git.kernel.org/stable/c/9d1fcd64ab81200e02b7a6db5eb1da8e244e8289
- git.kernel.org/stable/c/af28d801cd2db4cc7378554499bd4a5d84a5517e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.