CVE-2026-80627

MIPS: mm: Fix out-of-bounds write in maar_res_walk()

Published Aug 28, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An out‑of‑bounds write occurs in the Linux kernel’s MIPS memory‑management code. The function maar_res_walk() indexes a fixed‑size wi->cfg array using wi->num_cfg, but performs the fullness check only after the write has already taken place. If walk_system_ram_range reports more than 16 memory ranges, the write overruns the array boundary by one struct maar_config, corrupting adjacent kernel data. Based on the description, it is inferred that such corruption could lead to privilege escalation or a system crash if an attacker can trigger this path. The patch moves the overflow check before the write, preventing the overrun.

Affected Systems

The flaw exists only in the Linux kernel for the MIPS architecture. Any kernel that does not contain the commit that moves the full‑array check before the write is affected. No specific kernel release numbers are cited in the advisory, so operators should examine the running kernel version and compare it to the commit that implements the fix. The affected vendor is Linux; the primary product is the Linux kernel on MIPS.

Risk and Exploitability

The EPSS score of < 1% indicates a very low likelihood of exploitation, and the issue is not listed in CISA’s KEV catalog. The CVSS score of 5.5 reflects a moderate level of severity. Exploitation would likely require local or privileged access to code that triggers the memory‑range walking logic, such as during kernel boot or through privileged operations that supply many memory ranges. Based on the description, it is inferred that an attacker must be able to influence the walk_system_ram_range routine. No public exploit is documented, and the theoretical impact is high because kernel memory corruption can compromise entire system integrity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a release that includes the commit implementing the corrected array boundary check (e.g., the commit referenced in the advisory links).
  • Reboot the system after the kernel update so that the corrected code is loaded and any corrupted memory is reinitialized.
  • Apply any distribution‑provided security updates that address related memory‑management issues or otherwise strengthen the kernel.

Generated by OpenCVE AI on September 1, 2026 at 17:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8875-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8877-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8878-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8879-1 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8875-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8917-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8918-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9029-1 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-787
Type Values Removed Values Added
Weaknesses CWE-125
Type Values Removed Values Added
Weaknesses CWE-125
Type Values Removed Values Added
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.
Title MIPS: mm: Fix out-of-bounds write in maar_res_walk()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 28, 2026, 6:48 AM
Reserved
Aug 26, 2026, 2:34 PM
Status
Received
Published
Aug 28, 2026, 8:16 AM
Modified
Aug 28, 2026, 8:16 AM
Severity
Moderate
Public date
Aug 28, 2026, 12:00 AM