Kernel warning via invalid per-CPU kthread rebinding
Published Oct 21, 2024 · Updated May 11, 2026
Improper state handling in the kthread subsystem of affected Linux releases allows local users to trigger a kernel warning during teardown. The kthread_stop() path invokes kthread_unpark() even when a per-CPU task is already unparked, causing kthread_bind() to process a task that is neither inactive nor parked. Reachability requires local low-privileged access and a teardown path that stops an already unparked per-CPU kthread; published evidence shows a warning, not data exposure or code execution.
Summary
What happened
Improper state handling in the kthread subsystem of affected Linux releases allows local users to trigger a kernel warning during teardown. The kthread_stop() path invokes kthread_unpark() even when a per-CPU task is already unparked, causing kthread_bind() to process a task that is neither inactive nor parked. Reachability requires local low-privileged access and a teardown path that stops an already unparked per-CPU kthread; published evidence shows a warning, not data exposure or code execution.
The record
- CVE
- CVE-2024-50019
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.11
- Affected versionversion=5c25b5ff89f004c30b04759dc34ace8585a4085f <19a5029981c87c2ad0845e713837faa88f5d8e2b
- Affected versionversion=5c25b5ff89f004c30b04759dc34ace8585a4085f <214e01ad4ed7158cab66498810094fac5d09b218
- Affected versionversion=5c25b5ff89f004c30b04759dc34ace8585a4085f <40a6e660d2a3a7a5cb99f0b8ff4fb41bad039f68
- Affected versionversion=5c25b5ff89f004c30b04759dc34ace8585a4085f <8608196a155cb6cfae04d96b10a2652d0327e33f
- Affected versionversion=5c25b5ff89f004c30b04759dc34ace8585a4085f <cda5423c1a1c906062ef235c940f249b97d9d135
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
No sourced classifications are available.
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