CVE-2026-74379

UnknownEPSS 0.17%

Last modified

CVE-2026-74379 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

7.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < ef4fc53898bd6c4d0119cc6d419ebef7f2560f31; >= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < 5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb; >= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < d47b0b8a69a13e06afafa54723f3e8c99b0c788f; >= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < 799e54c510a03a65a57627018a817838d72f35bd; >= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < 598ed7393a639c7547b28ff3e14db9f1ac37c132; >= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < 30ea97affbcce236c57287c82dc6ef7a29c63b76; >= 60e93dc097f7f13a16a7e4b75b8803eb2adbb721, < 8aa442cfce79e2d69e72fc8e0c0864ac2971149d
LinuxLinux5.10

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74379?
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.
How severe is CVE-2026-74379?
Severity scoring for CVE-2026-74379 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74379?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-74379?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST