# CVE-2026-89729: HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature

> A malicious HID descriptor can trigger an out-of-bounds write in the Linux kernel sensor-hub driver, potentially allowing local attackers to execute code or escalate privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100848, BELL-CVE-2026-89729, DEBIAN-CVE-2026-89729, GHSA-2hjf-83c6-w88p, UBUNTU-CVE-2026-89729

## What is CVE-2026-89729?

CVE-2026-89729 is a high-severity memory corruption vulnerability in Linux, published on 11 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-hub: Fix out-of-bounds write in sensor_hub_get_feature

sensor_hub_get_feature() clamps its return value to the caller's buffer
size, but the copy loop still copies field->report_size / 8 bytes for
each report value. A malicious HID descriptor can advertise a large
feature field size while an IIO caller supplies a small stack buffer,
such as a single s32, causing an out-of-bounds write.

HID core stores parsed report values in __s32 slots and clamps extracted
values to 32 bits. Reject feature fields that require more than one slot
per value, guard the total byte count calculation, and clamp each
per-value copy to the remaining caller buffer.

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


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

Apply the vendor's patch.

## Is CVE-2026-89729 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89729 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89729 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-89729/ (Markdown: https://insights.sbomify.com/CVE-2026-89729/index.md)
```

## Sources

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

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