CVE-2026-58813: Linux kernel mmap bounds check vulnerability in mman.c

CVE-2026-58813 · Severity: info · Published 2026-11-10

The Linux kernel's memory mapping function contains a flaw that allows a local attacker to read and write memory outside designated bounds through improper size truncation. An attacker with system-level access could exploit this to escalate privileges or compromise system stability without any user interaction required.

Technologies: Google Android, Linux kernel. Vendors: Google.

Quick answers

Is CVE-2026-58813 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-58813 being exploited in the wild.
How severe is CVE-2026-58813?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Google Android; Linux kernel.
Is there a fix for CVE-2026-58813?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-58813 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-58813?
Check whether you run Google Android or Linux kernel. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an out-of-bounds read/write in the mmap function of mman.c, caused by an incorrect bounds check during mapping size truncation. This is a local privilege escalation (EoP) vulnerability requiring system execution privileges. The flaw allows direct memory access beyond intended boundaries, enabling privilege escalation.

Affected products

  • Google Android
  • Linux kernel

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.