GHSA-WPC6-X34R-QGJ2
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
dax/kmem: account for partial discontiguous resource upon removal
When dev_dax_kmem_probe() partially succeeds (at least one range is mapped) but a subsequent range fails request_mem_region() or add_memory_driver_managed(), the probe silently continues, ultimately returning success, but with the corresponding range resource NULL'ed out.
dev_dax_kmem_remove() iterates over all dax_device ranges regardless of if the underlying resource exists. When remove_memory() is called later, it returns 0 because the memory was never added which causes dev_dax_kmem_remove() to incorrectly assume the (nonexistent) resource can be removed and attempts cleanup on a NULL pointer.
Fix this by skipping these ranges altogether, noting that these cases are considered success, such that the cleanup is still reached when all actually-added ranges are successfully removed.
{
"affected": [],
"aliases": [
"CVE-2026-74379"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:39Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndax/kmem: account for partial discontiguous resource upon removal\n\nWhen dev_dax_kmem_probe() partially succeeds (at least one range is\nmapped) but a subsequent range fails request_mem_region() or\nadd_memory_driver_managed(), the probe silently continues, ultimately\nreturning success, but with the corresponding range resource NULL\u0027ed out.\n\ndev_dax_kmem_remove() iterates over all dax_device ranges regardless of if\nthe underlying resource exists. When remove_memory() is called later, it\nreturns 0 because the memory was never added which causes\ndev_dax_kmem_remove() to incorrectly assume the (nonexistent) resource can\nbe removed and attempts cleanup on a NULL pointer.\n\nFix this by skipping these ranges altogether, noting that these cases are\nconsidered success, such that the cleanup is still reached when all\nactually-added ranges are successfully removed.",
"id": "GHSA-wpc6-x34r-qgj2",
"modified": "2026-08-15T06:32:31Z",
"published": "2026-08-15T06:32:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74379"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/30ea97affbcce236c57287c82dc6ef7a29c63b76"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/598ed7393a639c7547b28ff3e14db9f1ac37c132"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/799e54c510a03a65a57627018a817838d72f35bd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8aa442cfce79e2d69e72fc8e0c0864ac2971149d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d47b0b8a69a13e06afafa54723f3e8c99b0c788f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ef4fc53898bd6c4d0119cc6d419ebef7f2560f31"
}
],
"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.