Look up another CVE · open CVE-2026-80752 in the interactive tracker
CVE-2026-80752
Input: psxpad-spi - set driver data before use
Published 2026-09-03 (2 months ago) by the Linux kernel CNA. Subsystem drivers/input. 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-80752 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.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-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
psxpad_spi_suspend() retrieves the controller state with spi_get_drvdata(), but probe never stores it, so suspend dereferences a NULL pointer. Store it during probe.
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/input/joystick/psxpad-spi.c
- What this is
- INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERSMAINTAINERS section matched on drivers/input/ · linux-input@vger.kernel.org · Maintained
- Kernel module
- none to look for. The file would have gone into psxpad_spi, and Debian does not compile it into that module, so finding psxpad_spi in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_INPUT|CONFIG_INPUT_JOYSTICK|CONFIG_JOYSTICK_PSXPAD_SPI' /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 5 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, sid, bookworm · linux-6.12n
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_INPUT, CONFIG_INPUT_JOYSTICK, CONFIG_JOYSTICK_PSXPAD_SPI
- 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
- 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.20%, higher than 8.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/input
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.12 | 5.10.266 | e980066e434a |
| 4.12 | 5.15.217 | 1bba6bd6861b |
| 4.12 | 6.1.184 | 86531cdfb3a0 |
| 4.12 | 6.6.153 | da6b8b05db0c |
| 4.12 | 6.12.105 | 1edcb7ffee7a |
| 4.12 | 6.18.46 | 8d622c58205a |
| 4.12 | 7.1.10 | 62e25677d144 |
| 4.12 | 7.2 | 732f38c36059 |
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
- The fault is reached only via the kernel system-sleep PM path (suspend/hibernate) calling dpm_suspend() -> psxpad_spi_suspend(); it is not triggered by network traffic, wireless frames, or SPI packet handling from a remote peer.
- AC:LAttack complexity, low
- On embedded retro consoles/arcade cabinets with a probed psxpad-spi controller, every system suspend deterministically calls psxpad_spi_suspend() with NULL drvdata and faults in psxpad_set_motor_level(); no race, heap layout, or rare timing is required beyond CONFIG_JOYSTICK_PSXPAD_SPI hardware being present.
- PR:NPrivileges required, none
- No Linux account is required on typical embedded/kiosk deployments: ACPI power-button sleep, lid-close policies, or automated idle suspend invoke the PM path without authenticated local userspace, and user namespaces cannot substitute for triggering host system sleep.
- UI:NUser interaction, none
- Exploitation requires only initiating or allowing a system suspend/hibernate cycle (power button, logind, or policy-driven sleep); no separate victim action such as opening a file, mounting a filesystem, or plugging in a controller at attack time is needed once the SPI pad is bound.
- S:UScope, unchanged
- The NULL dereference and resulting kernel oops/panic occur entirely within the same host kernel that owns the psxpad-spi driver; there is no VM escape, IOMMU/DMA boundary bypass, or cross-security-authority impact.
- C:HConfidentiality impact, high
- psxpad_spi_suspend() passes a NULL pad into psxpad_set_motor_level(), which performs kernel stores through a NULL structure pointer; this memory-unsafe dereference class can disclose kernel memory during fault/Oops handling or on mappings where low addresses are reachable, not merely a silent crash.
- I:HIntegrity impact, high
- The suspend path attempts writes to pad->motor1level and pad->motor2level via a NULL base pointer, constituting attempted kernel memory corruption that can yield further write primitives or control-flow hijack on configurations without strict NULL-page protection, beyond immediate denial of service.
- A:HAvailability impact, high
- The NULL pointer dereference in psxpad_set_motor_level() during psxpad_spi_suspend() causes a kernel Oops/panic that aborts or corrupts the suspend sequence, denying availability of a clean sleep/resume cycle on affected systems.