All of lore.kernel.org
 help / color / mirror / Atom feed
* CVE-2026-99739: mm/shmem: fix truncate hang in large swap entry
@ 2026-11-20  5:52 Greg Kroah-Hartman
  0 siblings, 0 replies; only message in thread
From: Greg Kroah-Hartman @ 2026-11-20  5:52 UTC (permalink / raw)
  To: linux-cve-announce; +Cc: Greg Kroah-Hartman

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

mm/shmem: fix truncate hang in large swap entry

Truncating a tmpfs file or memfd to a page-aligned size inside a large
swap entry can loop indefinitely in shmem_undo_range(). The task holds
the inode lock and cannot be killed.

A large swap entry represents a whole swapped-out folio. For example,
truncate a file whose pages 0-7 share one swap entry to four pages:

    [ 0  1  2  3 | 4  5  6  7 ]
         keep    |   discard
                 ^
            new EOF, start = 4

i_size has already been updated when boundary handling asks
shmem_get_partial_folio() for page 4. Since it is swapped out, the helper
calls shmem_get_folio() with SGP_READ. That rejects page 4 with -EINVAL
because its starting offset equals i_size. Nothing is read back.

The final scan cannot free the entry without losing pages 0-3. It skips
it, restarts from start = 4, and finds it again indefinitely. An unaligned
truncate avoids this particular failure because the requested page starts
below i_size. Folios already in the page-cache cannot trigger it as the
direct lookup will return them beyond EOF.

Fix it by letting shmem_get_partial_folio() call shmem_swapin_folio()
directly for swap entries. This bypasses the read path's i_size check,
allowing the existing boundary handling to zero and split the folio. If
swap-in returns a smaller folio, it also splits the swap entry so the
final scan can free the entries beyond EOF. Retry the lookup if the entry
changes during swap-in.

Handling swap-in allocation failures remains broken and is unchanged by
this commit. Even when shmem_swapin_folio() correctly returns -ENOMEM
instead of -EEXIST, shmem_get_partial_folio() returns NULL and
shmem_undo_range() skips boundary handling. If the large swap entry
remains intact, truncation can still loop in the final scan, while hole
punching can return without zeroing the boundary.

This may read an entire large folio back from swap while holding
i_rwsem, only to discard part of it. Avoiding that I/O would require
splitting both the swap entry and any large folio still in the swap
cache. That, however, is much bigger work.

The Linux kernel CVE team has assigned CVE-2026-99739 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.12.69 with commit a99f9a4669a04662c8f9efe0e62cafc598153139 and fixed in 6.12.118 with commit 9fbca74e8efbb8fed180639af349449f04a2a3c3
	Issue introduced in 6.18.9 with commit b23bee8cdb7aabce5701a7f57414db5a354ae8ed and fixed in 6.18.64 with commit 577374a2171cdb68e492725feb564364f93161b6
	Issue introduced in 6.19 with commit 8a1968bd997f45a9b11aefeabdd1232e1b6c7184 and fixed in 7.3.5 with commit ef6daf302dc569a67fe50968f9b6085f111b8560
	Issue introduced in 6.19 with commit 8a1968bd997f45a9b11aefeabdd1232e1b6c7184 and fixed in 7.4-rc2 with commit fa213b08f37f9dff78ce240a87579dc264fc7a5d

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-99739
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/shmem.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/9fbca74e8efbb8fed180639af349449f04a2a3c3
	https://git.kernel.org/stable/c/577374a2171cdb68e492725feb564364f93161b6
	https://git.kernel.org/stable/c/ef6daf302dc569a67fe50968f9b6085f111b8560
	https://git.kernel.org/stable/c/fa213b08f37f9dff78ce240a87579dc264fc7a5d

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-11-20  6:00 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20  5:52 CVE-2026-99739: mm/shmem: fix truncate hang in large swap entry Greg Kroah-Hartman

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.