cve.bz

CVE-2025-21722 linux linux kernel: Use After Free

7.8 highEPSS 0.3%Fix available

High (7.8) in linux linux kernel. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not force clear folio if buffer is referenced Patch series "nilfs2: protect busy buffer heads from being force-cleared". This series fixes the buffer head state inconsistency issues reported by syzbot that occurs when the filesystem is corrupted and falls back to read-only, and the associated buffer head use-after-free issue. This patch (of 2): Syzbot has reported that after nilfs2 detects filesystem corruption and falls back to read-only, inconsistencies in the buffer state may occur. One of the inconsistencies is that when nilfs2 calls mark_buffer_dirty() to set a data or metadata buffer as dirty, but it detects that the buffer is not in the uptodate state: WARNING: CPU: 0 PID: 6049 at fs/buffer.c:1177 mark_buffer_dirty+0x2e5/0x520 fs/buffer.c:1177 ... Call Trace: <TASK> nilfs_palloc_commit_alloc_entry+0x4b/0x160 fs/nilfs2/alloc.c:598 nilfs_ifile_create_inode+0x1dd/0x3a0 fs/nilfs2/ifile.c:73 nilfs_new_inode+0x254/0x830 fs/nilfs2/inode.c:344 nilfs_mkdir+0x10d/0x340 fs/nilfs2/namei.c:218 vfs_mkdir+0x2f9/0x4f0 fs/namei.c:4257 do_mkdirat+0x264/0x3a0 fs/namei.c:4280 __do_sys_mkdirat fs/namei.c:4295 [inline] __se_sys_mkdirat fs/namei.c:4293 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4293 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The other is when nilfs_btree_propagate(), which propagates the dirty state to the ancestor nodes of a b-tree that point to a dirty buffer, detects that the origin buffer is not dirty, even though it should be: WARNING: CPU: 0 PID: 5245 at fs/nilfs2/btree.c:2089 nilfs_btree_propagate+0xc79/0xdf0 fs/nilfs2/btree.c:2089 ... Call Trace: <TASK> nilfs_bmap_propagate+0x75/0x120 fs/nilfs2/bmap.c:345 nilfs_collect_file_data+0x4d/0xd0 fs/nilfs2/segment.c:587 nilfs_segctor_apply_buffers+0x184/0x340 fs/nilfs2/segment.c:1006 nilfs_segctor_scan_file+0x28c/0xa50 fs/nilfs2/segment.c:1045 nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1216 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1540 [inline] nilfs_segctor_do_construct+0x1c28/0x6b90 fs/nilfs2/segment.c:2115 nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2479 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline] nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Both of these issues are caused by the callbacks that handle the page/folio write requests, forcibly clear various states, including the working state of the buffers they hold, at unexpected times when they detect read-only fallback. Fix these issues by checking if the buffer is referenced before clearing the page/folio state, and skipping the clear if it is.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-02-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-21722 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-21722?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-21722?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-21722 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.10 and later

Fixed in

ProductRelease lineFixed in
Linux5.45.4.291
Linux5.105.10.235
Linux5.155.15.179
Linux6.16.1.129
Linux6.66.6.160
Linux6.126.12.13
Linux6.136.13.2
Linuxlater releases6.14

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux5.10.237-1DLA-4178-1
Debian11linux-6.16.1.129-1~deb11u1DLA-4102-1
Debian12linux6.1.129-1DEBIAN-CVE-2025-21722
Debian13, 14linux6.12.13-1DEBIAN-CVE-2025-21722
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-21722
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-21722
Ubuntu20.04:LTSlinux5.4.0-216.236UBUNTU-CVE-2025-21722 USN-7516-1
Ubuntu20.04:LTSlinux-aws5.4.0-1146.156UBUNTU-CVE-2025-21722 USN-7516-9
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1084.91~20.04.1UBUNTU-CVE-2025-21722 USN-7510-8
Ubuntu20.04:LTSlinux-azure5.4.0-1151.158UBUNTU-CVE-2025-21722 USN-7516-3
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1089.98~20.04.1UBUNTU-CVE-2025-21722 USN-7510-3
Ubuntu20.04:LTSlinux-bluefield5.4.0-1105.112UBUNTU-CVE-2025-21722 USN-7517-3
Ubuntu20.04:LTSlinux-gcp5.4.0-1149.158UBUNTU-CVE-2025-21722 USN-7516-1
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1083.92~20.04.1UBUNTU-CVE-2025-21722 USN-7512-1
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-21722
Ubuntu20.04:LTSlinux-ibm5.4.0-1092.97UBUNTU-CVE-2025-21722 USN-7516-6
100 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.130-r0BELL-CVE-2025-21722
Alpaquita25linux-lts6.12.41-r0BELL-CVE-2025-21722
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-21722

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A race in nilfs2 could force-clear page/buffer states while the underlying buffer heads were still referenced or locked, leading to buffer-state corruption and potential UAF-triggered kernel crashes. Exploitation requires local write capabilities on a nilfs2 mount (PR:L) and no user interaction; confidentiality and integrity are unaffected, but availability impact is High due to possible panics (CIA: N/N/H). The patch avoids clearing when buffers are in use, preventing the DoS condition during read-only fallback.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-21722.

References

Check your stackJSON