Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80767HID: sensor: custom: Fix use-after-free in enable_sensor

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < c2be74b0272b7f8f60739e7aaf0d36c0befe7136
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < d37ff4e3635c18af907f25712596f8ccec323751
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < 2ce90cfc6646a32100feabd7110ae0352aa01167
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < 244a1cb638370490ed74a8adb5cc3f1212602e32
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < 8406d4b69d48bc72fb6f8812a65a17a1f903440b
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < c0757f10610542d763bd0bf9bda455b78afeef0b
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < 7bb79a3cf45e0805aef74457e19deb77e18cf196
    • affected 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d – < ad8fb82b04422f49530d2aa2753cc81d1c60102c
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80767 badge
[![CVE-2026-80767](https://cveledger.app/badge/CVE-2026-80767.svg)](https://cveledger.app/cve/CVE-2026-80767)

Record last updated .