From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74279: crypto: cavium/cpt - fix DMA cleanup using wrong loop index
Date: Sat, 15 Aug 2026 15:10:06 +0900 [thread overview]
Message-ID: <2026081545-CVE-2026-74279-aec7@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-74279 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 5.10.261 with commit 23c6174e48f66fc10b998b0acdb406cb0caf5c80
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 5.15.212 with commit 23d3a7e896a1fe2d7a6bcb42f093948b79f8a198
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 6.1.178 with commit 28141f95ae93b18f9bfde953cb787fcb151fb9da
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 6.6.145 with commit 8afd1007ef79898a6e010eaade97097e49405fce
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 6.12.97 with commit 3b8a1e1f4e4071a62b20374028744e8cc8310d48
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 6.18.40 with commit fb4d57b83356d4bd411b45ede3024e0ff42c9b5e
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 7.1.5 with commit d319b83b97b3585550d9ae592dfa78c755b6129e
Issue introduced in 4.11 with commit c694b233295b99c33dd5ac28aede9f171f5a6862 and fixed in 7.2-rc1 with commit 9dbf173bd32d5f81b005008b682bfb50aa093455
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-74279
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/crypto/cavium/cpt/cptvf_reqmanager.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
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
reply other threads:[~2026-08-15 6:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081545-CVE-2026-74279-aec7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox