Answer in brief
CVE-2025-38539 records a Unknown severity vulnerability in tracing: Add down_write(trace_event_sem) when adding trace event. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38539 records a Unknown severity vulnerability in tracing: Add down_write(trace_event_sem) when adding trace event. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=110bf2b764eb6026b868d84499263cb24b1bcc8d <e70f5ee4c8824736332351b703c46f9469ed7f6c || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <db45632479ceecb669612ed8dbce927e3c6279fc || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <ca60064ea03f14e06c763de018403cb56ba3207d || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <6bc94f20a4c304997288f9a45278c9d0c06987d3 || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <33e20747b47ddc03569b6bc27a2d6894c1428182 || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <70fecd519caad0c1741c3379d5348c9000a5b29d || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df | e70f5ee4c8824736332351b703c46f9469ed7f6c, db45632479ceecb669612ed8dbce927e3c6279fc, ca60064ea03f14e06c763de018403cb56ba3207d, 7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b, 6bc94f20a4c304997288f9a45278c9d0c06987d3, 33e20747b47ddc03569b6bc27a2d6894c1428182, 70fecd519caad0c1741c3379d5348c9000a5b29d, b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df |
| Linux/Linuxgeneric | 2.6.31 | Not reported |
Published upstream
Aug 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=110bf2b764eb6026b868d84499263cb24b1bcc8d <e70f5ee4c8824736332351b703c46f9469ed7f6c || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <db45632479ceecb669612ed8dbce927e3c6279fc || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <ca60064ea03f14e06c763de018403cb56ba3207d || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <6bc94f20a4c304997288f9a45278c9d0c06987d3 || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <33e20747b47ddc03569b6bc27a2d6894c1428182 || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <70fecd519caad0c1741c3379d5348c9000a5b29d || >=110bf2b764eb6026b868d84499263cb24b1bcc8d <b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df | e70f5ee4c8824736332351b703c46f9469ed7f6c, db45632479ceecb669612ed8dbce927e3c6279fc, ca60064ea03f14e06c763de018403cb56ba3207d, 7803b28c9aa8d8bd4e19ebcf5f0db9612b0f333b, 6bc94f20a4c304997288f9a45278c9d0c06987d3, 33e20747b47ddc03569b6bc27a2d6894c1428182, 70fecd519caad0c1741c3379d5348c9000a5b29d, b5e8acc14dcb314a9b61ff19dcd9fdd0d88f70df |
| Linux/Linuxgeneric | 2.6.31 | Not reported |
Published upstream
Aug 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.