Quick answers
- Is CVE-2026-58845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58845 being exploited in the wild.
- How severe is CVE-2026-58845?
- Informational severity, published 2 November 2026.
- Which products and versions are affected?
- Google Android kernel 16K page size migration code.
- Is there a fix for CVE-2026-58845?
- Yes: fixed in Android kernel commit 3b9b40df51bda90ffb2833dcef11905e751dafdb and ed0e57e1e27a9eecd6c1a3dd1dd9ed1b8d1a06b4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58845 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58845?
- Check whether you run Google Android kernel at an affected version. 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.
How to fix
- Fixed in: Android kernel commit 3b9b40df51bda90ffb2833dcef11905e751dafdb and ed0e57e1e27a9eecd6c1a3dd1dd9ed1b8d1a06b4
Technical details
An integer overflow in VMA (virtual memory area) padding logic in the Android kernel's page size migration subsystem allows out-of-bounds memory writes. The vulnerability exists in multiple locations handling padding metadata for dynamically linked ELF binaries, particularly in vma_pad_pages() and related functions in mm/pgsize_migration.c and mm/mmap.c. Local exploitation requires no additional privileges and no user interaction.
Affected products
- Google Android kernel 16K page size migration code
Timeline
- 2026-11-02: disclosed