CVE-2022-48989: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: fscache: Fix oops due to race with cookie_lru and use_cookie If a cookie expires from the LRU and the LRU_DISCARD flag is set, but the state machine has not run yet, it's possible another thread can call fscache_use_cookie and begin to use it. When the cookie_worker finally runs, it will see the LRU_DISCARD flag set, transition the cookie->state to LRU_DISCARDING, which will then withdraw the cookie. Once the cookie is withdrawn the object is removed the below oops will occur because the object associated with the cookie is now NULL. Fix the oops by clearing the LRU_DISCARD bit if another thread uses the cookie before the cookie_worker runs. BUG: kernel NULL pointer dereference, address: 0000000000000008 ... CPU: 31 PID: 44773 Comm: kworker/u130:1 Tainted: G E 6.0.0-5.dneg.x86_64 #1 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022 Workqueue: events_unbound netfs_rreq_write_to_cache_work [netfs] RIP: 0010:cachefiles_prepare_write+0x28/0x90 [cachefiles] ... Call Trace: netfs_rreq_write_to_cache_work+0x11c/0x320 [netfs] process_one_work+0x217/0x3e0 worker_thread+0x4a/0x3b0 kthread+0xd6/0x100
AI Analysis
Technical Summary
CVE-2022-48989 is a vulnerability in the Linux kernel's fscache subsystem, specifically related to a race condition involving the cookie_lru (Least Recently Used) list and the use_cookie function. The issue arises when a cache cookie expires and is marked with the LRU_DISCARD flag, but the state machine responsible for handling this expiration has not yet executed. In this window, another thread can call fscache_use_cookie and begin using the cookie. When the cookie_worker thread eventually runs, it detects the LRU_DISCARD flag and transitions the cookie's state to LRU_DISCARDING, withdrawing the cookie and removing the associated object. Because the other thread is still using the cookie, this leads to a NULL pointer dereference (kernel oops) when the now-removed object is accessed. The kernel oops manifests as a crash with a NULL pointer dereference at address 0x8, causing instability in the kernel. The fix involves clearing the LRU_DISCARD bit if another thread uses the cookie before the cookie_worker runs, preventing the race condition and subsequent kernel crash. This vulnerability affects Linux kernel versions prior to the patch and can cause denial of service due to kernel panics or crashes. The vulnerability does not require user interaction but involves kernel-level concurrency issues. No known exploits are reported in the wild as of the publication date.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in environments running affected Linux kernel versions with fscache enabled, such as servers and cloud infrastructure. The impact is mainly denial of service through kernel crashes, which can disrupt critical services, cause downtime, and potentially lead to data loss or corruption if systems are abruptly halted. Organizations relying on Linux-based infrastructure for web services, cloud computing, or network file caching may experience instability or outages. Although this vulnerability does not appear to allow privilege escalation or remote code execution, the resulting kernel oops can degrade system reliability and availability, impacting business continuity. Given the widespread use of Linux in European data centers, cloud providers, and enterprise environments, the vulnerability could affect a broad range of sectors including finance, telecommunications, government, and critical infrastructure. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed promptly to prevent potential exploitation or accidental crashes.
Mitigation Recommendations
European organizations should promptly apply the Linux kernel patches that fix this race condition in the fscache subsystem. Since no patch links are provided in the source, organizations should monitor official Linux kernel repositories and distributions (e.g., Debian, Ubuntu, Red Hat, SUSE) for updated kernel packages addressing CVE-2022-48989. In the interim, organizations can mitigate risk by disabling fscache if it is not essential to their operations, thereby avoiding the vulnerable code path. System administrators should also implement robust kernel crash monitoring and automated recovery mechanisms to minimize downtime in case of kernel oops. Additionally, thorough testing of kernel updates in staging environments is recommended to ensure stability before production deployment. Network segmentation and limiting access to critical Linux servers can reduce the attack surface, although this vulnerability does not require remote exploitation. Maintaining up-to-date backups and disaster recovery plans will help mitigate the impact of unexpected outages caused by this vulnerability.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland, Belgium
CVE-2022-48989: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: fscache: Fix oops due to race with cookie_lru and use_cookie If a cookie expires from the LRU and the LRU_DISCARD flag is set, but the state machine has not run yet, it's possible another thread can call fscache_use_cookie and begin to use it. When the cookie_worker finally runs, it will see the LRU_DISCARD flag set, transition the cookie->state to LRU_DISCARDING, which will then withdraw the cookie. Once the cookie is withdrawn the object is removed the below oops will occur because the object associated with the cookie is now NULL. Fix the oops by clearing the LRU_DISCARD bit if another thread uses the cookie before the cookie_worker runs. BUG: kernel NULL pointer dereference, address: 0000000000000008 ... CPU: 31 PID: 44773 Comm: kworker/u130:1 Tainted: G E 6.0.0-5.dneg.x86_64 #1 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022 Workqueue: events_unbound netfs_rreq_write_to_cache_work [netfs] RIP: 0010:cachefiles_prepare_write+0x28/0x90 [cachefiles] ... Call Trace: netfs_rreq_write_to_cache_work+0x11c/0x320 [netfs] process_one_work+0x217/0x3e0 worker_thread+0x4a/0x3b0 kthread+0xd6/0x100
AI-Powered Analysis
Technical Analysis
CVE-2022-48989 is a vulnerability in the Linux kernel's fscache subsystem, specifically related to a race condition involving the cookie_lru (Least Recently Used) list and the use_cookie function. The issue arises when a cache cookie expires and is marked with the LRU_DISCARD flag, but the state machine responsible for handling this expiration has not yet executed. In this window, another thread can call fscache_use_cookie and begin using the cookie. When the cookie_worker thread eventually runs, it detects the LRU_DISCARD flag and transitions the cookie's state to LRU_DISCARDING, withdrawing the cookie and removing the associated object. Because the other thread is still using the cookie, this leads to a NULL pointer dereference (kernel oops) when the now-removed object is accessed. The kernel oops manifests as a crash with a NULL pointer dereference at address 0x8, causing instability in the kernel. The fix involves clearing the LRU_DISCARD bit if another thread uses the cookie before the cookie_worker runs, preventing the race condition and subsequent kernel crash. This vulnerability affects Linux kernel versions prior to the patch and can cause denial of service due to kernel panics or crashes. The vulnerability does not require user interaction but involves kernel-level concurrency issues. No known exploits are reported in the wild as of the publication date.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in environments running affected Linux kernel versions with fscache enabled, such as servers and cloud infrastructure. The impact is mainly denial of service through kernel crashes, which can disrupt critical services, cause downtime, and potentially lead to data loss or corruption if systems are abruptly halted. Organizations relying on Linux-based infrastructure for web services, cloud computing, or network file caching may experience instability or outages. Although this vulnerability does not appear to allow privilege escalation or remote code execution, the resulting kernel oops can degrade system reliability and availability, impacting business continuity. Given the widespread use of Linux in European data centers, cloud providers, and enterprise environments, the vulnerability could affect a broad range of sectors including finance, telecommunications, government, and critical infrastructure. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed promptly to prevent potential exploitation or accidental crashes.
Mitigation Recommendations
European organizations should promptly apply the Linux kernel patches that fix this race condition in the fscache subsystem. Since no patch links are provided in the source, organizations should monitor official Linux kernel repositories and distributions (e.g., Debian, Ubuntu, Red Hat, SUSE) for updated kernel packages addressing CVE-2022-48989. In the interim, organizations can mitigate risk by disabling fscache if it is not essential to their operations, thereby avoiding the vulnerable code path. System administrators should also implement robust kernel crash monitoring and automated recovery mechanisms to minimize downtime in case of kernel oops. Additionally, thorough testing of kernel updates in staging environments is recommended to ensure stability before production deployment. Network segmentation and limiting access to critical Linux servers can reduce the attack surface, although this vulnerability does not require remote exploitation. Maintaining up-to-date backups and disaster recovery plans will help mitigate the impact of unexpected outages caused by this vulnerability.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-08-22T01:27:53.635Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982fc4522896dcbe683c
Added to database: 5/21/2025, 9:09:03 AM
Last enriched: 7/1/2025, 12:55:35 AM
Last updated: 8/16/2025, 7:53:20 PM
Views: 16
Related Threats
CVE-2025-9107: Cross Site Scripting in Portabilis i-Diario
MediumCVE-2025-9106: Cross Site Scripting in Portabilis i-Diario
MediumCVE-2025-9105: Cross Site Scripting in Portabilis i-Diario
MediumCVE-2025-9104: Cross Site Scripting in Portabilis i-Diario
MediumCVE-2025-9102: Improper Export of Android Application Components in 1&1 Mail & Media mail.com App
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.