Kernel disclosure and memory exhaustion via recovery response
Published Nov 19, 2024 · Updated Aug 5, 2026
Out-of-bounds read and memory leak in Linux 5.1 and later affected branches allow physically proximate attackers to disclose data and exhaust memory. iwl_mvm_send_recovery_cmd() reads a 32-bit status without validating the response length and fails to free the response page. Malformed 802.11 frames can provoke automatic firmware recovery, leaking up to four kernel bytes to the log, disconnecting Wi-Fi, and exhausting memory when repeated.
Summary
What happened
Out-of-bounds read and memory leak in Linux 5.1 and later affected branches allow physically proximate attackers to disclose data and exhaust memory. iwl_mvm_send_recovery_cmd() reads a 32-bit status without validating the response length and fails to free the response page. Malformed 802.11 frames can provoke automatic firmware recovery, leaking up to four kernel bytes to the log, disconnecting Wi-Fi, and exhausting memory when repeated.
The record
- CVE
- CVE-2024-53059
- Published
- Nov 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- T1499.002
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 19, 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=0 <*
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
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