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-80627MIPS: mm: Fix out-of-bounds write in maar_res_walk()

Description

In the Linux kernel, the following vulnerability has been resolved: MIPS: mm: Fix out-of-bounds write in maar_res_walk() maar_res_walk() uses wi->num_cfg as the index into the fixed-size wi->cfg array, but checks whether the array is full only after it has filled the selected entry. If walk_system_ram_range() reports more than 16 memory ranges, the overflow call writes one struct maar_config past the end of the array before WARN_ON() prevents num_cfg from advancing. Move the full-array check before taking the array slot and return non-zero when the scratch array is full, so walk_system_ram_range() terminates the walk instead of invoking the callback for further ranges.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

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.22% · top 87% of all CVEs (19 Nov 2026)
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 a5718fe8f70f33b1b5b47a153057cfdd19684598 – < a594100e147a6a67eb29189170f1df3645cda12b
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < 8b3e0c1c63015deaf084286899f5b2d0526715de
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < 44c1d902cf0798b60762a7a98be992b9f5ded7dd
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < ac7385af1dca86a5ea704c80ca4dc822083ff9e2
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < 431812eb88c200bc3ec33b88782c8cc415842074
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < 92f38fe85198ace9b211bc7712b7951acfb94560
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < 038f068cced8e9c49e8c419f3112d909ad366a3a
    • affected a5718fe8f70f33b1b5b47a153057cfdd19684598 – < 1b001b16bc88f3f7817e228acfd91ee01bdcfcce
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 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-80627 badge
[![CVE-2026-80627](https://cveledger.app/badge/CVE-2026-80627.svg)](https://cveledger.app/cve/CVE-2026-80627)

Record last updated .