Not ratedCVE-2026-74379

    Linux Kernel: security vulnerability (CVE-2026-74379)

    Published Last modified Sources: Ubuntu, SUSE, BSI, CVE.org

    Share

    What is affected, what to do

    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.

    Update Linux Kernel to version 5.15.212, Linux Kernel to version 6.1.178, Linux Kernel to version 6.6.145.

    Affected
    • Linux Kernel lt 5.10..5.15.212
    • Linux Kernel lt 5.16..6.1.178
    • Linux Kernel lt 6.2..6.6.145
    • Linux Kernel lt 6.7..6.12.97
    • Linux Kernel lt 6.13..6.18.40
    • Linux Kernel lt 6.19..7.1.5
    Fixed in
    • Linux Kernel 5.15.212
    • Linux Kernel 6.1.178
    • Linux Kernel 6.6.145
    • Linux Kernel 6.12.97
    • Linux Kernel 6.18.40
    • Linux Kernel 7.1.5
    • Linux Kernel 7.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    —

    Priority

    No value is available for this vulnerability.

    —

    CVSS v3

    No value is available for this vulnerability.

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 6.7

    Show all metrics
    Severity
    Not rated
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    23.19 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    6.7
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: Ubuntu Security Notices, suse_csaf, BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 6.7 – < 6.12.97
    • 6.19 – < 7.1.5
    • 6.2 – < 6.6.145
    • 5.10 – < 5.15.212
    • —
    • 6.13 – < 6.18.40
    • 5.16 – < 6.1.178
    • 6.12.97
    • 7.1.5
    • 6.6.145
    • 5.15.212
    • 7.2
    • 6.18.40
    • 6.1.178

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxubuntulinuxnoble
    Linuxubuntulinuxresolute
    Linuxubuntulinux-awsnoble
    Linuxubuntulinux-awsresolute
    Linuxubuntulinux-aws-7.0noble
    Linuxubuntulinux-aws-fipsnoble
    Linuxubuntulinux-azurenoble
    Linuxubuntulinux-azureresolute
    Linuxubuntulinux-azure-7.0noble
    Linuxubuntulinux-azure-fdenoble
    Linuxubuntulinux-azure-fderesolute
    Linuxubuntulinux-azure-fde-7.0noble
    Linuxubuntulinux-azure-fipsnoble
    Linuxubuntulinux-fipsnoble
    Linuxubuntulinux-gcpnoble
    Linuxubuntulinux-gcpresolute
    Linuxubuntulinux-gcp-7.0noble
    Linuxubuntulinux-gcp-fipsnoble
    Linuxubuntulinux-gkenoble
    Linuxubuntulinux-gkeresolute
    Linuxubuntulinux-gkeopnoble
    Linuxubuntulinux-hwe-7.0noble
    Linuxubuntulinux-ibmnoble
    Linuxubuntulinux-ibmresolute

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedLinux

      1 individual change: Affected versions (publisher)

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)changed
      Linux, Linux
      Linux, Linux

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    2. ReceivedLinux

      Description added or changed

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Linux, Linux
      Descriptionadded
      —
      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.
      Referenceadded
      —
      https://git.kernel.org/stable/c/30ea97affbcce236c57287c82dc6ef7a29c63b76
      Referenceadded
      —
      https://git.kernel.org/stable/c/598ed7393a639c7547b28ff3e14db9f1ac37c132
      Referenceadded
      —
      https://git.kernel.org/stable/c/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb
      Referenceadded
      —
      https://git.kernel.org/stable/c/799e54c510a03a65a57627018a817838d72f35bd
      Referenceadded
      —
      https://git.kernel.org/stable/c/8aa442cfce79e2d69e72fc8e0c0864ac2971149d
      Referenceadded
      —
      https://git.kernel.org/stable/c/d47b0b8a69a13e06afafa54723f3e8c99b0c788f
      Referenceadded
      —
      https://git.kernel.org/stable/c/ef4fc53898bd6c4d0119cc6d419ebef7f2560f31

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-74379
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-74379"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-74379.svg?lang=en" alt="CVE-2026-74379 – NEOSEC Intel" height="20"></a>