# CVE-2026-98435: EDAC/altera: Use parent device for devres in altr_portb_setup()

> A Linux kernel EDAC driver bug causes resource management errors, potentially leading to system crashes or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108578, BELL-CVE-2026-98435, DEBIAN-CVE-2026-98435, GHSA-jhg6-q2rv-x659, UBUNTU-CVE-2026-98435

## What is CVE-2026-98435?

CVE-2026-98435 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

EDAC/altera: Use parent device for devres in altr_portb_setup()

Anchor the devres group and the devm-managed IRQ requests in altr_portb_setup()
to the actual parent device (device->edac->dev) instead of the embedded struct
device inside the copied per-port altr_edac_device_dev.

This keeps devres_open_group(), devm_request_irq(), devres_remove_group() and
devres_release_group() all referring to the same long-lived device so the
group and the resources allocated inside it are torn down together.

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


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

Apply the vendor's patch.

## Is CVE-2026-98435 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98435 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98435 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-98435/ (Markdown: https://insights.sbomify.com/CVE-2026-98435/index.md)
```

## Sources

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

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