MediumCVE-2026-80824

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

    Published Last modified Sources: Red Hat, HKCERT, Ubuntu, Debian LTS, Debian, SUSE, CVE.org, BSI, EUVD, Msrc Update Guide

    Share

    What is affected, what to do

    A flaw was found in the Linux kernel's USB subsystem (usbfs). An unprivileged local attacker with read/write access to a /dev/bus/usb node could exploit a use-after-free vulnerability.

    Update Linux Kernel to version 5.10.269, Linux Kernel to version 5.15.220, Linux Kernel to version 6.1.187.

    Affected
    • Linux Kernel lt 4.6..5.10.269
    • Linux Kernel lt 5.11..5.15.220
    • Linux Kernel lt 5.16..6.1.187
    • Linux Kernel lt 6.2..6.6.156
    • Linux Kernel lt 6.7..6.12.108
    • Linux Kernel lt 6.13..6.18.49
    • Linux Kernel lt 6.19..7.1.13
    • Linux Kernel lt 7.2..7.2.3
    Fixed in
    • Linux Kernel 5.10.269
    • Linux Kernel 5.15.220
    • Linux Kernel 6.1.187
    • Linux Kernel 6.6.156
    • Linux Kernel 6.12.108
    • Linux Kernel 6.18.49
    • Linux Kernel 7.1.13
    • Linux Kernel 7.2.3
    • Linux Kernel 7.3

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

    Metrics

    4.1

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    4.1

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Red Hat, HKCERT, Ubuntu, Debian LTS, Debian, SUSE, CVE.org, BSI, EUVD, Msrc Update Guide

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 9.3

    Show all metrics
    Severity
    Medium
    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
    45.26 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
    4.1 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
    4.1
    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
    9.3
    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

    A flaw was found in the Linux kernel's USB subsystem (usbfs). An unprivileged local attacker with read/write access to a /dev/bus/usb node could exploit a use-after-free vulnerability. This occurs because the usb_device structure is prematurely freed before all pending operations are completed. Successful exploitation of this memory corruption flaw could lead to a system crash or potentially privilege escalation.

    Source: redhat_csaf, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, Debian LTS Advisories, Debian Security Advisories, suse_csaf, NVD (NIST), CVE.org (MITRE), BSI WID Portal, BSI CSAF, ENISA EUVD, cvelistv5, Microsoft Security Update Guide

    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
    • 4.6 – < 5.10.269
    • 6.13 – < 6.18.49
    • 5.11 – < 5.15.220
    • 5.16 – < 6.1.187
    • 6.7 – < 6.12.108
    • 7.2 – < 7.2.3
    • —
    • 6.19 – < 7.1.13
    • 6.2 – < 6.6.156
    • 5.10.269
    • 6.18.49
    • 5.15.220
    • 6.1.187
    • 6.12.108
    • 7.2.3
    • 7.3
    • 7.1.13
    • 6.6.156
    Red HatOpenShift
    • Container Platform
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinuxtrixie
    Linuxubuntulinuxjammy
    Linuxubuntulinuxnoble
    Linuxubuntulinuxresolute
    Linuxdebianlinux-6.12bookworm
    Linuxubuntulinux-awsjammy
    Linuxubuntulinux-awsnoble
    Linuxubuntulinux-awsresolute
    Linuxubuntulinux-aws-5.15focal
    Linuxubuntulinux-aws-6.8jammy
    Linuxubuntulinux-aws-7.0noble
    Linuxubuntulinux-aws-fipsjammy
    Linuxubuntulinux-aws-fipsnoble
    Linuxubuntulinux-azurejammy
    Linuxubuntulinux-azurenoble
    Linuxubuntulinux-azureresolute
    Linuxubuntulinux-azure-5.15focal
    Linuxubuntulinux-azure-6.8jammy
    Linuxubuntulinux-azure-fdejammy
    Linuxubuntulinux-azure-fdenoble
    Linuxubuntulinux-azure-fderesolute
    Linuxubuntulinux-azure-fde-5.15focal
    Linuxubuntulinux-azure-fde-6.8jammy

    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)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80824.json">CVE-2026-80824</a>

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

    2. ReceivedLinux

      Description added or changed

      Show 11 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: usb: usbfs: fix use-after-free of usb_device in usbdev_release() usbdev_release() drops its reference to the struct usb_device before draining the list of completed async URBs, but that drain path reads back through the same object: free_async() calls dec_usb_memory_use_count() for any URB whose buffer came from the usbfs mmap() region, and its first statement is bus_to_hcd(ps->dev->bus). After a disconnect the usbfs reference can be the last one, in which case usb_put_dev() frees the device and the subsequent loop reads offset 80 of freed memory and uses the result as a struct usb_hcd *, which hcd_buffer_free_pages() then dereferences. This is reachable by an unprivileged process that has read/write access to a /dev/bus/usb node: mmap() the fd, submit one URB with a buffer inside the mapping, wait for the device to be unplugged, then munmap() and close(). It reproduces on every attempt rather than being a race, because a live MAP_SHARED vma holds a reference on the struct file, so usbdev_release() cannot run until the last vma is gone and the freeing branch of dec_usb_memory_use_count() is always taken. BUG: KASAN: slab-use-after-free in dec_usb_memory_use_count+0x3ae/0x410 Read of size 8 at addr ffff8880122ee050 by task poc/769 CPU: 1 UID: 1000 PID: 769 Comm: poc Tainted: G B 6.12.94 #3 Call Trace: dec_usb_memory_use_count+0x3ae/0x410 free_async+0x2aa/0x4f0 usbdev_release+0x375/0x460 __fput+0x3ea/0xb50 __x64_sys_close+0x86/0x100 Allocated by task 11: usb_alloc_dev+0x55/0xd90 hub_event+0x2524/0x43d0 Freed by task 769: kfree+0x121/0x360 device_release+0xd2/0x280 usb_put_dev+0x23/0x30 usbdev_release+0x2d8/0x460 Release the device reference after the drain loop instead. Nothing between the two points requires it to have been dropped.
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80824.json">CVE-2026-80824</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/0a960b88c5979f853019d4dc4957dfbeeb193440
      Referenceadded
      —
      https://git.kernel.org/stable/c/0dd68b5d01d022fc9c5e71c82a82b0a94d3d0671
      Referenceadded
      —
      https://git.kernel.org/stable/c/47a7f98fbb5006d46d15a3a210ffdc61448a4f19
      Referenceadded
      —
      https://git.kernel.org/stable/c/5f08c45bdcfd28d1171de38c5ef29fc89a76eedc
      Referenceadded
      —
      https://git.kernel.org/stable/c/65879e0a452ca2a234b9475e0c11aff7a4343738
      Referenceadded
      —
      https://git.kernel.org/stable/c/7f0278e474c4d1c4457974ff1137cc385c944ab3
      Referenceadded
      —
      https://git.kernel.org/stable/c/96f5520fc9a5e4bbf77ac93c9d5ce502f597e6cf
      Referenceadded
      —
      https://git.kernel.org/stable/c/b3cde26a66b04f1d90ed0b675899c88b4e49d424
      Referenceadded
      —
      https://git.kernel.org/stable/c/bd4bffc621a8cb2f4d9ed9b6447415de524a3bef

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