Skip to main content
VulnerabilityPublished Updated

CVE-2026-80689: Linux kernel · tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in dc1b1a057b3bb901f83433700e604fe0ae67c5f2 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:40 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in dc1b1a057b3bb901f83433700e604fe0ae67c5f2, a20a0010eb6485f60cd64e15ebc85a4bd388642e, 60234845142fddb27db89ebc00a65178421fb3a4 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ f984b51e0779a6dd30feedc41404013ca54e5d05, < dc1b1a057b3bb901f83433700e604fe0ae67c5f2
Fixed in
  • dc1b1a057b3bb901f83433700e604fe0ae67c5f2
LinuxLinuxAffected
  • ≥ f984b51e0779a6dd30feedc41404013ca54e5d05, < a20a0010eb6485f60cd64e15ebc85a4bd388642e
Fixed in
  • a20a0010eb6485f60cd64e15ebc85a4bd388642e
LinuxLinuxAffected
  • ≥ f984b51e0779a6dd30feedc41404013ca54e5d05, < 60234845142fddb27db89ebc00a65178421fb3a4
Fixed in
  • 60234845142fddb27db89ebc00a65178421fb3a4
LinuxLinuxAffected
  • ≥ f984b51e0779a6dd30feedc41404013ca54e5d05, < 876014b4eeb927146430e7591cf959a7ceb8d64a
Fixed in
  • 876014b4eeb927146430e7591cf959a7ceb8d64a
LinuxLinuxAffected
  • ≥ f984b51e0779a6dd30feedc41404013ca54e5d05, < 12b80cdbc54cf615b4717a4e8180063408091ea2
Fixed in
  • 12b80cdbc54cf615b4717a4e8180063408091ea2
LinuxLinuxAffected
  • ≥ f984b51e0779a6dd30feedc41404013ca54e5d05, < 6aee2d478545c089dd5d055d3c9f0c7ea034fb80
Fixed in
  • 6aee2d478545c089dd5d055d3c9f0c7ea034fb80

AI-suggested

A fix has been applied in the Linux kernel source code as indicated by multiple fixed commit versions. Users should update to a kernel version including these fixes to mitigate the issue. No additional mitigation is required beyond applying the official patch.

Description

A null pointer dereference vulnerability was identified in the Linux kernel's tracing/mmiotrace subsystem. The issue occurs because the logging functions did not check if the mmio_trace_array pointer was NULL before dereferencing it, which could cause a kernel crash. This was fixed by adding explicit NULL checks in the affected functions.

References

Community reviews

Loading reviews…