# CVE-2026-89626: HID: sensor: custom: Fix field sysfs group cleanup on failure

> A failure in sysfs group creation leaves dangling pointers, potentially causing a use-after-free or memory corruption in the Linux kernel HID sensor driver.

- **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-100428, BELL-CVE-2026-89626, DEBIAN-CVE-2026-89626, GHSA-5r2j-h2g4-5h5v, UBUNTU-CVE-2026-89626

## What is CVE-2026-89626?

CVE-2026-89626 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: custom: Fix field sysfs group cleanup on failure

hid_sensor_custom_add_attributes() creates one sysfs group for each
custom sensor field. If sysfs_create_group() fails after some groups
have already been created, the function returns the error without
removing the previously created groups.

Add a local unwind path to remove the groups that were already created.
With enable_sensor exposed only after the field attributes are ready,
this path can free sensor_inst->fields without leaving enable_sensor
able to access pointers into that array.

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


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

Apply the vendor's patch.

## Is CVE-2026-89626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89626 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-89626 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-89626/ (Markdown: https://insights.sbomify.com/CVE-2026-89626/index.md)
```

## Sources

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

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