From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46249: octeontx2-af: Fix PF driver crash with kexec kernel booting
Date: Wed, 3 Jun 2026 17:49:38 +0200 [thread overview]
Message-ID: <2026060334-CVE-2026-46249-ade7@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: Fix PF driver crash with kexec kernel booting
During a kexec reboot the hardware is not power-cycled, so AF state from
the old kernel can persist into the new kernel. When AF and PF drivers
are built as modules, the PF driver may probe before AF reinitializes
the hardware.
The PF driver treats the RVUM block revision as an indication that AF
initialization is complete. If this value is left uncleared at shutdown,
PF may incorrectly assume AF is ready and access stale hardware state,
leading to a crash.
Clear the RVUM block revision during AF shutdown to avoid PF
mis-detecting AF readiness after kexec.
The Linux kernel CVE team has assigned CVE-2026-46249 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 5.10.252 with commit b7605b9301abc18fbbf2b0e23fdd281fc768955d
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 5.15.202 with commit 9769a09afda20a006b528b9e723effcae45965b2
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 6.1.165 with commit 57821d1436ba1c6a6973aa32d54166fdec35558c
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 6.6.128 with commit 8b5ed7c5417b7013d35b6f2507dab739013ba1a9
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 6.12.75 with commit 7d56ba306e93d04696718963fb4cda2883ee7585
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 6.18.14 with commit 9c3398e5b3a914b74276d44ab54c49123b89c61a
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 6.19.4 with commit 1370736836a18b5e0cd74bcc9cffe11d21f1fe79
Issue introduced in 4.20 with commit 54494aa5d1e68945dc79feb7c8461cd382e11d8a and fixed in 7.0 with commit 2d2d574309e3ae84ee794869a5da8b4c38753a94
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-46249
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/marvell/octeontx2/af/rvu.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/b7605b9301abc18fbbf2b0e23fdd281fc768955d
https://git.kernel.org/stable/c/9769a09afda20a006b528b9e723effcae45965b2
https://git.kernel.org/stable/c/57821d1436ba1c6a6973aa32d54166fdec35558c
https://git.kernel.org/stable/c/8b5ed7c5417b7013d35b6f2507dab739013ba1a9
https://git.kernel.org/stable/c/7d56ba306e93d04696718963fb4cda2883ee7585
https://git.kernel.org/stable/c/9c3398e5b3a914b74276d44ab54c49123b89c61a
https://git.kernel.org/stable/c/1370736836a18b5e0cd74bcc9cffe11d21f1fe79
https://git.kernel.org/stable/c/2d2d574309e3ae84ee794869a5da8b4c38753a94
reply other threads:[~2026-06-03 16:04 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=2026060334-CVE-2026-46249-ade7@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