CVE-2024-40968: MIPS: Octeon: Add PCIe link status check
In the Linux kernel, the following vulnerability has been resolved:
MIPS: Octeon: Add PCIe link status check
The standard PCIe configuration read-write interface is used to access the configuration space of the peripheral PCIe devices of the mips processor after the PCIe link surprise down, it can generate kernel panic caused by "Data bus error". So it is necessary to add PCIe link status check for system protection. When the PCIe link is down or in training, assigning a value of 0 to the configuration address can prevent read-write behavior to the configuration space of peripheral PCIe devices, thereby preventing kernel panic.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.99-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.9.7-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Configuration
Add a PCIe link status check so standard PCIe configuration-space reads and writes to peripheral devices are prevented when the link is down or in training, by assigning 0 to the configuration address.
Linux kernel MIPS Octeon PCIe PCIe link status check = Assign 0 to the PCIe configuration address when the link is down or in training
Event History
Frequently Asked Questions
What is the severity of CVE-2024-40968?
The severity of CVE-2024-40968 has not been explicitly rated but it involves the Linux kernel and MIPS architecture, which indicates a notable risk if exploited.
How do I fix CVE-2024-40968?
To fix CVE-2024-40968, you should update to the affected versions of the Linux kernel as specified in the vulnerability details.
What systems are affected by CVE-2024-40968?
CVE-2024-40968 affects systems running specific versions of the Linux kernel on MIPS architecture.
Is there a workaround for CVE-2024-40968?
Currently, there are no documented workarounds for CVE-2024-40968 outside of upgrading to the patched kernel versions.
When was CVE-2024-40968 discovered?
CVE-2024-40968 was disclosed as part of an update to the Linux kernel, the exact discovery date is not specified in the available information.