Local kernel code execution via uninitialized ops pointer
Published Jul 25, 2025 · Updated Aug 5, 2026
Improper initialization in Linux irq_sim allows local users to execute kernel code or crash the host through a GPIO or IIO device. The irq_sim_work_ctx allocation uses kmalloc without clearing the ops member, so irq_sim_request_resources tests and calls stale function pointers. Reachability requires an enabled simulator and access to its local character device; a failed indirect call causes a kernel oops or panic, while heap grooming enables kernel control-flow hijacking.
Summary
What happened
Improper initialization in Linux irq_sim allows local users to execute kernel code or crash the host through a GPIO or IIO device. The irq_sim_work_ctx allocation uses kmalloc without clearing the ops member, so irq_sim_request_resources tests and calls stale function pointers. Reachability requires an enabled simulator and access to its local character device; a failed indirect call causes a kernel oops or panic, while heap grooming enables kernel control-flow hijacking.
The record
- CVE
- CVE-2025-38408
- Published
- Jul 25, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2025CVE 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=337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1 <186df821de0f34490ed5fc0861243748b2483861
- Affected versionversion=337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1 <19bd7597858dd15802c1d99fcc38e528f469080a
- Affected versionversion=337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1 <7f73d1def72532bac4d55ea8838f457a6bed955c
- Affected versionversion=337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1 <8a2277a3c9e4cc5398f80821afe7ecbe9bdf2819
- Affected versionversion=337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1 <c71aa4bb528ae6f8fd7577a0a39e5a03c60b04fb
- Affected versionversion=337cbeb2c13eb4cab84f576fd402d7ae4ed31ae1 <ec3656a8cb428d763def32bc2fa695f94be23629
- Affected versionversion=5.8
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