MediumCVE-2026-80767

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

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

    Share

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: HID: sensor: custom: Fix use-after-free in enable_sensor enable_sensor_store() can call set_power_report_state(), which dereferences sensor_inst->power_state and sensor_inst->report_state. These pointers refer to entries in sensor_inst->fields.

    Update Linux Kernel to version 5.10.267, Linux Kernel to version 5.15.218, Linux Kernel to version 6.1.185.

    Affected
    • Linux Kernel lt 4.1..5.10.267
    • Linux Kernel lt 5.11..5.15.218
    • Linux Kernel lt 5.16..6.1.185
    • Linux Kernel lt 6.2..6.6.154
    • Linux Kernel lt 6.7..6.12.106
    • Linux Kernel lt 6.13..6.18.47
    • Linux Kernel lt 6.19..7.1.11
    • Linux Kernel lt 7.2..7.2.1
    Fixed in
    • Linux Kernel 5.10.267
    • Linux Kernel 5.15.218
    • Linux Kernel 6.1.185
    • Linux Kernel 6.6.154
    • Linux Kernel 6.12.106
    • Linux Kernel 6.18.47
    • Linux Kernel 7.1.11
    • Linux Kernel 7.2.1
    • Linux Kernel 7.3

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

    Metrics

    4.7

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    4.7

    CVSS v3

    Severity Medium on the scale from 0 to 10.

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

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

    In the Linux kernel, the following vulnerability has been resolved: HID: sensor: custom: Fix use-after-free in enable_sensor enable_sensor_store() can call set_power_report_state(), which dereferences sensor_inst->power_state and sensor_inst->report_state. These pointers refer to entries in sensor_inst->fields. Create the field attributes before exposing the enable_sensor sysfs attribute, so enable_sensor cannot be accessed before the state it depends on has been initialized. On remove, delete enable_sensor before freeing the field attributes, so a concurrent sysfs write cannot dereference freed memory through power_state or report_state.

    Source: Ubuntu Security Notices, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Debian LTS Advisories, suse_csaf, ENISA EUVD, cvelistv5, NVD (NIST), CVE.org (MITRE), 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
    • 7.2 – < 7.2.1
    • 5.11 – < 5.15.218
    • 4.1 – < 5.10.267
    • 6.2 – < 6.6.154
    • 6.7 – < 6.12.106
    • —
    • 6.13 – < 6.18.47
    • 6.19 – < 7.1.11
    • 5.16 – < 6.1.185
    • 7.2.1
    • 5.15.218
    • 5.10.267
    • 6.6.154
    • 6.12.106
    • 7.3
    • 6.18.47
    • 7.1.11
    • 6.1.185
    Red HatOpenShift
    • Container Platform
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    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
    Linuxubuntulinux-azure-fde-7.0noble

    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-80767.json">CVE-2026-80767</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: HID: sensor: custom: Fix use-after-free in enable_sensor enable_sensor_store() can call set_power_report_state(), which dereferences sensor_inst->power_state and sensor_inst->report_state. These pointers refer to entries in sensor_inst->fields. Create the field attributes before exposing the enable_sensor sysfs attribute, so enable_sensor cannot be accessed before the state it depends on has been initialized. On remove, delete enable_sensor before freeing the field attributes, so a concurrent sysfs write cannot dereference freed memory through power_state or report_state.
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80767.json">CVE-2026-80767</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/244a1cb638370490ed74a8adb5cc3f1212602e32
      Referenceadded
      —
      https://git.kernel.org/stable/c/2ce90cfc6646a32100feabd7110ae0352aa01167
      Referenceadded
      —
      https://git.kernel.org/stable/c/7bb79a3cf45e0805aef74457e19deb77e18cf196
      Referenceadded
      —
      https://git.kernel.org/stable/c/8406d4b69d48bc72fb6f8812a65a17a1f903440b
      Referenceadded
      —
      https://git.kernel.org/stable/c/ad8fb82b04422f49530d2aa2753cc81d1c60102c
      Referenceadded
      —
      https://git.kernel.org/stable/c/c0757f10610542d763bd0bf9bda455b78afeef0b
      Referenceadded
      —
      https://git.kernel.org/stable/c/c2be74b0272b7f8f60739e7aaf0d36c0befe7136
      Referenceadded
      —
      https://git.kernel.org/stable/c/d37ff4e3635c18af907f25712596f8ccec323751
      Referenceadded
      —
      https://git.kernel.org/stable/c/d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855

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