From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64018: net: mana: validate rx_req_idx to prevent out-of-bounds array access
Date: Sun, 19 Jul 2026 17:38:00 +0200 [thread overview]
Message-ID: <2026071901-CVE-2026-64018-43bb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: mana: validate rx_req_idx to prevent out-of-bounds array access
In mana_hwc_rx_event_handler(), rx_req_idx is derived from
sge->address in DMA-coherent memory. In Confidential VMs
(SEV-SNP/TDX), this memory is shared unencrypted and HW can modify
WQE contents at any time. No bounds check exists on rx_req_idx,
which can lead to an out-of-bounds access into reqs[].
Add bounds check on rx_req_idx in mana_hwc_rx_event_handler() before
using it to index the reqs[] array.
The Linux kernel CVE team has assigned CVE-2026-64018 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 5.15.209 with commit 5ddc715324badd7f2641bc177db1d027b402adae
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 6.1.175 with commit ff1d5af207bcea857d45fe81505f1bc4b29eaef0
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 6.6.142 with commit 01f7f893d5e1baae995beeb86cd0f3e6bb2a3b01
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 6.12.92 with commit 763a372d344fb12fae566d36ddb46e92454ad58c
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 6.18.34 with commit fa627a5eaa83fc0261f44ef3769693b886ca6e27
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 7.0.11 with commit 355e9f2b2a7887ca38100127989af3e422ba71d0
Issue introduced in 5.13 with commit ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and fixed in 7.1 with commit b809d0409991b75a6cff846a5ac27c3062953f84
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-64018
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/net/ethernet/microsoft/mana/hw_channel.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/5ddc715324badd7f2641bc177db1d027b402adae
https://git.kernel.org/stable/c/ff1d5af207bcea857d45fe81505f1bc4b29eaef0
https://git.kernel.org/stable/c/01f7f893d5e1baae995beeb86cd0f3e6bb2a3b01
https://git.kernel.org/stable/c/763a372d344fb12fae566d36ddb46e92454ad58c
https://git.kernel.org/stable/c/fa627a5eaa83fc0261f44ef3769693b886ca6e27
https://git.kernel.org/stable/c/355e9f2b2a7887ca38100127989af3e422ba71d0
https://git.kernel.org/stable/c/b809d0409991b75a6cff846a5ac27c3062953f84
reply other threads:[~2026-07-19 15:41 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=2026071901-CVE-2026-64018-43bb@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.