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

Look up another CVE · open CVE-2026-80556 in the interactive tracker

CVE-2026-80556

mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition

7.8 EPSS 0.2% AV:L

Published 2026-08-26 (2 months ago) by the Linux kernel CNA. Subsystem drivers/mmc. 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-80556 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 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixed6.12.105-1Update the kernel and reboot. Fixed in 6.12.105-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.10-1Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.10-1Update 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.12fixedDLA-4788-1 · 2026-09-19 · text6.12.107-1~deb12u1Update 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

In atmci_probe, &host->bh_work is bound with atmci_work_func, and atmci_interrupt, atmci_timeout_timer and atmci_dma_complete can all queue this work on system_bh_wq. If we remove the module, atmci_remove makes cleanup and the memory allocated for host with devm_kzalloc() is released after the remove callback returns, while the work mentioned above may still be pending or running. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | atmci_interrupt | queue_work(system_bh_wq, | &host->bh_work) atmci_remove | atmci_cleanup_slot(...) | atmci_writel(host, ATMCI_IDR, ~0UL) | timer_delete_sync(&host->timer) | dma_release_channel(host->dma.chan) | free_irq(platform_get_irq(pdev, 0), host) | | atmci_work_func | // use host // devm resources released after | // remove returns, host is freed | | // use host (use-after-free) Fix it by canceling the work after all the sources that can schedule it (IRQ handler, timeout timer and DMA completion callback) have been stopped, and before proceeding with the remaining cleanup in atmci_remove.

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/mmc/host/atmel-mci.c

What this is
MICROCHIP MMC/SD/SDIO MCI DRIVERMAINTAINERS section matched on drivers/mmc/host/atmel-mci.c · Maintained
Kernel module
none to look for. The file would have gone into atmel_mci, and Debian does not compile it into that module, so finding atmel_mci in lsmod would say nothing about this CVE.

Check it on the machine

grep -w CONFIG_MMC_ATMELMCI /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 switch
CONFIG_MMC_ATMELMCI

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-26 (2 months 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.17%, higher than 6.0% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/mmc

Upstream fixes

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

IntroducedFixed inCommit
2.6.276.12.10522aecf6c4721
2.6.276.18.46b5060ff2f546
2.6.277.1.107599a73ff66d
2.6.277.2c125ee35a49a

Debian advisories

AdvisoryDateShipped toDebian
DLA-4788-12026-09-19bookworm 6.12.107-1~deb12u1tracker

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 UAF is in atmci_remove() platform-driver teardown (rmmod/sysfs unbind) while atmci_work_func() runs from IRQ/DMA/timer-driven work queued via local /dev/mmcblk* block I/O; there is no network, Bluetooth, or remote protocol path into this driver.
AC:LAttack complexity, low
This is a classic removal-vs-workqueue race where the attacker controls both sides: concurrent mmcblk read/write (or SDIO traffic) schedules bh_work via atmci_interrupt/atmci_dma_complete/atmci_timeout_timer while timing driver unbind/rmmod, and can retry rapidly to win reliably.
PR:LPrivileges required, low
Per CNA driver-removal UAF precedent, an unprivileged local user with /dev/mmcblk* access can drive the IRQ/DMA/timer side via block I/O while teardown occurs (admin unbind, rmmod, or automated reload during maintenance/reboot); init-namespace root is not the minimum privilege bar.
UI:NUser interaction, none
No victim interaction is required; the attacker performs mmcblk I/O themselves (or sustains SDIO/MMC activity) and coordinates or piggybacks on driver removal without needing another user to mount media or click anything.
S:UScope, unchanged
Impact is kernel heap corruption and privilege escalation within the same kernel security boundary on the Atmel/Microchip embedded host; this is not a VM escape, IOMMU bypass, or cross-authority sandbox breakout.
C:HConfidentiality impact, high
atmci_work_func() dereferences the freed atmel_mci host (locks, mrq/data pointers, MMIO via host->regs); this kernel heap UAF enables arbitrary read primitives through controlled reuse of the freed structure.
I:HIntegrity impact, high
The UAF work handler performs MMIO writes (atmci_writel), manipulates mmc_request state, and invokes stop_transfer callbacks on attacker-influenced freed memory, enabling heap spraying and arbitrary kernel write/control-flow hijack.
A:HAvailability impact, high
Use-after-free in atmci_work_func() during driver removal can cause immediate kernel oops/panic from dereferencing freed host memory, and successful exploitation can crash or hang the system even when not leveraged for code execution.