CVE-2025-38539
Last modified
CVE-2025-38539 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: tracing: Add down_write(trace_event_sem) when adding trace event When a module is loaded, it adds trace events defined by the module. It may also need to modify the modules trace printk formats to replace enum names with their values. If two modules are loaded at the same time, the adding of the event to the ftrace_events list can corrupt the walking of the list in the code that is modifying the printk format strings and crash the kernel. The addition of the event should take the trace_event_sem for write while it adds the new event. Also add a lockdep_assert_held() on that semaphore in __trace_add_event_dirs() as it iterates the list.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Add down_write(trace_event_sem) when adding trace event When a module is loaded, it adds trace events defined by the module. It may also need to modify the modules trace printk formats to replace enum names with their values. If two modules are loaded at the same time, the adding of the event to the ftrace_events list can corrupt the walking of the list in the code that is modifying the printk format strings and crash the kernel. The addition of the event should take the trace_event_sem for write while it adds the new event. Also add a lockdep_assert_held() on that semaphore in __trace_add_event_dirs() as it iterates the list.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 2.6.31, < 5.4.297 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.241 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.190 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.147 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.100 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.40 | — |
| Linux | Linux Kernel | >= 6.13, < 6.15.8 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlMailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38539?
How severe is CVE-2025-38539?
How do I fix CVE-2025-38539?
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 2025
- CVE-2025-38533In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38534In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38535In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38536In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38537In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38538In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-3854A vulnerability, which was classified as critical, was found…8.6
- CVE-2025-38540In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38541In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38542In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38543In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38544In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38539?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
