CVE-2026-99617
In the Linux kernel, the following vulnerability has been resolved: arm64: mm: validate /dev/mem mmap ranges without overflow An arm64 syzkaller reproducer creates a FUSE character device with major:minor 1:1, so opening it uses the /dev/mem file operations. It maps one page from offset 0xfffffffffffff000 at user address zero. The next openat() with a NULL pathname triggers a synchronous external abort (SEA, ESR 0x96000010) in strncpy_from_user() via do_getname(), panicking the kernel. valid_mmap_phys_addr_range() checks the exclusive end by adding the mapping size to the starting address. For this offset, the sum wraps to zero and passes the PHYS_MASK test, allowing an out-of-range PFN to reach remap_pfn_range(). The inclusive-end overflow check in mmap_mem_prepare() does not catch it because the end is ULONG_MAX. Reject starting PFNs outside PHYS_MASK and compare the inclusive length against the remaining physical range without overflowing. This also allows mappings that end exactly at PHYS_MASK, which the old check incorrectly rejects. [[email protected]: changed the check to look more like __access_ok()]
Properties
- Last source
- FIRST EPSS
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00201
- Cve id
- CVE-2026-99617
- First seen by Signal
- 2026-11-20T07:38:10+00:00
- Name
- CVE-2026-99617
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Published at
- 2026-11-20T06:17:54.227
- Last modified
- 2026-11-20T06:17:54.227
- Epss percentile
- 0.09918
Related research
Explore deeper with Ninja Signal's threat intelligence graph