GHSA-V693-V3PX-MXPC
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
bpf: Preserve pointer spill metadata during half-slot cleanup
__clean_func_state() cleans dead stack slots in 4-byte halves. When the high half of a STACK_SPILL slot is dead and the low half remains live, cleanup converts the live low half to STACK_MISC or STACK_ZERO and clears the saved spilled_ptr metadata.
That conversion is safe only for scalar spills. For a pointer spill, this metadata clear lets a later 32-bit fill from the still-live half avoid the normal non-scalar register-fill check and be treated as an ordinary scalar stack read.
Leave non-scalar spill slots intact in this half-live shape. This is conservative for pruning and preserves the existing check_stack_read_fixed_off() rejection path for partial fills from pointer spills.
{
"affected": [],
"aliases": [
"CVE-2026-72426"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:16Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Preserve pointer spill metadata during half-slot cleanup\n\n__clean_func_state() cleans dead stack slots in 4-byte halves. When the\nhigh half of a STACK_SPILL slot is dead and the low half remains live,\ncleanup converts the live low half to STACK_MISC or STACK_ZERO and clears\nthe saved spilled_ptr metadata.\n\nThat conversion is safe only for scalar spills. For a pointer spill, this\nmetadata clear lets a later 32-bit fill from the still-live half avoid the\nnormal non-scalar register-fill check and be treated as an ordinary scalar\nstack read.\n\nLeave non-scalar spill slots intact in this half-live shape. This is\nconservative for pruning and preserves the existing\ncheck_stack_read_fixed_off() rejection path for partial fills from pointer\nspills.",
"id": "GHSA-v693-v3px-mxpc",
"modified": "2026-08-17T06:33:29Z",
"published": "2026-08-15T06:32:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72426"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0f9278b22cda6fd2525049930157b79b4036b4ef"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3a354149bceacadbcf7d7b4766f5ef26a85892ab"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.
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.