In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking (again) Recent commit changed the… (CVE-2026-64027)
In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking (again) Recent commit changed the semantics from NOT_VALID to VALID. I didn't realize that the flags are not stored atomically with the entry in XArray. There's still a race of reader observing a VALID mark for a slot, getting interrupted, writer replacing the entry with a different one, reader continuing, fetching the entry which is now a different pointer than the pointer for which VALID was meant. The biggest consequence of this is that we may see a UAF since net_shaper_rollback() assumed that entries without VALID can be freed without observing RCU. Looks like the XArray marks are buying us nothing at this point. Let's convert the code to an explicit valid field. The smp_load_acquire() / smp_store_release() barriers are marginally cleaner.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-64027 concerns the network shaper's handling of VALID flags in XArray entries. A recent commit changed the semantics of these flags, but failed to account for the non-atomic storage of flags alongside entries, creating a race condition. A reader may see a VALID mark, get interrupted, and then access a different entry replaced by a writer, causing a use-after-free scenario. The root cause is that net_shaper_rollback() frees entries without observing RCU synchronization if the VALID flag is not set. The fix involved replacing the XArray marks with an explicit valid field and using smp_load_acquire() and smp_store_release() memory barriers to ensure proper synchronization.
Potential Impact
The vulnerability can cause use-after-free conditions in the Linux kernel's network shaper code, potentially leading to kernel memory corruption or instability. No known exploits in the wild have been reported. The impact is limited to affected kernel versions and depends on exploitation feasibility, which is not detailed in the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates that a code fix has been implemented to rework the VALID marking and synchronization, but no explicit patch or vendor advisory link is provided. Users should monitor official Linux kernel advisories for updates and apply fixes once available.
In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking (again) Recent commit changed the… (CVE-2026-64027)
Description
In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking (again) Recent commit changed the semantics from NOT_VALID to VALID. I didn't realize that the flags are not stored atomically with the entry in XArray. There's still a race of reader observing a VALID mark for a slot, getting interrupted, writer replacing the entry with a different one, reader continuing, fetching the entry which is now a different pointer than the pointer for which VALID was meant. The biggest consequence of this is that we may see a UAF since net_shaper_rollback() assumed that entries without VALID can be freed without observing RCU. Looks like the XArray marks are buying us nothing at this point. Let's convert the code to an explicit valid field. The smp_load_acquire() / smp_store_release() barriers are marginally cleaner.
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-64027 concerns the network shaper's handling of VALID flags in XArray entries. A recent commit changed the semantics of these flags, but failed to account for the non-atomic storage of flags alongside entries, creating a race condition. A reader may see a VALID mark, get interrupted, and then access a different entry replaced by a writer, causing a use-after-free scenario. The root cause is that net_shaper_rollback() frees entries without observing RCU synchronization if the VALID flag is not set. The fix involved replacing the XArray marks with an explicit valid field and using smp_load_acquire() and smp_store_release() memory barriers to ensure proper synchronization.
Potential Impact
The vulnerability can cause use-after-free conditions in the Linux kernel's network shaper code, potentially leading to kernel memory corruption or instability. No known exploits in the wild have been reported. The impact is limited to affected kernel versions and depends on exploitation feasibility, which is not detailed in the provided data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates that a code fix has been implemented to rework the VALID marking and synchronization, but no explicit patch or vendor advisory link is provided. Users should monitor official Linux kernel advisories for updates and apply fixes once available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p8c9-j99c-x8w3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64027"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912c8a4
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:54:37 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 12
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.