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.
Published: 2026-08-15
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The reported kernel defect stems from an incomplete cleanup path in dax/kmem initialization and removal routines. When a DAX device partial probe succeeds, the kernel silently treats the failure of later memory region requests as a success, leaving the corresponding resource pointer NULL. Subsequent device removal then attempts to free a non‑existent region, dereferences the NULL pointer, and crashes the kernel. The crash can be induced by any user capable of creating or manipulating DAX devices, potentially leading to a denial of service on the affected machine. The weakness aligns with improper resource management and null pointer dereference (CWE-476).

Affected Systems

The vulnerability affects the Linux kernel’s dax/kmem subsystem. No specific kernel release range is listed, so any system running an unpatched Linux kernel that supports DAX memory management could be impacted. The affected vendor is the Linux kernel maintainers, and the vulnerability is present in all kernels prior to the fix commit referenced in the advisory.

Risk and Exploitability

The CVSS score is 5.5, EPSS is < 1%, and the vulnerability is not listed in CISA’s KEV catalog, indicating no confirmed widespread exploits. Because the flaw requires the ability to create or control DAX devices, the attack vector is likely local, possibly limited to privileged or low‑privileged users with capability to bind DAX drivers. Nonetheless, a kernel crash can lead to a service interruption and may provide a foothold for further exploitation on systems where the crash can be tuned to elevate privileges. Administrators should treat this as a moderate to high risk until a patch is applied.

Generated by OpenCVE AI on August 22, 2026 at 00:05 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the system kernel to a version that includes the vendor fix for the dev_dax_kmem probe and removal logic.
  • Reboot the machine after the kernel update to ensure the corrected code is loaded into memory.
  • If an immediate kernel upgrade is not possible, disable or unload the dax/kmem driver modules until the patch is applied.
  • Continually monitor kernel logs (e.g., dmesg, /var/log/kern.log) for oops or panic messages that indicate a null‑pointer dereference.

Generated by OpenCVE AI on August 22, 2026 at 00:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Sat, 15 Aug 2026 13:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Sat, 15 Aug 2026 06:15:00 +0000

Type Values Removed Values 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.
Title dax/kmem: account for partial discontiguous resource upon removal
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:18:16.387Z

Reserved: 2026-08-15T05:44:03.890Z

Link: CVE-2026-74379

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:39.703

Modified: 2026-08-17T06:19:32.760

Link: CVE-2026-74379

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-74379 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-22T00:15:05Z

Weaknesses