tracing: Drain deferred trigger frees if kthread creation fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tracing: Drain deferred trigger frees if kthread creation fails
Boot-time trigger registration can fail before the trigger-data cleanup kthread exists. Deferring those frees until late init is fine, but the post-boot fallback must still drain the deferred list if kthread creation never succeeds.
Otherwise, boot-deferred nodes can accumulate on trigger_data_free_list, later frees fall back to synchronously freeing only the current object, and the older queued entries are leaked forever.
To trigger this, add the following to the kernel command line:
trace_event=sched_switch trace_trigger=sched_switch.traceon,sched_switch.traceon
The second traceon trigger will fail and be freed. This triggers a NULL pointer dereference and crashes the kernel.
Keep the deferred boot-time behavior, but when kthread creation fails, drain the whole queued list synchronously. Do the same in the late-init drain path so queued entries are not stranded there either.
From the CVE record · Linux
The Linux kernel’s tracing trigger cleanup can leave deferred frees queued if its cleanup thread fails to start. With the specified boot-time tracing triggers configured, a failing second trigger can cause a NULL pointer dereference and crash the kernel. The input does not establish whether an attacker can trigger this remotely or what privileges are required to change the kernel command line.
Engineers running the Linux kernel with boot-time tracing triggers should check their versions against the vendor advisory; affected versions were not provided.