ID allocation corruption via premature cleanup registration
Published Oct 23, 2026 · Updated Oct 23, 2026
Incorrect ID cleanup in Linux's Exar GPIO driver allows attackers to corrupt device-ID allocation via probe registration failure. gpio_exar_probe() registers cleanup before storing the allocated ID, so immediate failure cleanup releases ID 0 and leaks a nonzero allocation. Exposure requires an Exar GPIO device and cleanup-registration failure; attacker control of that failure and consequences beyond ID mismanagement are not documented.
Summary
What happened
Incorrect ID cleanup in Linux's Exar GPIO driver allows attackers to corrupt device-ID allocation via probe registration failure. gpio_exar_probe() registers cleanup before storing the allocated ID, so immediate failure cleanup releases ID 0 and leaks a nonzero allocation. Exposure requires an Exar GPIO device and cleanup-registration failure; attacker control of that failure and consequences beyond ID mismanagement are not documented.
The record
- CVE
- CVE-2026-98971
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.11
- Affected versionversion=5300ebb695fa0672589ab191062392f686fca75d <01318927a9055136c207399eeb36ce07becac179
- Affected versionversion=5300ebb695fa0672589ab191062392f686fca75d <4d69e74034b208588636ecc177e0dd43a7696af3
- Affected versionversion=5300ebb695fa0672589ab191062392f686fca75d <b78c114600ae3df90c083c72c290437b068577c8
- Affected versionversion=5300ebb695fa0672589ab191062392f686fca75d <bf3d841ef12fcbec4458e2750956b738b043a226
- Affected versionversion=5300ebb695fa0672589ab191062392f686fca75d <f7ec4dbd2a073dd53b6349be1c586fe8580dd6b2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us