CVE-2026-74379
dax/kmem: account for partial discontiguous resource upon removal
Description
In 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.
INFO
Published Date :
Aug. 15, 2026, 6:22 a.m.
Last Modified :
Aug. 15, 2026, 6:22 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-74379
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the latest version.
- Apply the specific patch for the DAX kmem driver.
- Ensure proper resource management in memory drivers.
- Test probe and remove sequences thoroughly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74379.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74379 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74379
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74379 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74379 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 15, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': 'ef4fc53898bd6c4d0119cc6d419ebef7f2560f31', 'versionType': 'git'}, {'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': '5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb', 'versionType': 'git'}, {'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': 'd47b0b8a69a13e06afafa54723f3e8c99b0c788f', 'versionType': 'git'}, {'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': '799e54c510a03a65a57627018a817838d72f35bd', 'versionType': 'git'}, {'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': '598ed7393a639c7547b28ff3e14db9f1ac37c132', 'versionType': 'git'}, {'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': '30ea97affbcce236c57287c82dc6ef7a29c63b76', 'versionType': 'git'}, {'status': 'affected', 'version': '60e93dc097f7f13a16a7e4b75b8803eb2adbb721', 'lessThan': '8aa442cfce79e2d69e72fc8e0c0864ac2971149d', 'versionType': 'git'}], 'programFiles': ['drivers/dax/kmem.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.10'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.10', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.212', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.178', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.145', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.97', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.40', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.5', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/dax/kmem.c'], 'defaultStatus': 'affected'}] Added Description In 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. Added Reference https://git.kernel.org/stable/c/30ea97affbcce236c57287c82dc6ef7a29c63b76 Added Reference https://git.kernel.org/stable/c/598ed7393a639c7547b28ff3e14db9f1ac37c132 Added Reference https://git.kernel.org/stable/c/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb Added Reference https://git.kernel.org/stable/c/799e54c510a03a65a57627018a817838d72f35bd Added Reference https://git.kernel.org/stable/c/8aa442cfce79e2d69e72fc8e0c0864ac2971149d Added Reference https://git.kernel.org/stable/c/d47b0b8a69a13e06afafa54723f3e8c99b0c788f Added Reference https://git.kernel.org/stable/c/ef4fc53898bd6c4d0119cc6d419ebef7f2560f31