GHSA-M447-WF7W-9QP4
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: Fix mmap_lock leak in irq_work path
stack_map_get_build_id_offset() introduced a per-CPU irq_work to defer mmap_read_unlock() from NMI context, and bpf_find_vma() later reused the same mmap_unlock_work. Both callers only check whether the work is busy before taking mmap_lock, so a nested caller can reuse the slot before the first caller queues it. Two read locks may then be acquired while only one deferred unlock runs, leaking a read lock and blocking exit_mmap().
Reserve the per-CPU slot before mmap_read_trylock(). Use the same wrapper in stackmap and bpf_find_vma() so both callers release the reservation on trylock failure. Keep rejecting the slot while the irq_work remains busy. Release it after the irq_work callback unlocks the mm.
{
"affected": [],
"aliases": [
"CVE-2026-90247"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:20Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix mmap_lock leak in irq_work path\n\nstack_map_get_build_id_offset() introduced a per-CPU irq_work to defer\nmmap_read_unlock() from NMI context, and bpf_find_vma() later reused the\nsame mmap_unlock_work. Both callers only check whether the work is busy\nbefore taking mmap_lock, so a nested caller can reuse the slot before the\nfirst caller queues it. Two read locks may then be acquired while only one\ndeferred unlock runs, leaking a read lock and blocking exit_mmap().\n\nReserve the per-CPU slot before mmap_read_trylock(). Use the same wrapper\nin stackmap and bpf_find_vma() so both callers release the reservation on\ntrylock failure. Keep rejecting the slot while the irq_work remains busy.\nRelease it after the irq_work callback unlocks the mm.",
"id": "GHSA-m447-wf7w-9qp4",
"modified": "2026-09-17T18:31:57Z",
"published": "2026-09-17T18:31:57Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90247"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/051f2da26ce377f683b938a3382e0f16d02f3139"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a052ad5edccf5319f50ed955de4368f8318a9f20"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fa9dcacdcdf487f0ffef64bf67622f1caed509f1"
}
],
"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.