Look up another CVE · open CVE-2026-89877 in the interactive tracker
CVE-2026-89877
media: saa7164: fix cleanup on resource allocation failure
Published 2026-09-16 (33 days ago) by the Linux kernel CNA. Subsystem drivers/media. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-89877 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-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
saa7164_dev_setup() adds the device to the global saa7164_devlist before requesting the PCI BAR memory regions. If get_resources() fails, saa7164_dev_setup() decrements the device count and returns an error, but leaves the device on saa7164_devlist. The probe error path then frees the device, leaving a dangling entry on the global list. Reuse the existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning. Also release BAR0 if it was successfully requested but the BAR2 request fails.
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/media/pci/saa7164/saa7164-core.c
- What this is
- MEDIA INPUT INFRASTRUCTURE (V4L/DVB)MAINTAINERS section matched on drivers/media/ · linux-media@vger.kernel.org · Maintained
- Kernel module
- saa7164
Check it on the machine
grep -w CONFIG_VIDEO_SAA7164 /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 saa7164Prints 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/cloud-amd64, arm64/cloud-arm64
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi
- forky, sid, bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_VIDEO_SAA7164
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-16 (33 days ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.18%, higher than 7.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/media
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.32 | 6.1.188 | daa5b32cdf7d |
| 2.6.32 | 6.6.157 | 77f216f8de62 |
| 2.6.32 | 6.12.110 | 69259c627009 |
| 2.6.32 | 6.18.51 | 4d2048466af9 |
| 2.6.32 | 7.2.5 | fc65623524b5 |
| 2.6.32 | 7.3 | 28e84c6e2e67 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-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
- The bug is reached only from saa7164 PCI probe (saa7164_initdev → saa7164_dev_setup → get_resources()) on a locally attached NXP SAA7164/Hauppauge HVR card; PVR, HTPC, and broadcast systems enumerate that function at boot, udev bind, or PCI/Thunderbolt hotplug, which is a local PCI probe path, not a network or USB protocol path.
- AC:LAttack complexity, low
- A 1131:7164 function whose BAR0 or BAR2 cannot be reserved (zero-length BAR, overlap with busy iomem, or BAR2 failing after BAR0 was claimed) makes get_resources() return -EBUSY on every probe, so the dangling saa7164_devlist UAF is deterministic with no race or layout lottery the attacker cannot influence.
- PR:NPrivileges required, none
- saa7164_initdev() performs no capability or authentication checks; when a matching PCI function appears, kernel enumeration and udev module autoload run the failing get_resources() path automatically without an OS account or user-namespace privilege.
- UI:NUser interaction, none
- Probe is invoked automatically by the PCI core and udev-driven module autoload on device enumeration; no victim must open a V4L/DVB node, load firmware, or otherwise interact.
- S:UScope, unchanged
- The dangling saa7164_devlist pointer and follow-on use-after-free remain inside the host kernel saa7164 driver and do not cross a VM, IOMMU, or sandbox security boundary.
- C:HConfidentiality impact, high
- After kfree(dev) the global saa7164_devlist still points at the freed saa7164_dev; debugfs seq_start/seq_show and later probes walk that object, so reclaimed heap contents including kernel pointers can be read back — a use-after-free read primitive.
- I:HIntegrity impact, high
- The next list_add_tail() or list_del() on saa7164_devlist writes next/prev through the freed list node, corrupting whatever slab object reused that allocation and enabling an arbitrary kernel write and control-flow hijack.
- A:HAvailability impact, high
- Walking or mutating the dangling saa7164_devlist entry after kfree causes a kernel oops or panic via poisoned-slab dereference or list corruption, fully denying availability.