CVEvulnerability
CVE-2025-71072
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2026-01-13
- Last modified
- 2026-10-21
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 8.2 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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().
Affected configurations
• linux linux kernel (>= 6.6.1 < 6.12.64)
• linux linux kernel (>= 6.13 < 6.18.3)
• linux linux kernel 6.6
• linux linux kernel 6.19
References
- https://git.kernel.org/stable/c/4642686699a46718d7f2fb5acd1e9d866a9d9cca Patch
- https://git.kernel.org/stable/c/4b0fe71fb3965d0db83cdfc2f4fe0b3227d70113 Patch
- https://git.kernel.org/stable/c/8fdbc6f9a994eb327868a4aa74a58953f31a2d0f git.kernel.org
- https://git.kernel.org/stable/c/e1b4c6a58304fd490124cc2b454d80edc786665c Patch