In the Linux kernel, the following vulnerability has been resolved: bpf: Invalidate RCU pointers after final spin unlock In a sleepable BPF program,… (CVE-2026-90317)
A use-after-free vulnerability in the Linux kernel's BPF subsystem was resolved. The issue occurs in sleepable BPF programs where a spin lock provides RCU protection for a kernel pointer, but the verifier incorrectly leaves the pointer valid after the final spin unlock. This can lead to use of a freed object, causing potential system compromise. The fix involves tracking RCU-protected contexts and invalidating pointers only when leaving the final such context.
AI Analysis
Technical Summary
CVE-2026-90317 addresses a use-after-free vulnerability in the Linux kernel's BPF implementation. In sleepable BPF programs, a spin lock can be the sole RCU protection for a kernel pointer (kptr). The final bpf_spin_unlock() call ends this protection, but the verifier erroneously keeps the pointer valid. Consequently, another CPU may free the object before the pointer is used, leading to a use-after-free condition demonstrated by a capability-limited proof of concept triggering a task_struct use-after-free in __bpf_get_task_stack(). The patch records whether the program is in an RCU-protected context before releasing the lock and invalidates RCU-protected pointers only when the unlock leaves the final such context, preserving valid pointers in other cases.
Potential Impact
This vulnerability allows a local attacker with limited privileges to cause a use-after-free in kernel memory, potentially leading to arbitrary code execution or system compromise. The CVSS score of 7.8 reflects high impact on confidentiality, integrity, and availability. However, exploitation requires local access and involves kernel BPF programs.
Mitigation Recommendations
A fix is available that properly invalidates RCU pointers after the final spin unlock in sleepable BPF programs. Users should apply the official Linux kernel patch that addresses this issue. No additional mitigation is indicated by the vendor advisory.
In the Linux kernel, the following vulnerability has been resolved: bpf: Invalidate RCU pointers after final spin unlock In a sleepable BPF program,… (CVE-2026-90317)
Description
A use-after-free vulnerability in the Linux kernel's BPF subsystem was resolved. The issue occurs in sleepable BPF programs where a spin lock provides RCU protection for a kernel pointer, but the verifier incorrectly leaves the pointer valid after the final spin unlock. This can lead to use of a freed object, causing potential system compromise. The fix involves tracking RCU-protected contexts and invalidating pointers only when leaving the final such context.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-90317 addresses a use-after-free vulnerability in the Linux kernel's BPF implementation. In sleepable BPF programs, a spin lock can be the sole RCU protection for a kernel pointer (kptr). The final bpf_spin_unlock() call ends this protection, but the verifier erroneously keeps the pointer valid. Consequently, another CPU may free the object before the pointer is used, leading to a use-after-free condition demonstrated by a capability-limited proof of concept triggering a task_struct use-after-free in __bpf_get_task_stack(). The patch records whether the program is in an RCU-protected context before releasing the lock and invalidates RCU-protected pointers only when the unlock leaves the final such context, preserving valid pointers in other cases.
Potential Impact
This vulnerability allows a local attacker with limited privileges to cause a use-after-free in kernel memory, potentially leading to arbitrary code execution or system compromise. The CVSS score of 7.8 reflects high impact on confidentiality, integrity, and availability. However, exploitation requires local access and involves kernel BPF programs.
Mitigation Recommendations
A fix is available that properly invalidates RCU pointers after the final spin unlock in sleepable BPF programs. Users should apply the official Linux kernel patch that addresses this issue. No additional mitigation is indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6jx2-qmxh-94v4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-90317"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade52155bf5e2cf5edc177
Added to database: 09/19/2026, 01:28:01 UTC
Last enriched: 09/19/2026, 01:49:18 UTC
Last updated: 09/19/2026, 04:01:25 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.