# CVE-2026-80732: ata: pata_sl82c105: fix bridge revision use-after-free

> A use-after-free in the Linux kernel pata_sl82c105 driver allows attackers to potentially execute code or cause a system crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** AZL-99026, BELL-CVE-2026-80732, DEBIAN-CVE-2026-80732, GHSA-p564-mwrx-5m7j, UBUNTU-CVE-2026-80732

## What is CVE-2026-80732?

CVE-2026-80732 is a high-severity use after free vulnerability in Linux, published on 3 Sep 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:

ata: pata_sl82c105: fix bridge revision use-after-free

pci_get_slot() returns a referenced PCI device. Commit 44c10138fd4b
("PCI: Change all drivers to use pci_device->revision") replaced a
configuration-space read with direct access to the cached revision field,
but left that access after pci_dev_put(). The bridge may therefore be freed
before its revision is read.

Read the revision before dropping the reference.

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


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

Apply the vendor's patch.

## Is CVE-2026-80732 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80732 is a high-severity use after free vulnerability in Linux, published on 3 Sep 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-80732 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-80732/ (Markdown: https://insights.sbomify.com/CVE-2026-80732/index.md)
```

## Sources

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

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