CVE-2026-68177
Last modified
CVE-2026-68177 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: tracing: Delay module ref count for "enable_event" trigger Triggers are now delayed from freeing, but can still be triggered until after the RCU grace period has ended. The freeing of the enable_event data is put into the private_data_free() 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 trace_event_put_ref() that releases the module into the delayed callback so that the module can not be removed until any reference to its events are finished.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Delay module ref count for "enable_event" trigger Triggers are now delayed from freeing, but can still be triggered until after the RCU grace period has ended. The freeing of the enable_event data is put into the private_data_free() 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 trace_event_put_ref() that releases the module into the delayed callback so that the module can not be removed until any reference to its events are finished.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 61d445af0a7c70018111919e47beaaee15653f2f, < 159fdc3e01dca5fdbc412fcd8b239895733a270d; >= 61d445af0a7c70018111919e47beaaee15653f2f, < e091351b38818ef620d27f44f4bfd625f13afbff |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68177?
How severe is CVE-2026-68177?
How do I fix CVE-2026-68177?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68171Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-68172In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-68173In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-68174In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68175In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68176In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68178In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-68179In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-6818The VikBooking Hotel Booking Engine & PMS plugin for WordPre…7.2
- CVE-2026-68180In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68181In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68182In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68177?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
