MediumCVE-2026-80780

    Linux Kernel: Out-of-Bounds Write (CVE-2026-80780)

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

    Share

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: HID: pidff: fix OOB write when hid->inputs is empty hid_pidff_init_with_quirks() derives its input_dev from list_entry(hid->inputs.next, struct hid_input, list) without first checking that hid->inputs is non-empty. The list member of struct hid_input is at offset 0, so on an empty list list_entry() yields &hid->inputs itself and the following hidinput->input load reads an unrelated member of struct hid_device. dev is then a type-confused pointer, and force-feedback init writes through it: each set_bit(FF_*, dev->ffbit) stores 8 bytes at dev + 192, past the end of the object dev actually aliases, and input_ff_create() adds further writes of a heap pointer and two function pointers.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Conflicting version data — version display is hidden until the data is resolved.

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

    Metrics

    5.9

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    5.9

    CVSS v3

    Severity Medium on the scale from 0 to 10.

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

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 7.8

    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
    53.84 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
    5.9 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
    5.9
    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
    7.8
    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: HID: pidff: fix OOB write when hid->inputs is empty hid_pidff_init_with_quirks() derives its input_dev from list_entry(hid->inputs.next, struct hid_input, list) without first checking that hid->inputs is non-empty. The list member of struct hid_input is at offset 0, so on an empty list list_entry() yields &hid->inputs itself and the following hidinput->input load reads an unrelated member of struct hid_device. dev is then a type-confused pointer, and force-feedback init writes through it: each set_bit(FF_*, dev->ffbit) stores 8 bytes at dev + 192, past the end of the object dev actually aliases, and input_ff_create() adds further writes of a heap pointer and two function pointers. Until hid-universal-pidff the only caller was hid_pidff_init() from usbhid, which runs under HID_CLAIMED_INPUT and therefore always has at least one hid_input. universal_pidff_probe() starts the device with HID_CONNECT_DEFAULT & ~HID_CONNECT_FF and then calls hid_pidff_init_with_quirks() directly whenever the descriptor carries a PID usage page, bypassing that gate. A report descriptor whose only application collection is on HID_UP_PID leaves hid->inputs empty while hid_connect() still succeeds through the hidraw claim, so probe reaches the unguarded list_entry(). The write happens in the USB probe path, on the hotplug workqueue, so plugging in a malicious device is enough to trigger it; no attacker software and no logged-in user are required. KASAN reports an 8-byte out-of-bounds write in hid_pidff_init_with_quirks() reached from universal_pidff_probe(). Check for an empty list before deriving dev and return -ENODEV, as the other HID force-feedback drivers already do. universal_pidff_probe() propagates the error and unwinds. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>

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

    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.6.88 – < 6.6.156
    • 6.15 – < 6.18.47
    • 7.2 – < 7.2.1
    • 6.12.24 – < 6.12.108
    • —
    • 6.13.12 – < 6.14
    • 6.19 – < 7.1.11
    • 6.14.3 – < 6.15
    • 6.6.156
    • 6.18.47
    • 7.2.1
    • 6.12.108
    • 7.3
    • 6.14
    • 7.1.11
    • 6.15
    Red HatOpenShift
    • Container Platform
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxtrixie
    Linuxubuntulinuxnoble
    Linuxubuntulinuxresolute
    Linuxdebianlinux-6.12bookworm
    Linuxubuntulinux-awsnoble
    Linuxubuntulinux-awsresolute
    Linuxubuntulinux-aws-6.8jammy
    Linuxubuntulinux-aws-7.0noble
    Linuxubuntulinux-aws-fipsnoble
    Linuxubuntulinux-azurenoble
    Linuxubuntulinux-azureresolute
    Linuxubuntulinux-azure-6.8jammy
    Linuxubuntulinux-azure-fdenoble
    Linuxubuntulinux-azure-fderesolute
    Linuxubuntulinux-azure-fde-6.8jammy
    Linuxubuntulinux-azure-fde-7.0noble
    Linuxubuntulinux-azure-fipsnoble
    Linuxubuntulinux-gcpnoble
    Linuxubuntulinux-gcpresolute
    Linuxubuntulinux-gcp-6.8jammy
    Linuxubuntulinux-gcp-7.0noble
    Linuxubuntulinux-gcp-fipsnoble
    Linuxubuntulinux-gkenoble
    Linuxubuntulinux-gkeresolute

    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-80780.json">CVE-2026-80780</a>

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

    2. ReceivedLinux

      Description added or changed

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: HID: pidff: fix OOB write when hid->inputs is empty hid_pidff_init_with_quirks() derives its input_dev from list_entry(hid->inputs.next, struct hid_input, list) without first checking that hid->inputs is non-empty. The list member of struct hid_input is at offset 0, so on an empty list list_entry() yields &hid->inputs itself and the following hidinput->input load reads an unrelated member of struct hid_device. dev is then a type-confused pointer, and force-feedback init writes through it: each set_bit(FF_*, dev->ffbit) stores 8 bytes at dev + 192, past the end of the object dev actually aliases, and input_ff_create() adds further writes of a heap pointer and two function pointers. Until hid-universal-pidff the only caller was hid_pidff_init() from usbhid, which runs under HID_CLAIMED_INPUT and therefore always has at least one hid_input. universal_pidff_probe() starts the device with HID_CONNECT_DEFAULT & ~HID_CONNECT_FF and then calls hid_pidff_init_with_quirks() directly whenever the descriptor carries a PID usage page, bypassing that gate. A report descriptor whose only application collection is on HID_UP_PID leaves hid->inputs empty while hid_connect() still succeeds through the hidraw claim, so probe reaches the unguarded list_entry(). The write happens in the USB probe path, on the hotplug workqueue, so plugging in a malicious device is enough to trigger it; no attacker software and no logged-in user are required. KASAN reports an 8-byte out-of-bounds write in hid_pidff_init_with_quirks() reached from universal_pidff_probe(). Check for an empty list before deriving dev and return -ENODEV, as the other HID force-feedback drivers already do. universal_pidff_probe() propagates the error and unwinds. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80780.json">CVE-2026-80780</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/2e0471bf3ab2a6b7eedcc3b8a2a17286b6a9ae1a
      Referenceadded
      —
      https://git.kernel.org/stable/c/4529c03c3da8f91392cd630453452f569973f4cd
      Referenceadded
      —
      https://git.kernel.org/stable/c/67bb1074e3d2d12fa059a9cc707e89398a4e4704
      Referenceadded
      —
      https://git.kernel.org/stable/c/86b63adfa5e132beac4be72668fdf9128fe51d2e
      Referenceadded
      —
      https://git.kernel.org/stable/c/ad9330f7e74a97842815a291a0d7389ed2f34504
      Referenceadded
      —
      https://git.kernel.org/stable/c/d416eeb7d016d82af67c149d884bc6a9323c4ac7

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