GHSA-364X-FFH5-8MMX
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
bpf, cgroup: Fix storage null-ptr-deref after replacing prog
Syzkaller reported a storage null-ptr-deref issue after replacing prog. This occurs in the following scenario: 1. prog A, an empty prog, is attached to a cgrp. 2. prog B uses BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE and calls the bpf_get_local_storage helper. 3. link_update is called to replace prog A with prog B.
The reason is that __cgroup_bpf_replace fails to alloc and assign the required cgrp storage for the incoming replacement prog. Consequently, the new prog inherits an uninit storage, leading to null-ptr-deref panic when kick the new prog.
Fix this by rejecting a link update if new_prog's cgroup storage is incompatible with link->prog.
{
"affected": [],
"aliases": [
"CVE-2026-90250"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:21Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf, cgroup: Fix storage null-ptr-deref after replacing prog\n\nSyzkaller reported a storage null-ptr-deref issue after replacing prog.\nThis occurs in the following scenario:\n1. prog A, an empty prog, is attached to a cgrp.\n2. prog B uses BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE and calls the\n bpf_get_local_storage helper.\n3. link_update is called to replace prog A with prog B.\n\nThe reason is that __cgroup_bpf_replace fails to alloc and assign the\nrequired cgrp storage for the incoming replacement prog. Consequently,\nthe new prog inherits an uninit storage, leading to null-ptr-deref panic\nwhen kick the new prog.\n\nFix this by rejecting a link update if new_prog\u0027s cgroup storage is\nincompatible with link-\u003eprog.",
"id": "GHSA-364x-ffh5-8mmx",
"modified": "2026-09-17T18:31:57Z",
"published": "2026-09-17T18:31:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90250"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/12feca126831556dc7fabe5a3ba28fbd328768b6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1ab3da12061d7ccb099f7e925fa2d865967a316a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3f562c537e9ecf4bc5e206cfffc2cc047f1b7e94"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a033c950f6731be88a7da98604ed78f302f15b80"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.