Kernel-memory corruption via post-delivery CAN frame write
Published Dec 27, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux hi311x CAN driver allows physically proximate attackers to corrupt kernel memory through CAN bus error frames. In hi3110_can_ist(), netif_rx() can consume or free an skb before the driver appends txerr or rxerr counters to that same buffer. Exploitation requires an HI-3110 controller on a shared CAN segment, where induced error-state transitions trigger writes into freed or reused kernel memory.
Summary
What happened
Use-after-free in the Linux hi311x CAN driver allows physically proximate attackers to corrupt kernel memory through CAN bus error frames. In hi3110_can_ist(), netif_rx() can consume or free an skb before the driver appends txerr or rxerr counters to that same buffer. Exploitation requires an HI-3110 controller on a shared CAN segment, where induced error-state transitions trigger writes into freed or reused kernel memory.
The record
- CVE
- CVE-2024-56651
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=22e382d47de09e865a9214cc5c9f99256e65deaa
- Affected versionversion=303733fdab728d34708014b3096dc69ebae6e531
- Affected versionversion=330b0ac34beec4fef8b002549af5bc6d0b6f0836
- Affected versionversion=410054f1cf75378a6f009359e5952a240102a1a2
- Affected versionversion=4.14.291 <4.15
- Affected versionversion=4.19.256 <4.20
- Affected versionversion=5.10.137 <5.11
- Affected versionversion=5.15.61 <5.16
- Affected versionversion=5.18.18 <5.19
- Affected versionversion=5.19.2 <5.20
- Affected versionversion=5.4.211 <5.5
- Affected versionversion=6.0
- Affected versionversion=a22bd630cfff496b270211745536e50e98eb3a45 <1128022009444faf49359bd406cd665b177cb643
- Affected versionversion=a22bd630cfff496b270211745536e50e98eb3a45 <4ad77eb8f2e07bcfa0e28887d3c7dbb732d92cc1
- Affected versionversion=a22bd630cfff496b270211745536e50e98eb3a45 <9ad86d377ef4a19c75a9c639964879a5b25a433b
- Affected versionversion=a22bd630cfff496b270211745536e50e98eb3a45 <bc30b2fe8c54694f8ae08a5b8a5d174d16d93075
- Affected versionversion=d20bf7e76136fd4c1e47502a1f5773f2290013ed
- Affected versionversion=dcfcd5fc999b1eb7946de1fd031bc3aaf224c5ae
- Affected versionversion=f3d865a6b791abbc874739ed702ae64ad2607511
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo