tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions (CVE-2026-80689) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80689

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

Answer in brief

CVE-2026-80689 records a Unknown severity vulnerability in tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Aug 28, 2026Source checked Aug 28, 2026First seen by HOL Aug 28, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=f984b51e0779a6dd30feedc41404013ca54e5d05 <876014b4eeb927146430e7591cf959a7ceb8d64a \|\| >=f984b51e0779a6dd30feedc41404013ca54e5d05 <a20a0010eb6485f60cd64e15ebc85a4bd388642e \|\| >=f984b51e0779a6dd30feedc41404013ca54e5d05 <60234845142fddb27db89ebc00a65178421fb3a4 \|\| >=f984b51e0779a6dd30feedc41404013ca54e5d05 <12b80cdbc54cf615b4717a4e8180063408091ea2	876014b4eeb927146430e7591cf959a7ceb8d64a, a20a0010eb6485f60cd64e15ebc85a4bd388642e, 60234845142fddb27db89ebc00a65178421fb3a4, 12b80cdbc54cf615b4717a4e8180063408091ea2
Linux/Linuxgeneric	2.6.27	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 876014b4eeb927146430e7591cf959a7ceb8d64a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 28, 2026

Sources and claim methodology

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

Quoted source text, attributed separately from HOL analysis.