# CVE-2026-64462: PCI: altera: Fix resource leaks on probe failure

> A use-after-free vulnerability in the Linux kernel Altera PCI driver allows local attackers to cause denial of service or potentially execute code via probe failure.

- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** AZL-93786, BELL-CVE-2026-64462, DEBIAN-CVE-2026-64462, GHSA-w9v7-p38p-x494, ROOT-OS-UBUNTU-2204-CVE-2026-64462, UBUNTU-CVE-2026-64462

## What is CVE-2026-64462?

CVE-2026-64462 is an use after free vulnerability in Linux, published on 25 Jul 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:

PCI: altera: Fix resource leaks on probe failure

The chained IRQ handler is set during probe, but is only removed during the
driver remove(). If pci_host_probe() fails, the handler and INTx IRQ
domain remain set even though the devm-managed host bridge storage
containing struct altera_pcie will be released, leaving the handler with
a stale data pointer.

Interrupts are also enabled before pci_host_probe() is called. If probe
fails after that point, the controller interrupt source should be disabled
before the chained handler and INTx domain are removed.

So set the chained handler only after the INTx domain has been created.
Disable controller interrupts during IRQ teardown, and tear the IRQ setup
down if pci_host_probe() fails.

[mani: commit log]

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


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

Apply the vendor's patch.

## Is CVE-2026-64462 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64462 is an use after free vulnerability in Linux, published on 25 Jul 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-64462 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-64462/ (Markdown: https://insights.sbomify.com/CVE-2026-64462/index.md)
```

## Sources

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

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