Dismissed
(max. allowed matches exceeded)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions
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().
References
Affected products
Linux
- ==2.6.27
- <12b80cdbc54cf615b4717a4e8180063408091ea2
- =<6.18.*
- =<6.12.*
- <876014b4eeb927146430e7591cf959a7ceb8d64a
- <60234845142fddb27db89ebc00a65178421fb3a4
- =<7.1.*
- <a20a0010eb6485f60cd64e15ebc85a4bd388642e
- =<*
- <2.6.27