octeontx2-af: Fix PF driver crash with kexec kernel booting
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 54494aa5d1e68945dc79feb7c8461cd382e11d8a · < 9c3398e5b3a914b74276d44ab54c49123b89c61a| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
During a kexec reboot, the PF driver can mistake persistent hardware state for completed AF initialization and crash when it accesses stale state. This can occur when the AF and PF drivers are built as modules and PF probes before AF reinitializes the hardware; the input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the octeontx2 AF and PF drivers built as modules should check their deployments; affected versions are not specified.