Look up another CVE · open CVE-2026-93070 in the interactive tracker
CVE-2026-93070
media: ipu6: Do not free aux device pdata after init
Published 2026-09-17 (31 days ago) by the Linux kernel CNA. Subsystem drivers/media. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-93070 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 | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| 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
ipu6_bus_initialize_device() stores the isys/psys pdata pointer in struct ipu6_bus_device and initializes the auxiliary device. After that point, error unwinding must drop the auxiliary device reference and let ipu6_bus_release() free both the bus device and adev->pdata. The isys and psys init paths already call put_device() when MMU initialization fails, and ipu6_bus_add_device() calls auxiliary_device_uninit() on auxiliary_device_add() failure. Both paths therefore run the bus release callback. The extra kfree(pdata) in the callers can release the same object a second time. Remove the manual pdata frees after the auxiliary device has been initialized. This issue was found by a static analysis checker and confirmed by manual source review.
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/intel/ipu6/ipu6.c
- What this is
- INTEL IPU6 INPUT SYSTEM DRIVERMAINTAINERS section matched on drivers/media/pci/intel/ipu6/ · linux-media@vger.kernel.org · Maintained
- Kernel module
- intel_ipu6
Check it on the machine
grep -w CONFIG_VIDEO_INTEL_IPU6 /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 intel_ipu6Prints 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. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixieMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switch
- CONFIG_VIDEO_INTEL_IPU6
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-17 (31 days 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.16%, higher than 5.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- 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 |
|---|---|---|
| 6.10 | 6.12.110 | faa1eb97f0e6 |
| 6.10 | 6.18.52 | 5323ed5a7bb2 |
| 6.10 | 7.2.6 | 7d102d1f0631 |
| 6.10 | 7.3 | 9be07216af4c |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| 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 extra kfree(pdata) runs only in ipu6_isys_init()/ipu6_psys_init() after ipu6_bus_initialize_device(), called from ipu6_pci_probe() on Intel IPU6 PCI IDs (0x9a19/0x4e19/0x465d/0x462e/0xa75d/0x7d19). V4L2 ioctls and received packets never enter those error paths; this is a local PCI probe, not a network or USB protocol path.
- AC:LAttack complexity, low
- After ipu6_mmu_init() fails, put_device() runs ipu6_bus_release() which kfree(adev->pdata) before the extra kfree(pdata); ipu6_bus_add_device() does the same via auxiliary_device_uninit() when auxiliary_device_add() fails. Both double-frees then run with no race. A local attacker can induce those ENOMEM failures (alloc_dma_mapping()/device_add()) with allocation pressure.
- PR:LPrivileges required, low
- ipu6_pci_probe() performs no capable() check. Sysfs bind/modprobe needs init-namespace admin, but probe already runs automatically: request_firmware() for isp->cpd_fw_name waits for userspace, and ipu_bridge_init() can return -EPROBE_DEFER until IVSC is ready then retry. An ordinary local user can apply memory pressure during that automatic probe, so Low is the higher defensible value.
- UI:NUser interaction, none
- The double-free occurs inside ipu6_pci_probe error unwinding in ipu6_isys_init()/ipu6_psys_init(); no mount, file open, or other victim action is required. PCI enumeration, firmware wait, and IVSC deferred retries are kernel/udev driven.
- S:UScope, unchanged
- kfree of the isys/psys pdata slab and the containing ipu6_bus_device corrupts host kernel heap in the same security authority as the IPU6 PCI driver. This is not a VM escape, IOMMU bypass, or sandbox boundary cross.
- C:HConfidentiality impact, high
- ipu6_bus_release() already kfree(adev->pdata) and kfree(adev); the extra kfree(pdata) is a SLUB double-free of ipu6_isys_pdata/ipu6_psys_pdata, and the MMU-fail path then reads isys_adev->mmu after adev was freed. Reclaiming those slabs can disclose kernel memory.
- I:HIntegrity impact, high
- Double-free of pdata after ipu6_bus_release(), plus kfree of struct ipu6_bus_device on the MMU-fail put_device() path, yields two owners of one heap object. That overlapping allocation can corrupt live kernel structures and is exploitable for arbitrary writes or control-flow hijack, not merely a clean fail.
- A:HAvailability impact, high
- The second kfree(pdata) after ipu6_bus_release() trips SLAB_FREELIST_HARDENED BUG_ON or corrupts the freelist, and the MMU-fail path dereferences the already-freed ipu6_bus_device via isys_adev->mmu. Either produces a kernel oops or panic during probe unwind.