Look up another CVE · open CVE-2026-53057 in the interactive tracker
CVE-2026-53057
iommu/riscv: Add IOTINVAL after updating DDT/PDT entries
Published 2026-06-24 (4 months ago) by the Linux kernel CNA. Subsystem drivers/iommu. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-53057 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 | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.10-1 | Update the kernel and reboot. Fixed in 7.0.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Add riscv_iommu_iodir_iotinval() to perform required TLB and context cache invalidations after updating DDT or PDT entries, as mandated by the RISC-V IOMMU specification (Section 6.3.1 and 6.3.2).
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/iommu/riscv/iommu.c
- What this is
- RISC-V IOMMUMAINTAINERS section matched on drivers/iommu/riscv/ · iommu@lists.linux.dev · Maintained
Check it on the machine
grep -w CONFIG_RISCV_IOMMU /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 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 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- Y
- built in 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_RISCV_IOMMU
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-06-24 (4 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 6.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/iommu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.13 | 6.18.33 | 3f917d9bff68 |
| 6.13 | 7.0.10 | d99d1c13faa7 |
| 6.13 | 7.1 | f5c262b54497 |
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 vulnerable RISC-V IOMMU path is reached through local device/IOMMU management flows such as VFIO/iommufd domain attach, detach, or replacement for DMA-capable devices. It is not directly reachable from network packets.
- AC:LAttack complexity, low
- An attacker controlling an assigned DMA-capable device can prepopulate translation caches and trigger domain changes without needing to win an uncontrollable race. The bug is a missing required invalidation after DDT/PDT updates.
- PR:LPrivileges required, low
- Exploitation requires local access to a DMA-capable device or delegated VFIO/iommufd device ownership, which is commonly granted to non-root users or guest workloads. It does not require real init-namespace root once that device access exists.
- UI:NUser interaction, none
- No separate victim action is required after the attacker has device access. The attacker can trigger DMA and domain transitions directly through the local device management path.
- S:CScope, changed
- This is an IOMMU/DMA isolation failure, so stale translations can cross the intended device, guest, or host memory protection boundary. Kernel guidance treats IOMMU/DMA boundary bypass as scope changed.
- C:HConfidentiality impact, high
- Stale DDT/PDT-derived translations can allow a device to DMA-read memory belonging to a previous or different protection domain. In the severe reasonable VFIO or passthrough scenario, this can expose arbitrary host or other-guest memory.
- I:HIntegrity impact, high
- The same stale translations can permit DMA writes outside the attacker's assigned domain. That can corrupt host or other-guest memory and potentially alter privileged state.
- A:HAvailability impact, high
- Unauthorized DMA writes or stale-domain DMA after blocking/detach can corrupt critical memory and crash or hang the host or victim workload. Repeated triggering is feasible through local device control.