Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < dc1b1a057b3bb901f83433700e604fe0ae67c5f2
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < 6aee2d478545c089dd5d055d3c9f0c7ea034fb80
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < 4e4ab09db7899d7f2d2293a18adf0fa200a27e73
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < 2df964d141270c40f07547b0c2e0a51e2573d46d
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < 876014b4eeb927146430e7591cf959a7ceb8d64a
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < a20a0010eb6485f60cd64e15ebc85a4bd388642e
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < 60234845142fddb27db89ebc00a65178421fb3a4
    • affected f984b51e0779a6dd30feedc41404013ca54e5d05 – < 12b80cdbc54cf615b4717a4e8180063408091ea2
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80689 badge
[![CVE-2026-80689](https://cveledger.app/badge/CVE-2026-80689.svg)](https://cveledger.app/cve/CVE-2026-80689)

Record last updated .