CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free
can: hi311x: hi3110canist(): fix potential use-after-free
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
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.137-1Fixed in 6.1.135-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch a22bd630cfff - Configuration
In can: hi311x hi3110_can_ist(), postpone the netif_rx() call when performing txerr and rxerr reporting so that error count information is not added to the CAN frame after netif_rx(), avoiding a potential use-after-free.
CAN driver (hi311x: hi3110_can_ist()) netif_rx() call timing = postpone netif_rx() invocation in case of txerr and rxerr reporting
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56651?
CVE-2024-56651 is a critical vulnerability due to a potential use-after-free in the Linux kernel.
How do I fix CVE-2024-56651?
To fix CVE-2024-56651, update your Linux kernel to a version that addresses this vulnerability.
What versions of the Linux kernel are affected by CVE-2024-56651?
CVE-2024-56651 affects multiple versions of the Linux kernel, specifically from version 4.14.291 to 6.13-rc1.
Can CVE-2024-56651 lead to system stability issues?
Yes, CVE-2024-56651 can lead to system instability and exploitation due to the use-after-free vulnerability.
Is there a workaround for CVE-2024-56651?
There are no confirmed workarounds for CVE-2024-56651 other than applying the available patches.