octeontx2-af: Fix PF driver crash with kexec kernel booting
Summary
| CVE | CVE-2026-46249 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-03 18:16:25 UTC |
| Updated | 2026-06-03 18:16:25 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a b7605b9301abc18fbbf2b0e23fdd281fc768955d git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 9769a09afda20a006b528b9e723effcae45965b2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 57821d1436ba1c6a6973aa32d54166fdec35558c git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 8b5ed7c5417b7013d35b6f2507dab739013ba1a9 git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 7d56ba306e93d04696718963fb4cda2883ee7585 git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 9c3398e5b3a914b74276d44ab54c49123b89c61a git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 1370736836a18b5e0cd74bcc9cffe11d21f1fe79 git |
Not specified |
| CNA |
Linux |
Linux |
affected 54494aa5d1e68945dc79feb7c8461cd382e11d8a 2d2d574309e3ae84ee794869a5da8b4c38753a94 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.20 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.20 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.252 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.202 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.165 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.128 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.75 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.14 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.4 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/57821d1436ba1c6a6973aa32d54166fdec35558c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1370736836a18b5e0cd74bcc9cffe11d21f1fe79 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b7605b9301abc18fbbf2b0e23fdd281fc768955d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/8b5ed7c5417b7013d35b6f2507dab739013ba1a9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2d2d574309e3ae84ee794869a5da8b4c38753a94 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9c3398e5b3a914b74276d44ab54c49123b89c61a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9769a09afda20a006b528b9e723effcae45965b2 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7d56ba306e93d04696718963fb4cda2883ee7585 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.