CVE-2025-21721

MEDIUM EPSS 8.5%
Published Feb 27, 20251y ago · Modified Jun 17, 20262w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Feb 27, 2025 1y ago
Last Modified Jun 17, 2026 2w ago

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: handle errors that nilfs_prepare_chunk() may return Patch series "nilfs2: fix issues with rename operations". This series fixes BUG_ON check failures reported by syzbot around rename operations, and a minor behavioral issue where the mtime of a child directory changes when it is renamed instead of moved. This patch (of 2): The directory manipulation routines nilfs_set_link() and nilfs_delete_entry() rewrite the directory entry in the folio/page previously read by nilfs_find_entry(), so error handling is omitted on the assumption that nilfs_prepare_chunk(), which prepares the buffer for rewriting, will always succeed for these. And if an error is returned, it triggers the legacy BUG_ON() checks in each routine. This assumption is wrong, as proven by syzbot: the buffer layer called by nilfs_prepare_chunk() may call nilfs_get_block() if necessary, which may fail due to metadata corruption or other reasons. This has been there all along, but improved sanity checks and error handling may have made it more reproducible in fuzzing tests. Fix this issue by adding missing error paths in nilfs_set_link(), nilfs_delete_entry(), and their caller nilfs_rename().

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
8.5% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-617

Affected Products 7

VendorProductVersionRange
linuxlinux_kernel*≥2.6.30  –  <5.4.291
linuxlinux_kernel*≥5.5  –  <5.10.235
linuxlinux_kernel*≥5.11  –  <5.15.179
linuxlinux_kernel*≥5.16  –  <6.1.131
linuxlinux_kernel*≥6.2  –  <6.6.80
linuxlinux_kernel*≥6.7  –  <6.12.13
linuxlinux_kernel*≥6.13  –  <6.13.2

References 10

  • git.kernel.org https://git.kernel.org/stable/c/1ee2d454baa361d2964e3e2f2cca9ee3f769d93c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/481136234dfe96c7f92770829bec6111c7c5f5dd
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/607dc724b162f4452dc768865e578c1a509a1c8c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/7891ac3b0a5c56f7148af507306308ab841cdc31
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b38c6c260c2415c7f0968871305e7a093daabb4c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/eddd3176b8c4c83a46ab974574cda7c3dfe09388
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/ee70999a988b8abc3490609142f50ebaa8344432
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f70bd2d8ca454e0ed78970f72147ca321dbaa015
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/1ee2d454baa361d2964e3e2f2cca9ee3f769d93c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/481136234dfe96c7f92770829bec6111c7c5f5dd
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/607dc724b162f4452dc768865e578c1a509a1c8c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/7891ac3b0a5c56f7148af507306308ab841cdc31
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b38c6c260c2415c7f0968871305e7a093daabb4c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/eddd3176b8c4c83a46ab974574cda7c3dfe09388
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/ee70999a988b8abc3490609142f50ebaa8344432
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f70bd2d8ca454e0ed78970f72147ca321dbaa015
    Patch