CVE-2026-64027 (GCVE-0-2026-64027)
Vulnerability from cvelistv5 – Published: 2026-07-19 15:39 – Updated: 2026-08-05 12:38
VLAI
EPSS
VEX
Title
net: shaper: rework the VALID marking (again)
Summary
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.
Severity
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
93954b40f6a4fc43226c01a15b02732f884500f1 , < 2417df5e7bb4184b9d3a2988036bf2c46e594545
(git)
Affected: 93954b40f6a4fc43226c01a15b02732f884500f1 , < 96ea960dd40fd55302e0fd755176f26a95e6a50c (git) Affected: 93954b40f6a4fc43226c01a15b02732f884500f1 , < b8d7519352ba8c6df83259295d4a3bad093cae90 (git) |
guessed | |
| Linux | Linux |
Affected:
6.13
Unaffected: 0 , < 6.13 (semver) Unaffected: 6.18.34 , ≤ 6.18.* (semver) Unaffected: 7.0.11 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"include/net/net_shaper.h",
"net/shaper/shaper.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2417df5e7bb4184b9d3a2988036bf2c46e594545",
"status": "affected",
"version": "93954b40f6a4fc43226c01a15b02732f884500f1",
"versionType": "git"
},
{
"lessThan": "96ea960dd40fd55302e0fd755176f26a95e6a50c",
"status": "affected",
"version": "93954b40f6a4fc43226c01a15b02732f884500f1",
"versionType": "git"
},
{
"lessThan": "b8d7519352ba8c6df83259295d4a3bad093cae90",
"status": "affected",
"version": "93954b40f6a4fc43226c01a15b02732f884500f1",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"include/net/net_shaper.h",
"net/shaper/shaper.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.13"
},
{
"lessThan": "6.13",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.34",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.11",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.34",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0.11",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1",
"versionStartIncluding": "6.13",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: shaper: rework the VALID marking (again)\n\nRecent commit changed the semantics from NOT_VALID to VALID.\nI didn\u0027t realize that the flags are not stored atomically\nwith the entry in XArray. There\u0027s still a race of reader\nobserving a VALID mark for a slot, getting interrupted,\nwriter replacing the entry with a different one, reader\ncontinuing, fetching the entry which is now a different\npointer than the pointer for which VALID was meant.\n\nThe biggest consequence of this is that we may see a UAF\nsince net_shaper_rollback() assumed that entries without\nVALID can be freed without observing RCU.\n\nLooks like the XArray marks are buying us nothing at this\npoint. Let\u0027s convert the code to an explicit valid field.\nThe smp_load_acquire() / smp_store_release() barriers are\nmarginally cleaner."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The vulnerability is reached only through the net-shaper generic netlink API (socket syscall), not via remote packet handling. This matches the kernel guidance for tc/netlink-style configuration subsystems.\nAC:L - The family sets parallel_ops, so an attacker can run concurrent SET/GROUP/DELETE and GET/dump requests to control both sides of the TOCTOU race. No attacker-uncontrollable memory layout or rare timing is required beyond issuing concurrent netlink operations.\nPR:L - Exploitation requires triggering net_shaper_rollback() via SET, GROUP, or DELETE, which are gated by GENL_ADMIN_PERM (CAP_NET_ADMIN). That capability is available to an unprivileged user inside a user network namespace, not only to init-namespace root.\nUI:N - Exploitation is fully programmatic through netlink messages and requires no victim interaction such as mounting a filesystem or opening a file.\nS:U - Impact is kernel heap corruption and privilege escalation within the same kernel; it does not cross a VM, container runtime, or IOMMU security boundary by itself.\nC:H - The commit explicitly identifies a use-after-free; concurrent RCU readers can dereference freed net_shaper objects, enabling arbitrary kernel memory disclosure via UAF exploitation.\nI:H - UAF on heap-allocated net_shaper structures can be leveraged for heap grooming and arbitrary write or control-flow hijack, consistent with standard kernel UAF impact.\nA:H - The UAF can cause kernel oops or panic on freed-object access during lookup, dump, or rollback, and matches kernel guidance that any UAF warrants High availability impact."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:38:22.063Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/2417df5e7bb4184b9d3a2988036bf2c46e594545"
},
{
"url": "https://git.kernel.org/stable/c/96ea960dd40fd55302e0fd755176f26a95e6a50c"
},
{
"url": "https://git.kernel.org/stable/c/b8d7519352ba8c6df83259295d4a3bad093cae90"
}
],
"title": "net: shaper: rework the VALID marking (again)",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-64027",
"datePublished": "2026-07-19T15:39:18.470Z",
"dateReserved": "2026-07-19T07:54:57.028Z",
"dateUpdated": "2026-08-05T12:38:22.063Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-64027",
"date": "2026-10-11",
"epss": "0.00173",
"percentile": "0.062"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"include/net/net_shaper.h",
"net/shaper/shaper.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2417df5e7bb4184b9d3a2988036bf2c46e594545",
"status": "affected",
"version": "93954b40f6a4fc43226c01a15b02732f884500f1",
"versionType": "git"
},
{
"lessThan": "96ea960dd40fd55302e0fd755176f26a95e6a50c",
"status": "affected",
"version": "93954b40f6a4fc43226c01a15b02732f884500f1",
"versionType": "git"
},
{
"lessThan": "b8d7519352ba8c6df83259295d4a3bad093cae90",
"status": "affected",
"version": "93954b40f6a4fc43226c01a15b02732f884500f1",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"include/net/net_shaper.h",
"net/shaper/shaper.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.13"
},
{
"lessThan": "6.13",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.34",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.11",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: shaper: rework the VALID marking (again)\n\nRecent commit changed the semantics from NOT_VALID to VALID.\nI didn\u0027t realize that the flags are not stored atomically\nwith the entry in XArray. There\u0027s still a race of reader\nobserving a VALID mark for a slot, getting interrupted,\nwriter replacing the entry with a different one, reader\ncontinuing, fetching the entry which is now a different\npointer than the pointer for which VALID was meant.\n\nThe biggest consequence of this is that we may see a UAF\nsince net_shaper_rollback() assumed that entries without\nVALID can be freed without observing RCU.\n\nLooks like the XArray marks are buying us nothing at this\npoint. Let\u0027s convert the code to an explicit valid field.\nThe smp_load_acquire() / smp_store_release() barriers are\nmarginally cleaner."
}
],
"id": "CVE-2026-64027",
"lastModified": "2026-07-30T14:59:47.950",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-07-19T16:17:42.777",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2417df5e7bb4184b9d3a2988036bf2c46e594545"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/96ea960dd40fd55302e0fd755176f26a95e6a50c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b8d7519352ba8c6df83259295d4a3bad093cae90"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Awaiting Analysis"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-08-05T14:20:31+00:00",
"cve": "CVE-2026-64027",
"id": "CVE-2026-64027",
"initial_release_date": "2026-07-19T00:00:00+00:00",
"product_status:known_affected": "184",
"product_status:known_not_affected": "91",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: net: shaper: rework the VALID marking (again)",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-64027.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "important",
"current_release_date": "2026-09-15T01:57:06Z",
"cve": "CVE-2026-64027",
"id": "CVE-2026-64027",
"initial_release_date": "2026-07-21T13:01:14Z",
"product_status:known_affected": "29",
"product_status:known_not_affected": "345",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-64027",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-64027.json",
"version": "5"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…