Kernel crash via stack-allocated CPU mask
Published Jul 29, 2024 · Updated May 12, 2026
Stack overflow in the Linux dpaa2 Ethernet driver from 4.16 allows local users to crash the kernel under affected configurations. The update_xps function places an explicit CPU mask on the kernel stack instead of using cpumask_var allocation, so a large mask can exhaust stack space. Reachability requires the dpaa2 driver and CONFIG_CPUMASK_OFFSTACK=y; public sources do not identify the operation that reaches update_xps or demonstrate exploitation.
Summary
What happened
Stack overflow in the Linux dpaa2 Ethernet driver from 4.16 allows local users to crash the kernel under affected configurations. The update_xps function places an explicit CPU mask on the kernel stack instead of using cpumask_var allocation, so a large mask can exhaust stack space. Reachability requires the dpaa2 driver and CONFIG_CPUMASK_OFFSTACK=y; public sources do not identify the operation that reaches update_xps or demonstrate exploitation.
The record
- CVE
- CVE-2024-42093
- Published
- Jul 29, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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