CVE-2026-89626: HID: sensor: custom: Fix field sysfs group cleanup on failure
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 10b05fafff932e325896d59dde40938954ab4577, 2409779f3096fcef41bcf57b5f4887d0fa0dc8dd, 3789d0802ddb4b3be04062caf4bfadd23496e9a7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 10b05fafff932e325896d59dde40938954ab4577, 2409779f3096fcef41bcf57b5f4887d0fa0dc8dd, 3789d0802ddb4b3be04062caf4bfadd23496e9a7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.1affected
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 416194933af63bd58d03b7605b1ebc1711186838affected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before d0e15091e88d18e30b67daf85b88f6528bb9bf41affected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 10b05fafff932e325896d59dde40938954ab4577affected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 2409779f3096fcef41bcf57b5f4887d0fa0dc8ddaffected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 79154fad98ee843e5363940841e2d831503c190aaffected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before f3f37b937a6ea2a00fb5e6189e74f855caa43eb5affected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before d96f8958d4469ac02d9c563686cdd968005b944daffected · git
- 4a7de0519df5e8fb89cef6ee062330ffe4b50a4d and later · before 3789d0802ddb4b3be04062caf4bfadd23496e9a7affected · git
- before 4.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89624Sep 11, 2026 · HID: universal-pidff: stop the device when force-feedback init fails31Monitor
- ← EarlierCVE-2026-89625Sep 11, 2026 · HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind0Monitor
- Later →CVE-2026-89627Sep 11, 2026 · HID: roccat: free buffered reports when destroying device0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 10b05fafff932e325896d59dde40938954ab4577 | Vendor (CNA) |
| Linux Linux | 2409779f3096fcef41bcf57b5f4887d0fa0dc8dd | Vendor (CNA) |
| Linux Linux | 3789d0802ddb4b3be04062caf4bfadd23496e9a7 | Vendor (CNA) |
| Linux Linux | 416194933af63bd58d03b7605b1ebc1711186838 | Vendor (CNA) |
| Linux Linux | 79154fad98ee843e5363940841e2d831503c190a | Vendor (CNA) |
| Linux Linux | d0e15091e88d18e30b67daf85b88f6528bb9bf41 | Vendor (CNA) |
| Linux Linux | d96f8958d4469ac02d9c563686cdd968005b944d | Vendor (CNA) |
| Linux Linux | f3f37b937a6ea2a00fb5e6189e74f855caa43eb5 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2409779f3096fcef41bcf57b5f4887d0fa0dc8dd
- git.kernel.org/stable/c/3789d0802ddb4b3be04062caf4bfadd23496e9a7
- git.kernel.org/stable/c/416194933af63bd58d03b7605b1ebc1711186838
- git.kernel.org/stable/c/79154fad98ee843e5363940841e2d831503c190a
- git.kernel.org/stable/c/d0e15091e88d18e30b67daf85b88f6528bb9bf41
- git.kernel.org/stable/c/d96f8958d4469ac02d9c563686cdd968005b944d
- git.kernel.org/stable/c/f3f37b937a6ea2a00fb5e6189e74f855caa43eb5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.