Look up another CVE · open CVE-2026-80732 in the interactive tracker
CVE-2026-80732
ata: pata_sl82c105: fix bridge revision use-after-free
Published 2026-09-03 (2 months ago) by the Linux kernel CNA. Subsystem drivers/ata. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80732 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4777-1 · 2026-09-08 · text | 6.1.187-1 | Update the kernel and reboot. DLA-4777-1 shipped the fix on 2026-09-08, in 6.1.187-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.105-1 | Update the kernel and reboot. Fixed in 6.12.105-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4788-1 · 2026-09-19 · text | 6.12.107-1~deb12u1 | Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/ata/pata_sl82c105.c
- What this is
- LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)MAINTAINERS section matched on drivers/ata/ · linux-ide@vger.kernel.org · Maintained
- Kernel module
- pata_sl82c105
Check it on the machine
grep -wE 'CONFIG_ATA|CONFIG_PATA_WINBOND' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w pata_sl82c105Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, i386/686, i386/686-pae, i386/rt/686-pae
- trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_ATA, CONFIG_PATA_WINBOND
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-03 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 6.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/ata
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.23 | 5.10.265 | 1268ca9418e2 |
| 2.6.23 | 5.15.216 | a626dfca9604 |
| 2.6.23 | 6.1.183 | 5ef87b1b4656 |
| 2.6.23 | 6.6.152 | fa0dca89b4fb |
| 2.6.23 | 6.12.104 | dc711fb137b3 |
| 2.6.23 | 6.18.45 | a837deeaa37c |
| 2.6.23 | 7.1.9 | 56fd78c8c820 |
| 2.6.23 | 7.2 | 7700a31039cd |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4788-1 | 2026-09-19 | bookworm 6.12.107-1~deb12u1 | tracker |
| DLA-4777-1 | 2026-09-08 | bookworm 6.1.187-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- sl82c105_bridge_revision() is only reached from sl82c105_init_one() during PCI driver probe of onboard SL82C105 hardware, triggered by boot enumeration, udev, or local module/sysfs bind; no network or adjacent protocol path exists.
- AC:LAttack complexity, low
- Once CONFIG_PATA_WINBOND and matching Winbond W83C553 bridge hardware are present, the UAF is a deterministic, synchronous read after pci_dev_put() on every successful probe path—no race, layout dependency, or victim state beyond standard probe.
- PR:LPrivileges required, low
- Probe is initiated automatically by kernel PCI enumeration and udev during boot or hotplug on systems with SL82C105 storage (Netwinder, briq, legacy embedded), so reaching the bug does not require admin action; only local presence on such a host is needed.
- UI:NUser interaction, none
- Driver probe runs automatically during boot enumeration or udev module load when matching PCI hardware is present; no administrator or victim must mount media, open files, or perform any interactive action.
- S:UScope, unchanged
- Corrupting or reading freed pci_dev memory affects only the host kernel address space, yielding a standard local kernel compromise or panic rather than crossing a VM, hypervisor, or IOMMU boundary.
- C:HConfidentiality impact, high
- Reading bridge->revision after pci_dev_put() is a use-after-free of struct pci_dev; if the allocation is reused, the attacker obtains a kernel memory disclosure primitive and can read adjacent freed data.
- I:HIntegrity impact, high
- UAF of struct pci_dev enables heap-spray reclamation of the freed object, giving attacker-controlled contents for subsequent kernel dereferences and a well-established path to arbitrary write and privilege escalation.
- A:HAvailability impact, high
- Dereferencing a potentially freed pci_dev during probe can immediately oops or panic the kernel; even without full exploitation, UAF corruption commonly crashes the system on affected legacy embedded hosts.