From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74280: crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
Date: Sat, 15 Aug 2026 15:10:07 +0900 [thread overview]
Message-ID: <2026081546-CVE-2026-74280-623d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
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.
The Linux kernel CVE team has assigned CVE-2026-74280 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 5.10.261 with commit 97f150ba3e372256eabb93bd80c2cf3740077fb5
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 5.15.212 with commit 8a0db9fad3c97e6447a92417cb95d7c55eaa9530
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 6.1.178 with commit 8d301e5a51173ba56ce4f632a2a33bf6b14b0fcf
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 6.6.145 with commit ed374dbc70c10c4a864414b3d9c257faec8fd485
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 6.12.97 with commit 6c721a3e43344f8560ee4ef506fc1f72b4646dcd
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 6.18.40 with commit 5f99a396f706afc749448659d1565991330e4f71
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 7.1.5 with commit acff30cfc0d72465b51b0bfdf019f1cb54e15314
Issue introduced in 5.7 with commit 10b4f09491bfeb0b298cb2f49df585510ee6189a and fixed in 7.2-rc1 with commit 7891c64c0520519782470ba29bac8a5761e295d8
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-74280
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/marvell/octeontx/otx_cptvf_reqmgr.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/97f150ba3e372256eabb93bd80c2cf3740077fb5
https://git.kernel.org/stable/c/8a0db9fad3c97e6447a92417cb95d7c55eaa9530
https://git.kernel.org/stable/c/8d301e5a51173ba56ce4f632a2a33bf6b14b0fcf
https://git.kernel.org/stable/c/ed374dbc70c10c4a864414b3d9c257faec8fd485
https://git.kernel.org/stable/c/6c721a3e43344f8560ee4ef506fc1f72b4646dcd
https://git.kernel.org/stable/c/5f99a396f706afc749448659d1565991330e4f71
https://git.kernel.org/stable/c/acff30cfc0d72465b51b0bfdf019f1cb54e15314
https://git.kernel.org/stable/c/7891c64c0520519782470ba29bac8a5761e295d8
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=2026081546-CVE-2026-74280-623d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.