From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154077; b=jkPW8bQVcnOtQzhyXE+lCM37DW3EllcxjxMzCy5mMXaNRNRdWR+lSiTnUrjp3Ja7f3DM qdDArquMvru/9sAUs9ItZIg1DDm0snGZiGGwdusatAnK6SsrBWtKtlE1f9BY6Wer8KsaF 1YzXpgDGzgIRPx+P44tjJzf9Xf8dLpkixeegns48lAucaWPPbFy4sixujos3K4GyxxxsY GTpr10LszmWtwAiqxr9tLoaBzvKpHOwIfzC0yZu0p+8yMwuejnRuhnVLWtrpvurkkT6/6 HNz7LgXGG5GT/MZcG4NZyn7fE2MP09CcX3yDjIjA0shoF8TJKQxSBIuc/UdNMWbtwrw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154077; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=IrWAwBmg6nsKWkMl+EGCbdu9GnhntvpYksSnFPj9WMA=; b=0BgfmoVQ+O7P0QgXb40dTAWzDl09Oqm33XMVxZKqE6edtnRb9qhXZGtNJIXpiH3T/7OW c2MGK/g4ptzBVGLR1xZd26EkEPyexW46H8ybYZGzh3ZvErfDfBI03tSPR+lpT2WL9R+m7 1iqANOE+hj+8myx53ZF7kuMYkvNeX4l1iLFDQeLjlkqUVkzaf/P/kvrTKnWZyv2aOMbuj PFC3ewaJxhi34pUrnwVFX+U83IurlYwW2xo/MBKoV/TN2qL5cMhIV9zlp4hJRFkPFUPa1 m0rp4wKSOzF87g+Ql5iU6OKVNEqoSFDIDRdwfBYp79pD9SU9QKTBSk6TwKM9Uyoi4lQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=IeeHd4ds; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0B824606A320 for ; Fri, 20 Nov 2026 05:54:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=IeeHd4ds Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5A61A1F000C6; Fri, 20 Nov 2026 05:54:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154076; bh=IrWAwBmg6nsKWkMl+EGCbdu9GnhntvpYksSnFPj9WMA=; h=From:To:Cc:Subject:Date:Reply-To; b=IeeHd4dsYVf/5D0xQPxMvHML2xdaI7/8g6U6EM4JteC3j20/pnkVe4O8ccGrpQhU/ TXJOvsCw9AcR5p0c2Rou7J3YuFGOzEvG+MYKTwDfhvqZegEIPk4aC03ZG5UAzlr9at bNdp7i7PmzoxfkfBpCozEEb3eAWVPwatA5fg3ZT0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99617: arm64: mm: validate /dev/mem mmap ranges without overflow Date: Fri, 20 Nov 2026 06:50:03 +0100 Message-ID: <2026112031-CVE-2026-99617-bc6a@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3244; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=4glCjspO0Er56WSiFs5kV3/mzjvP5aJ+SeeQEtv0cl4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7+cYi0ifS0wSmFXBxmPcyb06R8l2Gvss5/pJzSeu7 p6v/UKmI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACbC38IwP7JI9H2UwBme41s8 ApYH9udGuHmuYZhfILCnbU/YT/9mjaIXyhcNb9ozW/EDAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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