PT-2026-152619

CVE-2026-99739

·

Publicado

2026-11-20

·

Atualizado

2026-11-20

Descrição por

Pontuação
N/A
Não disponível

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.

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.
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾