# CVE-2026-98932: EDAC/altera: Fix use-after-free in error paths


- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** AZL-110717, BELL-CVE-2026-98932, DEBIAN-CVE-2026-98932, GHSA-5pw6-gvgr-qwqf, UBUNTU-CVE-2026-98932

## What is CVE-2026-98932?

CVE-2026-98932 is a high-severity vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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

EDAC/altera: Fix use-after-free in error paths

In both altr_edac_a10_device_add() and altr_portb_setup(), the error path
freed the dci structure before releasing the devres group. Since the managed
single and double bit IRQ handlers use altdev(dci->pvt_info) as their data, an
IRQ firing between freeing dci and unregistering the IRQs could dereference
the freed memory.

Release the devres group first so the managed IRQs are unregistered
before the dci structure is freed.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98932 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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