Linux Kernel up to 7.1.4 DAX kmem drivers/dax/kmem.c dev_dax_kmem_remove null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.2$0-$5k0.94

Summaryinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 7.1.4. This impacts the function dev_dax_kmem_remove of the file drivers/dax/kmem.c of the component DAX kmem. Executing a manipulation can lead to null pointer dereference. This vulnerability is tracked as CVE-2026-74379. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 7.1.4. This vulnerability affects the function dev_dax_kmem_remove of the file drivers/dax/kmem.c of the component DAX kmem. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability was named CVE-2026-74379 since 08/15/2026. The exploitation appears to be easy. Local access is required to approach this attack. Additional levels of successful authentication are required for exploitation. Technical details are known, but there is no available exploit.

Upgrading to version 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch ef4fc53898bd6c4d0119cc6d419ebef7f2560f31/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb/d47b0b8a69a13e06afafa54723f3e8c99b0c788f/799e54c510a03a65a57627018a817838d72f35bd/598ed7393a639c7547b28ff3e14db9f1ac37c132/30ea97affbcce236c57287c82dc6ef7a29c63b76/8aa442cfce79e2d69e72fc8e0c0864ac2971149d is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.2

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: ef4fc53898bd6c4d0119cc6d419ebef7f2560f31/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb/d47b0b8a69a13e06afafa54723f3e8c99b0c788f/799e54c510a03a65a57627018a817838d72f35bd/598ed7393a639c7547b28ff3e14db9f1ac37c132/30ea97affbcce236c57287c82dc6ef7a29c63b76/8aa442cfce79e2d69e72fc8e0c0864ac2971149d

Timelineinfo

08/15/2026 Advisory disclosed
08/15/2026 +0 days CVE reserved
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-74379 (🔒)
GCVE (CVE): GCVE-0-2026-74379
GCVE (VulDB): GCVE-100-390322

Entryinfo

Created: 08/15/2026 09:56
Changes: 08/15/2026 09:56 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!