tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f984b51e0779a6dd30feedc41404013ca54e5d05 · < a20a0010eb6485f60cd64e15ebc85a4bd388642e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions
mmio_trace_rw() and mmio_trace_mapping() retrieve mmio_trace_array into tr and pass it to __trace_mmiotrace_rw() and __trace_mmiotrace_map(). If these functions are invoked while mmio_trace_array is NULL (e.g. before initialization or after disabled), accessing tr->array_buffer.buffer will result in a NULL pointer dereference crash.
Fix this by adding an explicit NULL check for tr at the beginning of __trace_mmiotrace_rw() and __trace_mmiotrace_map().
From the CVE record · Linux
The Linux kernel's mmiotrace logging functions can dereference a NULL pointer and crash if called before mmio_trace_array is initialized or after it is disabled. The input does not establish whether an attacker can trigger this condition, or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels with mmiotrace should check their kernel versions; affected versions are not specified.