CVE-2026-99737: mm/shmem: fix truncate loop after boundary swapin failure

Published Nov 20, 2026
·
Updated

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

mm/shmem: fix truncate loop after boundary swapin failure

If swapping in a large entry at the new EOF fails, shmemundorange() leaves the entry in place. Its final scan skips the entry, then restarts from the same start index and finds it again. Truncation can loop forever while holding irwsem.

Advance start past the skipped entry so that a restarted scan can finish, as we already do for folios that cannot be split.

Note that this does not fix the missing zeroing when boundary swapin fails, it merely prevents the endless loop.

Affected Software

6 affected componentsFixes available
linux/kernel>=6.12.69<6.12.118
6.12.118
linux/kernel>=6.18.9<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux<=6.12.107-1, <=6.12.117-1, <=7.3.4-1
6.1.176-16.1.192-27.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

What conditions are required to trigger the infinite truncation loop?

The failure occurs when truncating shmem and swapping in a large entry at the new end-of-file boundary fails. The entry is left in place, causing the final scan to restart at the same index and repeatedly encounter it while holding i_rwsem.

2

What is the practical impact of the issue?

Truncation can loop indefinitely while holding i_rwsem. This can block operations that need that inode read-write semaphore.

3

Does this fix address all consequences of a boundary swapin failure?

No. The fix prevents the endless truncation loop by advancing the scan start past the skipped entry, but it does not fix the missing zeroing when boundary swapin fails.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203