Kernel memory overwrite via mismatched union clearing
Published Jun 19, 2024 · Updated May 11, 2026
Out-of-bounds write in the Linux kernel's carl9170 driver allows remote attackers to corrupt kernel memory via wireless traffic. The carl9170_tx_release() function clears pad and rate_driver_data separately because memset_after() used the status union view while the original pointer came from rate_driver_data, producing a fortified write-beyond-field condition. Reachability requires an active carl9170 wireless device and an affected kernel; the published assessment limits impact to memory integrity and service availability.
Summary
What happened
Out-of-bounds write in the Linux kernel's carl9170 driver allows remote attackers to corrupt kernel memory via wireless traffic. The carl9170_tx_release() function clears pad and rate_driver_data separately because memset_after() used the status union view while the original pointer came from rate_driver_data, producing a fortified write-beyond-field condition. Reachability requires an active carl9170 wireless device and an affected kernel; the published assessment limits impact to memory integrity and service availability.
The record
- CVE
- CVE-2024-38616
- Published
- Jun 19, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.17
- Affected versionversion=fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e <042a39bb8e0812466327a5102606e88a5a4f8c02
- Affected versionversion=fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e <066afafc10c9476ee36c47c9062527a17e763901
- Affected versionversion=fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e <0c38c9c460bb8ce8d6f6cf316e0d71a70983ec83
- Affected versionversion=fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e <13857683126e8a6492af73c74d702835f7a2175b
- Affected versionversion=fb5f6a0e8063b7a84d6d44ef353846ccd7708d2e <87586467098281f04fa93e59fe3a516b954bddc4
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.
Weakness, pattern, technique
No sourced classifications are available.
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