CVE-2026-64027

Last refreshed2026-10-13

Status: UPDATED | Advisory ID: CVE-2026-64027

Key Details

CVE	CVE-2026-64027
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-13
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel
Classified as	CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-64027
CVE	https://www.cve.org/CVERecord?id=CVE-2026-64027

Source

Reference

NVD

CVE