Look up another CVE · open CVE-2026-72133 in the interactive tracker
CVE-2026-72133
spi: uniphier: Fix completion initialization order before devm_request_irq()
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/spi. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-72133 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 | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The driver calls devm_request_irq() before initializing the completion used by the interrupt handler. Because the interrupt may occur immediately after devm_request_irq(), the handler may execute before init_completion(). This may result in calling complete() on an uninitialized completion, causing undefined behavior. This has been observed with KASAN. Fix this by initializing the completion before registering the IRQ.
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/spi/spi-uniphier.c
- What this is
- SPI SUBSYSTEMMAINTAINERS section matched on drivers/spi/ · linux-spi@vger.kernel.org · Maintained
- Kernel module
- none to look for. The file would have gone into spi_uniphier, and Debian does not compile it into that module, so finding spi_uniphier in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_SPI|CONFIG_SPI_UNIPHIER' /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.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_SPI, CONFIG_SPI_UNIPHIER
- 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-08-15 (2 months 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.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/spi
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.19 | 5.10.261 | b9fcf0db433d |
| 4.19 | 5.15.212 | 82a5746c4c9e |
| 4.19 | 6.1.178 | f4bb0a91f7ba |
| 4.19 | 6.6.145 | 49f6705d80b5 |
| 4.19 | 6.12.97 | 8b5798ce0007 |
| 4.19 | 6.18.40 | d44b828eb551 |
| 4.19 | 7.1.5 | 077a7bc1c32d |
| 4.19 | 7.2 | f3ad1c87d820 |
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 in uniphier_spi_probe() on Socionext UniPhier embedded SoCs; uniphier_spi_handler() runs during platform driver initialization at boot/module load, not via network protocols, remote packets, or runtime SPI syscalls/ioctls.
- AC:LAttack complexity, low
- Commit and reporter confirm the SPI controller IRQ may assert immediately after devm_request_irq(); stale or pending SSI status on warm reboot can invoke complete() on uninitialized xfer_done without attacker luck.
- PR:NPrivileges required, none
- uniphier_spi_probe() has no credential or capability checks before devm_request_irq(); on affected UniPhier boards the vulnerable probe sequence runs automatically during kernel boot without the attacker holding Linux privileges.
- UI:NUser interaction, none
- No victim action is required; a pending SPI controller interrupt during driver probe at boot or reboot can trigger the uninitialized complete() path without opening /dev/spidev*, mounting filesystems, or other user operations.
- S:UScope, unchanged
- Impact is kernel panic from uninitialized completion/spinlock handling within the host kernel; this is not a VM escape, hypervisor bypass, IOMMU violation, or sandbox boundary crossing on embedded UniPhier systems.
- C:HConfidentiality impact, high
- complete() takes an uninitialized wait.lock and swake_up_locked() walks a zeroed task_list, causing KASAN wild-memory-access and invalid kernel memory reads beyond a strictly bounded NULL fault.
- I:HIntegrity impact, high
- Calling complete() on an uninitialized completion corrupts spinlock/wait-queue metadata in uniphier_spi_priv; KASAN-reported undefined behavior in IRQ context can corrupt adjacent kzalloc slab data and enable further kernel control primitives.
- A:HAvailability impact, high
- KASAN wild-memory-access and NULL list dereference in uniphier_spi_handler() during probe cause kernel oops/panic on affected UniPhier embedded devices, denying all system availability until reboot.