tracing: Verify event formats that have "%*p.."
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5013f454a352cce8e62162976026a9c472595e42 · < ea8d7647f9ddf1f81e2027ed305299797299aa03| No fix yet |
| Linux Linux |
|
|
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".
From the CVE record · Linux
The Linux kernel trace event verifier can overlook pointer references in event formats that use "%*p..". If an event references data freed before the event is read, reading it can crash the kernel. The input does not establish an attacker access path or authentication requirement.
Engineers running Linux kernels with trace events should check their versions against the vendor advisory; affected versions are not specified.