CVE-2025-37938: tracing: Verify event formats that have "%*p.."
In the Linux kernel, the following vulnerability has been resolved:
tracing: Verify event formats that have "%p.."
The trace event verifier checks the formats of trace events to make sure that they do not point at memory that is not in the trace event itself or in data that will never be freed. If an event references data that was allocated when the event triggered and that same data is freed before the event is read, then the kernel can crash by reading freed memory.
The verifier runs at boot up (or module load) and scans the print formats of the events and checks their arguments to make sure that dereferenced pointers are safe. If the format uses "%p.." the verifier will ignore it, and that could be dangerous. Cover this case as well.
Also add to the sample code a use case of "%pbl".
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.92.2-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-37938?
The severity of CVE-2025-37938 is rated as medium, indicating a moderate level of risk.
How do I fix CVE-2025-37938?
To fix CVE-2025-37938, you should update the Linux kernel to the latest stable version where the vulnerability has been patched.
What types of systems are affected by CVE-2025-37938?
CVE-2025-37938 affects systems running the Linux kernel that utilize trace events.
What are the consequences of not addressing CVE-2025-37938?
Failing to address CVE-2025-37938 may allow unauthorized access or manipulation of trace events in the kernel.
Is CVE-2025-37938 present in older versions of the Linux kernel?
Yes, CVE-2025-37938 is present in earlier versions of the Linux kernel prior to the patch release.