CVE-2026-80689

tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions

N/A
Published: August 28, 2026 at 06:52 AM UTC
Updated: September 14, 2026 at 01:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.27 ≤ v < 5.10.2702.6.27 ≤ v < 5.15.2212.6.27 ≤ v < 6.1.1882.6.27 ≤ v < 6.12.1032.6.27 ≤ v < 6.18.442.6.27 ≤ v < 6.6.1572.6.27 ≤ v < 7.1.82.6.27 ≤ v < 7.22.6.27f984b51e0779a6dd30feedc41404013ca54e5d05
Vendor states this is fixed in 12b80cdbc54cf615b4717a4e8180063408091ea2 (fixed)
Vendor states this is fixed in 2df964d141270c40f07547b0c2e0a51e2573d46d (fixed)
Vendor states this is fixed in 4e4ab09db7899d7f2d2293a18adf0fa200a27e73 (fixed)
Vendor states this is fixed in 60234845142fddb27db89ebc00a65178421fb3a4 (fixed)
Vendor states this is fixed in 6aee2d478545c089dd5d055d3c9f0c7ea034fb80 (fixed)
Vendor states this is fixed in 876014b4eeb927146430e7591cf959a7ceb8d64a (fixed)
Vendor states this is fixed in a20a0010eb6485f60cd64e15ebc85a4bd388642e (fixed)
Vendor states this is fixed in dc1b1a057b3bb901f83433700e604fe0ae67c5f2 (fixed)
Vendor states this is fixed in 2.6.27 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card