Quick answers
- Is CVE-2026-74279 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74279 being exploited in the wild.
- How severe is CVE-2026-74279?
- Critical severity, with a CVSS score of 10, published 15 August 2026.
- Which products and versions are affected?
- Linux Kernel affected versions with Cavium CPT driver (approximately 4.19 and later).
- Is there a fix for CVE-2026-74279?
- A patch was published on 2026-06-02. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-74279 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-74279?
- Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An off-by-one error in the sg_cleanup error path of the Cavium CPT virtual function driver uses the wrong loop index (list[i] instead of list[j]) when unmapping DMA buffers. This causes successfully mapped entries to remain mapped (leak) while the failed entry is unmapped repeatedly. The vulnerable code is in drivers/crypto/cavium/cpt/cptvf_reqmanager.c in the setup_sgio_components() function. Exploitation requires local kernel code execution to trigger the error path during DMA buffer setup. The fix corrects the index reference in two dma_unmap_single() calls to use the correct loop variable. Patches are available in the Linux kernel stable tree.
Affected products
- Linux Linux kernel affected versions with Cavium CPT driver (approximately 4.19 and later)
Timeline
- 2026-08-15: disclosed
- 2026-06-02: patched