CVE-2025-21721: nilfs2: handle errors that nilfs_prepare_chunk() may return
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1ee2d454baa361d2964e3e2f2cca9ee3f769d93c, 481136234dfe96c7f92770829bec6111c7c5f5dd, 607dc724b162f4452dc768865e578c1a509a1c8c.
Low priority for now. Upgrade to Linux Linux 1ee2d454baa361d2964e3e2f2cca9ee3f769d93c, 481136234dfe96c7f92770829bec6111c7c5f5dd, 607dc724b162f4452dc768865e578c1a509a1c8c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-617
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.30affected
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before b38c6c260c2415c7f0968871305e7a093daabb4caffected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before f70bd2d8ca454e0ed78970f72147ca321dbaa015affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 607dc724b162f4452dc768865e578c1a509a1c8caffected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 1ee2d454baa361d2964e3e2f2cca9ee3f769d93caffected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 7891ac3b0a5c56f7148af507306308ab841cdc31affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before eddd3176b8c4c83a46ab974574cda7c3dfe09388affected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before 481136234dfe96c7f92770829bec6111c7c5f5ddaffected · git
- 2ba466d74ed74f073257f86e61519cb8f8f46184 and later · before ee70999a988b8abc3490609142f50ebaa8344432affected · git
- before 2.6.30not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.30 and later · before 5.4.291
- linux linux kernel5.5 and later · before 5.10.235
- linux linux kernel5.11 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.131
- linux linux kernel6.2 and later · before 6.6.80
- linux linux kernel6.7 and later · before 6.12.13
- linux linux kernel6.13 and later · before 6.13.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.133-1 | 6.1.133-1 |
| Debian:13 | linux | before 6.12.13-1 | 6.12.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-21717Feb 26, 2025 · net/mlx5e: add missing cpu_to_node to kvzalloc_node in mlx5e_open_xdpredirect_sq28Monitor
- ← EarlierCVE-2025-21720Feb 26, 2025 · xfrm: delete intermediate secpath entry in packet offload mode22Monitor
- Later →CVE-2025-21730Feb 26, 2025 · wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ee2d454baa361d2964e3e2f2cca9ee3f769d93c | Vendor (CNA) |
| Linux Linux | 481136234dfe96c7f92770829bec6111c7c5f5dd | Vendor (CNA) |
| Linux Linux | 607dc724b162f4452dc768865e578c1a509a1c8c | Vendor (CNA) |
| Linux Linux | 7891ac3b0a5c56f7148af507306308ab841cdc31 | Vendor (CNA) |
| Linux Linux | b38c6c260c2415c7f0968871305e7a093daabb4c | Vendor (CNA) |
| Linux Linux | eddd3176b8c4c83a46ab974574cda7c3dfe09388 | Vendor (CNA) |
| Linux Linux | ee70999a988b8abc3490609142f50ebaa8344432 | Vendor (CNA) |
| Linux Linux | f70bd2d8ca454e0ed78970f72147ca321dbaa015 | Vendor (CNA) |
| debian:linux | 6.1.133-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31739429 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2026-52952483 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2025-39803201 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2023-52621337 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers31Monitor
- CVE-2026-31398401 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2026-46117456 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/481136234dfe96c7f92770829bec6111c7c5f5dd
- git.kernel.org/stable/c/607dc724b162f4452dc768865e578c1a509a1c8c
- git.kernel.org/stable/c/7891ac3b0a5c56f7148af507306308ab841cdc31
- git.kernel.org/stable/c/b38c6c260c2415c7f0968871305e7a093daabb4c
- git.kernel.org/stable/c/eddd3176b8c4c83a46ab974574cda7c3dfe09388
- git.kernel.org/stable/c/ee70999a988b8abc3490609142f50ebaa8344432
- git.kernel.org/stable/c/f70bd2d8ca454e0ed78970f72147ca321dbaa015
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.