# CVE-2026-98971: gpio: exar: initialize the ID before registering its cleanup


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110795, BELL-CVE-2026-98971, DEBIAN-CVE-2026-98971, GHSA-x5r8-cmvp-6558, UBUNTU-CVE-2026-98971

## What is CVE-2026-98971?

CVE-2026-98971 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

gpio: exar: initialize the ID before registering its cleanup

devm_add_action_or_reset() invokes the cleanup action immediately when
registering the action fails.  gpio_exar_probe() currently stores the
allocated ID in exar_gpio only after registering the action, so that
failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is
nonzero, this leaks that ID and can free ID 0 belonging to another device.

Store the ID before registering the cleanup action so both the immediate
failure path and normal device teardown release the correct allocation.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98971 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98971 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98971 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-98971/ (Markdown: https://insights.sbomify.com/CVE-2026-98971/index.md)
```

## Sources

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

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