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

> A use-after-free vulnerability in the Linux kernel HID sensor driver allows local attackers to execute arbitrary code or escalate privileges via sysfs writes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99500, BELL-CVE-2026-80767, DEBIAN-CVE-2026-80767, GHSA-hxq5-9fvr-38r3, UBUNTU-CVE-2026-80767

## What is CVE-2026-80767?

CVE-2026-80767 is an use after free vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-80767?


## How do I fix CVE-2026-80767?

Apply the vendor's patch.

## Is CVE-2026-80767 being exploited?

There is no known exploitation of CVE-2026-80767 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80767 and fix it if it is affected.

What it is: CVE-2026-80767 is an use after free vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80767 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80767/ (Markdown: https://insights.sbomify.com/CVE-2026-80767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80767
- OSV: https://osv.dev/vulnerability/CVE-2026-80767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80767/
Summaries are generated and may contain mistakes; the official description above is the record.