CVE-2025-38539
BaseFortify
Publication date: 2025-08-16
Last updated on: 2025-11-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.1.153-1 |
| linux | linux_kernel | 5.10.244-1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's tracing subsystem when two modules are loaded simultaneously. Both modules add trace events to a shared list without proper synchronization, which can corrupt the list and cause the kernel to crash. The issue arises because the code modifying the trace printk format strings does not hold the necessary write lock (trace_event_sem) while adding new events, leading to unsafe concurrent modifications.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash if two modules are loaded at the same time, leading to system instability or downtime. Such crashes can disrupt services, cause data loss, or require system reboots, impacting system reliability and availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix which adds down_write(trace_event_sem) when adding trace events. This ensures proper locking and prevents kernel crashes caused by concurrent module loading and trace event additions.