Kernel fault via unchecked copy failure
Published Sep 17, 2025 · Updated Sep 17, 2025
Use of uninitialized memory in the Linux kernel allows local users to trigger a kernel fault through a malformed CAN BCM write. The bcm_tx_setup function copies a message into newly allocated op->frames storage, then compares its len field even when memcpy_from_msg fails, leaving that field uninitialized. Reaching the path requires local access to submit an asynchronous CAN BCM socket write; the demonstrated consequence is a KMSAN-detected fault, with no documented data disclosure or code execution.
Summary
What happened
Use of uninitialized memory in the Linux kernel allows local users to trigger a kernel fault through a malformed CAN BCM write. The bcm_tx_setup function copies a message into newly allocated op->frames storage, then compares its len field even when memcpy_from_msg fails, leaving that field uninitialized. Reaching the path requires local access to submit an asynchronous CAN BCM socket write; the demonstrated consequence is a KMSAN-detected fault, with no documented data disclosure or code execution.
The record
- CVE
- CVE-2023-53344
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 2025Record 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=4.8
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <2b4c99f7d9a57ecd644eda9b1fb0a1072414959f
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <2e6ad51c709fa794e0ce26003c9c9cd944e3383a
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <3fa0f1e0e31b1b73cdf59d4c36c7242e6ef821be
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <618b15d09fed6126356101543451d49860db4388
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <78bc7f0ab99458221224d3ab97199c0f8e6861f1
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <ab2a55907823f0bca56b6d03ea05e4071ba8535f
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <bf70e0eab64c625da84d9fdf4e84466b79418920
- Affected versionversion=6f3b911d5f29b98752e5da86a295210c0c4f4e14 <c11dbc7705b3739974ac31a13f4ab81e61a5fb07
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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