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

CVE record · `CVE-2026-74279`

- **Identifiers:** `CVE-2026-74279`
- **State:** Confirmed
- **Severity:** CVSS 10.0 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 15 Aug 2026, 05:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 10.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before 23c6174e48f66fc10b998b0acdb406cb0caf5c80` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before 23d3a7e896a1fe2d7a6bcb42f093948b79f8a198` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before 28141f95ae93b18f9bfde953cb787fcb151fb9da` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before 8afd1007ef79898a6e010eaade97097e49405fce` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before 3b8a1e1f4e4071a62b20374028744e8cc8310d48` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before fb4d57b83356d4bd411b45ede3024e0ff42c9b5e` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before d319b83b97b3585550d9ae592dfa78c755b6129e` (git)
  - affected: `c694b233295b99c33dd5ac28aede9f171f5a6862 to before 9dbf173bd32d5f81b005008b682bfb50aa093455` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.11`
  - unaffected: `before 4.11` (semver)
  - unaffected: `5.10.261 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.212 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.178 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.145 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.97 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.40 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.5 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0076, the 55th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 15 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-74279](https://www.cve.org/CVERecord?id=CVE-2026-74279)
- [NVD: CVE-2026-74279](https://nvd.nist.gov/vuln/detail/CVE-2026-74279)

### References from the CNA

- <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>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-74279>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-74279/>. Everything for agents: <https://agentprime.io/llms.txt>.
