CVE-2025-40021Published Oct 24, 2025 · Oct 24Updated Oct 28
tracing: dynevent: Add a missing lockdown check on dynevent
Linux
Unrated
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 · < b47c4e06687a5a7b6c6ef4bd303fcfe4430b26bb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tracing: dynevent: Add a missing lockdown check on dynevent
Since dynamic_events interface on tracefs is compatible with kprobe_events and uprobe_events, it should also check the lockdown status and reject if it is set.
From the CVE record · Linux
The Linux kernel's tracing dynamic_events interface lacks a lockdown check. A local user who can access that interface may use it while lockdown is enabled, when comparable kprobe_events and uprobe_events interfaces would reject the request.
Engineers running Linux kernels that expose the tracing dynamic_events interface should check whether their kernel is affected; affected versions were not specified.