Kernel panic via unsafe LDR uprobe simulation
Published Nov 5, 2024 · Updated Aug 5, 2026
Improper user-memory access in affected arm64 Linux kernel releases from 4.10 allows local users to crash or panic the kernel through uprobes. The simulate_ldr_literal() and simulate_ldrsw_literal() paths reuse plain C loads without user-access helpers or exception-table entries, so a fault is treated as an unintended kernel access. Reaching the fault requires tracing privilege to register the uprobe, after which a local user's execution can kill the kernel thread and trigger a lockup or panic.
Summary
What happened
Improper user-memory access in affected arm64 Linux kernel releases from 4.10 allows local users to crash or panic the kernel through uprobes. The simulate_ldr_literal() and simulate_ldrsw_literal() paths reuse plain C loads without user-access helpers or exception-table entries, so a fault is treated as an unintended kernel access. Reaching the fault requires tracing privilege to register the uprobe, after which a local user's execution can kill the kernel thread and trigger a lockup or panic.
The record
- CVE
- CVE-2024-50099
- Published
- Nov 5, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 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=4.10
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <20cde998315a3d2df08e26079a3ea7501abce6db
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <3728b4eb27910ffedd173018279a970705f2e03a
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <9f1e7735474e7457a4d919a517900e46868ae5f6
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <acc450aa07099d071b18174c22a1119c57da8227
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <ad4bc35a6d22e9ff9b67d0d0c38bce654232f195
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <ae743deca78d9e4b7f4f60ad2f95e20e8ea057f9
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <bae792617a7e911477f67a3aff850ad4ddf51572
- Affected versionversion=9842ceae9fa8deae141533d52a6ead7666962c09 <cc86f2e9876c8b5300238cec6bf0bd8c842078ee
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