CVE-2024-56651: In the Linux kernel, the following vulnerability has been resolved: can: hi311x: hi3110_can_ist(): fix potential use-after-free The commit a22bd630c...

Description

In the Linux kernel, the following vulnerability has been resolved: can: hi311x: hi3110_can_ist(): fix potential use-after-free The commit a22bd630cfff ("can: hi311x: do not report txerr and rxerr during bus-off") removed the reporting of rxerr and txerr even in case of correct operation (i. e. not bus-off). The error count information added to the CAN frame after netif_rx() is a potential use after free, since there is no guarantee that the skb is in the same state. It might be freed or reused. Fix the issue by postponing the netif_rx() call in case of txerr and rxerr reporting.

Metrics

CVSS 3.1

7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

0.23%

13.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions	Update
Linux	Linux Kernel	>= 4.14.291, < 4.15	—
Linux	Linux Kernel	>= 4.19.256, < 4.20	—
Linux	Linux Kernel	>= 5.4.211, < 5.5	—
Linux	Linux Kernel	>= 5.10.137, < 5.11	—
Linux	Linux Kernel	>= 5.15.61, < 5.16	—
Linux	Linux Kernel	>= 5.18.18, < 5.19	—
Linux	Linux Kernel	>= 5.19.2, < 5.20	—
Linux	Linux Kernel	>= 6.0, < 6.1.120	—
Linux	Linux Kernel	>= 6.2, < 6.6.66	—
Linux	Linux Kernel	>= 6.7, < 6.12.5	—
Linux	Linux Kernel	6.13	Rc1

References

Timeline

Published: Dec 27, 2024
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2024-56651?

In the Linux kernel, the following vulnerability has been resolved: can: hi311x: hi3110_can_ist(): fix potential use-after-free The commit a22bd630cfff ("can: hi311x: do not report txerr and rxerr during bus-off") removed the reporting of rxerr and txerr even in case of correct operation (i. e. not bus-off). The error count information added to the CAN frame after netif_rx() is a potential use after free, since there is no guarantee that the skb is in the same state. It might be freed or reused. Fix the issue by postponing the netif_rx() call in case of txerr and rxerr reporting.

How severe is CVE-2024-56651?

CVE-2024-56651 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.23% probability of exploitation in the next 30 days.

How do I fix CVE-2024-56651?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.