HighCVE-2026-74313

    Linux Kernel: Use-After-Free (CVE-2026-74313)

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

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: vduse: hold vduse_lock across IDR lookup in open path vduse_dev_open() looks up struct vduse_dev through the IDR and then acquires dev->lock only after vduse_lock has been dropped. This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the same object from the IDR and free it before the open path locks the device, leading to a use-after-free.

    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.15..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

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Ubuntu, SUSE, BSI, CVE.org

    0.1 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 2.2

    Show all metrics
    Severity
    High
    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
    67.50 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
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    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.1 %
    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
    2.2
    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
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    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: vduse: hold vduse_lock across IDR lookup in open path vduse_dev_open() looks up struct vduse_dev through the IDR and then acquires dev->lock only after vduse_lock has been dropped. This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the same object from the IDR and free it before the open path locks the device, leading to a use-after-free. Close this race by keeping vduse_lock held until dev->lock has been acquired in the open path, matching the lock ordering already used by the destroy path.

    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.15 – < 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
    Linuxubuntulinux-gcp-5.15focal

    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

      Show 14 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/35483c5306e09b3190ff937089d404a78012695c
      Referenceadded
      —
      https://git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95
      Referenceadded
      —
      https://git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be
      Referenceadded
      —
      https://git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7
      Referenceadded
      —
      https://git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2
      Referenceadded
      —
      https://git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af
      Referenceadded
      —
      https://git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce
      Referenceremoved
      https://git.kernel.org/stable/c/35483c5306e09b3190ff937089d404a78012695c
      —
      Referenceremoved
      https://git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95
      —
      Referenceremoved
      https://git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be
      —
      Referenceremoved
      https://git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7
      —
      Referenceremoved
      https://git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2
      —
      Referenceremoved
      https://git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af
      —
      Referenceremoved
      https://git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce
      —

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

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-74313","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-16T18:53:05.168424Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Record modifiedLinux

      CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
      Affected versions (publisher)changed
      Linux, Linux
      Linux, Linux

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

    4. 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: vduse: hold vduse_lock across IDR lookup in open path vduse_dev_open() looks up struct vduse_dev through the IDR and then acquires dev->lock only after vduse_lock has been dropped. This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the same object from the IDR and free it before the open path locks the device, leading to a use-after-free. Close this race by keeping vduse_lock held until dev->lock has been acquired in the open path, matching the lock ordering already used by the destroy path.
      Referenceadded
      —
      https://git.kernel.org/stable/c/35483c5306e09b3190ff937089d404a78012695c
      Referenceadded
      —
      https://git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95
      Referenceadded
      —
      https://git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be
      Referenceadded
      —
      https://git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7
      Referenceadded
      —
      https://git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2
      Referenceadded
      —
      https://git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af
      Referenceadded
      —
      https://git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce

      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-74313
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-74313"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-74313.svg?lang=en" alt="CVE-2026-74313 – NEOSEC Intel" height="20"></a>