CVE-2026-68177: tracing: Delay module ref count for "enable_event" trigger
In the Linux kernel, the following vulnerability has been resolved:
tracing: Delay module ref count for "enableevent" trigger
Triggers are now delayed from freeing, but can still be triggered until after the RCU grace period has ended. The freeing of the enableevent data is put into the privatedatafree() callback, but the put of the module refcount is done immediately.
It is possible that if a module is removed that has an event that would enable (or disable) it is still active, it can read the data of the module after it is removed causing a use-after-free bug.
Move the traceeventputref() that releases the module into the delayed callback so that the module can not be removed until any reference to its events are finished.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68177?
CVE-2026-68177 has a risk score of 47, indicating a moderate severity level.
How do I fix CVE-2026-68177?
To fix CVE-2026-68177, update your Linux kernel to the latest version that addresses this vulnerability.
What impacts does CVE-2026-68177 have on system security?
CVE-2026-68177 may allow for use-after-free conditions, potentially leading to memory corruption and security vulnerabilities.
Which versions of the Linux kernel are affected by CVE-2026-68177?
CVE-2026-68177 affects the Linux kernel prior to its resolution in the latest security update.
Is CVE-2026-68177 actively exploited in the wild?
As of now, there is no indication that CVE-2026-68177 is actively exploited in the wild.