Look up another CVE · open CVE-2026-74280 in the interactive tracker
CVE-2026-74280
crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/crypto. 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-74280 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 sg_cleanup path used list[i] instead of list[j] when unmapping DMA buffers, leaking successfully mapped entries and repeatedly unmapping the failed one.
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/crypto/marvell/octeontx/otx_cptvf_reqmgr.c
- What this is
- MARVELL CRYPTO DRIVERMAINTAINERS section matched on drivers/crypto/marvell/ · linux-crypto@vger.kernel.org · Maintained
- Kernel module
- none to look for. The file would have gone into octeontx_cptvf, and Debian does not compile it into that module, so finding octeontx_cptvf in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_CRYPTO|CONFIG_CRYPTO_DEV_MARVELL|CONFIG_CRYPTO_DEV_OCTEONTX_CPT' /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_CRYPTO, CONFIG_CRYPTO_DEV_MARVELL, CONFIG_CRYPTO_DEV_OCTEONTX_CPT
- 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
- 10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- network (AV:N)source
- EPSS
- 0.76%, higher than 54.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/crypto
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.7 | 5.10.261 | 97f150ba3e37 |
| 5.7 | 5.15.212 | 8a0db9fad3c9 |
| 5.7 | 6.1.178 | 8d301e5a5117 |
| 5.7 | 6.6.145 | ed374dbc70c1 |
| 5.7 | 6.12.97 | 6c721a3e4334 |
| 5.7 | 6.18.40 | 5f99a396f706 |
| 5.7 | 7.1.5 | acff30cfc0d7 |
| 5.7 | 7.2 | 7891c64c0520 |
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:NAttack vector, network
- On OcteonTX/Thunder network appliances, remote peers reach setup_sgio_components() through inbound IPsec ESP or kTLS decryption that offloads AEAD/skcipher to the Marvell CPT VF before any peer authentication.
- AC:LAttack complexity, low
- An attacker can reliably force the buggy sg_cleanup path by submitting heavily fragmented scatter-gather crypto requests that exhaust DMA/IOMMU mappings, causing dma_map_single() to fail at index i>=1 while earlier entries remain mapped.
- PR:NPrivileges required, none
- Inbound network decryption invokes CPT hardware offload without attacker credentials; no init-namespace root or CAP_NET_ADMIN is required on an already configured VPN/TLS endpoint to deliver ciphertext that reaches this driver.
- UI:NUser interaction, none
- Exploitation requires only automated kernel crypto processing of attacker-supplied ciphertext or AF_ALG requests; no victim mount, file open, or other interactive action is needed.
- S:CScope, changed
- The flaw leaks DMA_BIDIRECTIONAL IOMMU mappings for the CPT PCI device, crossing the intended DMA boundary between host memory and hardware crypto offload rather than staying within a single software security scope.
- C:HConfidentiality impact, high
- Leaked bidirectional IOMMU mappings leave previously mapped pages device-readable after logical cleanup, enabling memory disclosure when stale mappings persist or interact with subsequent CPT DMA activity under resource pressure.
- I:HIntegrity impact, high
- Unreleased DMA_BIDIRECTIONAL mappings and repeated bogus dma_unmap_single() calls on the failed entry can corrupt IOMMU bookkeeping and allow the CPT device to perform unintended DMA writes to host memory outside the aborted request buffers.
- A:HAvailability impact, high
- Each triggered failure leaks IOMMU mappings and may WARN or panic on invalid unmaps, causing gradual DMA resource exhaustion or immediate kernel crashes that deny crypto and overall system availability on affected OcteonTX systems.