Home

Description

In the Linux kernel, the following vulnerability has been resolved: shmem: fix recovery on rename failures maple_tree insertions can fail if we are seriously short on memory; simple_offset_rename() does not recover well if it runs into that. The same goes for simple_offset_rename_exchange(). Moreover, shmem_whiteout() expects that if it succeeds, the caller will progress to d_move(), i.e. that shmem_rename2() won't fail past the successful call of shmem_whiteout(). Not hard to fix, fortunately - mtree_store() can't fail if the index we are trying to store into is already present in the tree as a singleton. For simple_offset_rename_exchange() that's enough - we just need to be careful about the order of operations. For simple_offset_rename() solution is to preinsert the target into the tree for new_dir; the rest can be done without any potentially failing operations. That preinsertion has to be done in shmem_rename2() rather than in simple_offset_rename() itself - otherwise we'd need to deal with the possibility of failure after successful shmem_whiteout().

PUBLISHED Reserved 2026-01-13 | Published 2026-01-13 | Updated 2026-02-09 | Assigner Linux

Product status

Default status
unaffected

a2e459555c5f9da3e619b7e47a63f98574dc75f1 (git) before 4b0fe71fb3965d0db83cdfc2f4fe0b3227d70113
affected

a2e459555c5f9da3e619b7e47a63f98574dc75f1 (git) before 4642686699a46718d7f2fb5acd1e9d866a9d9cca
affected

a2e459555c5f9da3e619b7e47a63f98574dc75f1 (git) before e1b4c6a58304fd490124cc2b454d80edc786665c
affected

Default status
affected

6.6
affected

Any version before 6.6
unaffected

6.12.64 (semver)
unaffected

6.18.3 (semver)
unaffected

6.19 (original_commit_for_fix)
unaffected

References

git.kernel.org/...c/4b0fe71fb3965d0db83cdfc2f4fe0b3227d70113

git.kernel.org/...c/4642686699a46718d7f2fb5acd1e9d866a9d9cca

git.kernel.org/...c/e1b4c6a58304fd490124cc2b454d80edc786665c

cve.org (CVE-2025-71072)

nvd.nist.gov (CVE-2025-71072)

Download JSON