CVE-2026-98971: Linux kernel · gpio: exar: initialize the ID before registering its cleanup
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f7ec4dbd2a073dd53b6349be1c586fe8580dd6b2 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f7ec4dbd2a073dd53b6349be1c586fe8580dd6b2, bf3d841ef12fcbec4458e2750956b738b043a226, b78c114600ae3df90c083c72c290437b068577c8 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel as indicated by the presence of fixed commit versions. Users should update to a Linux kernel version that includes these fixes to resolve the issue.
Description
A vulnerability in the Linux kernel's gpio exar driver was fixed by ensuring the device ID is initialized before registering its cleanup action. The issue caused incorrect ID handling during failure in registering cleanup, potentially freeing the wrong device ID and leaking allocated IDs.
References
- git.kernel.org/stable/c/bf3d841ef12fcbec4458e2750956b738b043a226 (opens in a new tab)
- git.kernel.org/stable/c/b78c114600ae3df90c083c72c290437b068577c8 (opens in a new tab)
- git.kernel.org/stable/c/01318927a9055136c207399eeb36ce07becac179 (opens in a new tab)
- git.kernel.org/stable/c/f7ec4dbd2a073dd53b6349be1c586fe8580dd6b2 (opens in a new tab)
- git.kernel.org/stable/c/4d69e74034b208588636ecc177e0dd43a7696af3 (opens in a new tab)