From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99617: arm64: mm: validate /dev/mem mmap ranges without overflow
Date: Fri, 20 Nov 2026 06:50:03 +0100 [thread overview]
Message-ID: <2026112031-CVE-2026-99617-bc6a@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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.
[catalin.marinas@arm.com: changed the check to look more like __access_ok()]
The Linux kernel CVE team has assigned CVE-2026-99617 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.7 with commit 1d18c47c735e8adfe531fc41fae31e98f86b68fe and fixed in 6.12.118 with commit db6607fd74263ead8df644b98ff25fac74d86f0e
Issue introduced in 3.7 with commit 1d18c47c735e8adfe531fc41fae31e98f86b68fe and fixed in 6.18.64 with commit fddf55af2d078f4186c5ab4f07383c8599b14640
Issue introduced in 3.7 with commit 1d18c47c735e8adfe531fc41fae31e98f86b68fe and fixed in 7.3.5 with commit c9a54fc8147f45020badd9001d4ed234c74b9526
Issue introduced in 3.7 with commit 1d18c47c735e8adfe531fc41fae31e98f86b68fe and fixed in 7.4-rc2 with commit b0958b1397fb5ffdb995c0ccc74349841929c08d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99617
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/arm64/mm/mmap.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/db6607fd74263ead8df644b98ff25fac74d86f0e
https://git.kernel.org/stable/c/fddf55af2d078f4186c5ab4f07383c8599b14640
https://git.kernel.org/stable/c/c9a54fc8147f45020badd9001d4ed234c74b9526
https://git.kernel.org/stable/c/b0958b1397fb5ffdb995c0ccc74349841929c08d
reply other threads:[~2026-11-20 5:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112031-CVE-2026-99617-bc6a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.