From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99653: mm: fix unkillable fault loop on MAP_DROPPABLE memory
Date: Fri, 20 Nov 2026 06:50:39 +0100 [thread overview]
Message-ID: <2026112045-CVE-2026-99653-9bf3@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mm: fix unkillable fault loop on MAP_DROPPABLE memory
handle_mm_fault() suppresses VM_FAULT_OOM for VM_DROPPABLE mappings.
For user-mode faults, pending signals are processed before retrying the
access. Kernel-mode faults on user buffers instead return directly to
the faulting instruction.
With persistent allocation failures (esp. memcg limits), a syscall,
such as write(), can therefore loop while not dropping locks.
Only suppress VM_FAULT_OOM when FAULT_FLAG_USER is set, allowing
kernel-mode faults and GUP to fail and signal allocation errors.
Fix generated by an LLM and sent by Chris Mason in private.
[ david: simplify description ]
The Linux kernel CVE team has assigned CVE-2026-99653 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 9651fcedf7b92d3f7f1ab179e8ab55b85ee10fc1 and fixed in 6.12.118 with commit f8ed1ee3f590555be7cdbaeaa5b349eb9c95ba94
Issue introduced in 6.11 with commit 9651fcedf7b92d3f7f1ab179e8ab55b85ee10fc1 and fixed in 6.18.64 with commit 76ae1564e4c77d0ade4f533ac6de4fe1eb6d7e7f
Issue introduced in 6.11 with commit 9651fcedf7b92d3f7f1ab179e8ab55b85ee10fc1 and fixed in 7.3.5 with commit a9756f83b8a84b1f50c6af48aeabe9eb6429bcb1
Issue introduced in 6.11 with commit 9651fcedf7b92d3f7f1ab179e8ab55b85ee10fc1 and fixed in 7.4-rc2 with commit 9f02ca8c15a74bc9e4e8e05ec089f63cb87cbf75
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-99653
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:
mm/memory.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/f8ed1ee3f590555be7cdbaeaa5b349eb9c95ba94
https://git.kernel.org/stable/c/76ae1564e4c77d0ade4f533ac6de4fe1eb6d7e7f
https://git.kernel.org/stable/c/a9756f83b8a84b1f50c6af48aeabe9eb6429bcb1
https://git.kernel.org/stable/c/9f02ca8c15a74bc9e4e8e05ec089f63cb87cbf75
reply other threads:[~2026-11-20 5:56 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=2026112045-CVE-2026-99653-9bf3@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.