data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2025-71188 in the interactive tracker

CVE-2025-71188

dmaengine: lpc18xx-dmamux: fix device leak on route allocation

EPSS 0.2%

Published 2026-01-31 (9 months ago) by the Linux kernel CNA. Subsystem drivers/dma. 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-2025-71188 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

ReleaseStatus VersionWhat this means
Debian 12bookwormwon't fix6.1.190-1Debian has decided against an update for bookworm: Arm v7-M not a supported architecture. Moving to a newer release is the way to get the fix.
Debian 13trixiewon't fix6.12.113-1Debian has decided against an update for trixie: Arm v7-M not a supported architecture. Moving to a newer release is the way to get the fix.
Debian 14forkyfixed6.18.8-1Update the kernel and reboot. Fixed in 6.18.8-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.18.8-1Update the kernel and reboot. Fixed in 6.18.8-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

Make sure to drop the reference taken when looking up the DMA mux platform device during route allocation. Note that holding a reference to a device does not prevent its driver data from going away so there is no point in keeping 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/dma/lpc18xx-dmamux.c

What this is
DMA GENERIC OFFLOAD ENGINE SUBSYSTEMMAINTAINERS section matched on drivers/dma/ · dmaengine@vger.kernel.org · Maintained
Kernel module
none to look for. The file would have gone into lpc18xx_dmamux, and Debian does not compile it into that module, so finding lpc18xx_dmamux in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_DMADEVICES|CONFIG_LPC18XX_DMAMUX' /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_DMADEVICES, CONFIG_LPC18XX_DMAMUX
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-01-31 (9 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.21%, higher than 10.2% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/dma

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
4.35.10.2493d396ebfb304
4.35.15.199499ddae78c4b
4.36.1.162adef147a8d8c
4.36.6.1229fba97baa520
4.36.12.67992eb8055a6e
4.36.18.71e47d80f6720
4.36.19d4d63059dee7

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2025-71188, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.