Kernel crash via concurrent sysctl writes
Published Jun 18, 2025 · Updated Aug 15, 2026
Race condition in Linux arm64 instruction-emulation sysctls allows local users to crash the kernel through concurrent writes. The emulation_proc_handler function temporarily replaces table->data before proc_dointvec_minmax uses it, so a simultaneous invocation can dereference a NULL pointer. Reaching the race requires local low-privileged sysctl write access and simultaneous writes; the demonstrated consequence is a kernel oops and service interruption.
Summary
What happened
Race condition in Linux arm64 instruction-emulation sysctls allows local users to crash the kernel through concurrent writes. The emulation_proc_handler function temporarily replaces table->data before proc_dointvec_minmax uses it, so a simultaneous invocation can dereference a NULL pointer. Reaching the race requires local low-privileged sysctl write access and simultaneous writes; the demonstrated consequence is a kernel oops and service interruption.
The record
- CVE
- CVE-2022-50206
- Published
- Jun 18, 2025
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=3.19
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <04549063d5701976034d8c2bfda3d3a8cbf0409f
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <07022e07017ee5540f5559b0aeb916e8383c1e1a
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <353b4673d01c512303c45cf2346f630cda73b5c9
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <6a2fd114678d7fc1b5a0f8865ae98f1c17787455
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <9d5fec6ba2e4117d196a8259ab54615ffe562460
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <af483947d472eccb79e42059276c4deed76f99a6
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <b51881b1da57fe9877125dfdd0aac5172958fcfd
- Affected versionversion=587064b610c703f259317d00dc37bf6d40f4fc74 <cc69ef95988b9ef2fc730ec452a7441efb90ef5e
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.
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