CVE-2025-22002: netfs: Call `invalidate_cache` only if implemented
In the Linux kernel, the following vulnerability has been resolved:
netfs: Call invalidatecache only if implemented
Many filesystems such as NFS and Ceph do not implement the invalidatecache method. On those filesystems, if writing to the cache (NETFSWRITETOCACHE) fails for some reason, the kernel crashes like this:
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor instruction fetch in kernel mode #PF: errorcode(0x0010) - not-present page PGD 0 P4D 0 Oops: Oops: 0010 [#1] SMP PTI CPU: 9 UID: 0 PID: 3380 Comm: kworker/u193:11 Not tainted 6.13.3-cm4all1-hp #437 Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/17/2018 Workqueue: eventsunbound netfswritecollectionworker RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffff9b86e2ca7dc0 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 7fffffffffffffff RDX: 0000000000000001 RSI: ffff89259d576a18 RDI: ffff89259d576900 RBP: ffff89259d5769b0 R08: ffff9b86e2ca7d28 R09: 0000000000000002 R10: ffff89258ceaca80 R11: 0000000000000001 R12: 0000000000000020 R13: ffff893d158b9338 R14: ffff89259d576900 R15: ffff89259d5769b0 FS: 0000000000000000(0000) GS:ffff893c9fa40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 000000054442e003 CR4: 00000000001706f0 Call Trace: <TASK> ? die+0x1f/0x60 ? pagefaultoops+0x15c/0x460 ? trytowakeup+0x2d2/0x530 ? excpagefault+0x5e/0x100 ? asmexcpagefault+0x22/0x30 netfswritecollectionworker+0xe9f/0x12b0 ? xspollcheckreadable+0x3f/0x80 ? xsstreamdatareceiveworkfn+0x8d/0x110 processonework+0x134/0x2d0 workerthread+0x299/0x3a0 ? pfxworkerthread+0x10/0x10 kthread+0xba/0xe0 ? pfxkthread+0x10/0x10 retfromfork+0x30/0x50 ? pfxkthread+0x10/0x10 retfromforkasm+0x1a/0x30 </TASK> Modules linked in: CR2: 0000000000000000
This patch adds the missing NULL check.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-azure-6.11to a version that resolves this vulnerability.Fixed in 6.11.0-1018.18~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.11to a version that resolves this vulnerability.Fixed in 6.11.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-6.11to a version that resolves this vulnerability.Fixed in 6.11.0-28.28~24.04.1 - Upgrade
Upgrade
ubuntu/linux-lowlatency-hwe-6.11to a version that resolves this vulnerability.Fixed in 6.11.0-1015.16~24.04.2 - Upgrade
Upgrade
ubuntu/linux-nvidia-6.11to a version that resolves this vulnerability.Fixed in 6.11.0-1012.12 - Upgrade
Upgrade
ubuntu/linux-oem-6.11to a version that resolves this vulnerability.Fixed in 6.11.0-1024.24
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22002?
CVE-2025-22002 is classified as a moderate severity vulnerability due to its specific impact on certain filesystems.
How do I fix CVE-2025-22002?
To fix CVE-2025-22002, ensure that your Linux kernel is updated to the latest version where this vulnerability has been addressed.
Which versions of the Linux kernel are affected by CVE-2025-22002?
CVE-2025-22002 affects Linux kernel versions that do not implement the `invalidate_cache` method for filesystems such as NFS and Ceph.
What components are impacted by CVE-2025-22002?
CVE-2025-22002 specifically impacts the netfs subsystem within the Linux kernel, affecting its interaction with certain filesystems.
Is my data at risk due to CVE-2025-22002?
Yes, data integrity may be at risk if cached writes fail on unsupported filesystems, making it important to address this vulnerability promptly.