Skip to main content

CVE-2024-53090: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-53090cvecve-2024-53090
Published: Thu Nov 21 2024 (11/21/2024, 18:17:07 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: afs: Fix lock recursion afs_wake_up_async_call() can incur lock recursion. The problem is that it is called from AF_RXRPC whilst holding the ->notify_lock, but it tries to take a ref on the afs_call struct in order to pass it to a work queue - but if the afs_call is already queued, we then have an extraneous ref that must be put... calling afs_put_call() may call back down into AF_RXRPC through rxrpc_kernel_shutdown_call(), however, which might try taking the ->notify_lock again. This case isn't very common, however, so defer it to a workqueue. The oops looks something like: BUG: spinlock recursion on CPU#0, krxrpcio/7001/1646 lock: 0xffff888141399b30, .magic: dead4ead, .owner: krxrpcio/7001/1646, .owner_cpu: 0 CPU: 0 UID: 0 PID: 1646 Comm: krxrpcio/7001 Not tainted 6.12.0-rc2-build3+ #4351 Hardware name: ASUS All Series/H97-PLUS, BIOS 2306 10/09/2014 Call Trace: <TASK> dump_stack_lvl+0x47/0x70 do_raw_spin_lock+0x3c/0x90 rxrpc_kernel_shutdown_call+0x83/0xb0 afs_put_call+0xd7/0x180 rxrpc_notify_socket+0xa0/0x190 rxrpc_input_split_jumbo+0x198/0x1d0 rxrpc_input_data+0x14b/0x1e0 ? rxrpc_input_call_packet+0xc2/0x1f0 rxrpc_input_call_event+0xad/0x6b0 rxrpc_input_packet_on_conn+0x1e1/0x210 rxrpc_input_packet+0x3f2/0x4d0 rxrpc_io_thread+0x243/0x410 ? __pfx_rxrpc_io_thread+0x10/0x10 kthread+0xcf/0xe0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x24/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK>

AI-Powered Analysis

AILast updated: 06/28/2025, 14:54:30 UTC

Technical Analysis

CVE-2024-53090 is a vulnerability identified in the Linux kernel related to the AFS (Andrew File System) implementation, specifically within the afs_wake_up_async_call() function. The issue arises due to lock recursion involving the ->notify_lock spinlock. When afs_wake_up_async_call() is invoked from the AF_RXRPC context while holding the ->notify_lock, it attempts to take a reference on the afs_call structure to pass it to a work queue. If the afs_call is already queued, an extraneous reference is created that must be released. The release operation, afs_put_call(), can call back into AF_RXRPC via rxrpc_kernel_shutdown_call(), which attempts to reacquire the ->notify_lock. This recursive lock acquisition leads to a spinlock recursion bug, which is a serious kernel-level synchronization error causing kernel oops or crashes. The vulnerability is not common but can cause system instability or denial of service due to kernel panic or deadlock. The provided kernel oops trace confirms the spinlock recursion on CPU0, showing the call stack leading to the issue. The fix involves deferring the problematic call to a workqueue to avoid recursive locking. This vulnerability affects Linux kernel versions prior to the patch and is relevant to systems using AFS and RXRPC subsystems. There are no known exploits in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, the impact of CVE-2024-53090 primarily concerns systems running Linux kernels with AFS and RXRPC enabled, which are typically found in enterprise environments utilizing distributed file systems or legacy network file sharing solutions. The vulnerability can lead to kernel crashes or system instability, resulting in denial of service (DoS). This can disrupt critical services, especially in sectors relying on high availability such as finance, telecommunications, healthcare, and government infrastructure. Although exploitation does not appear trivial and requires specific kernel configurations, affected systems may experience unexpected downtime, impacting business continuity and operational efficiency. Confidentiality and integrity impacts are minimal since the vulnerability is related to locking and resource management rather than direct data exposure or privilege escalation. However, availability degradation can indirectly affect security posture by causing service interruptions and potential cascading failures in dependent systems.

Mitigation Recommendations

To mitigate CVE-2024-53090, European organizations should: 1) Apply the latest Linux kernel patches that address this vulnerability as soon as they become available, prioritizing systems with AFS and RXRPC enabled. 2) Audit and identify systems running affected kernel versions, focusing on those utilizing AFS for file sharing or network communication. 3) Where patching is not immediately feasible, consider disabling AFS or RXRPC modules if they are not critical to operations to reduce exposure. 4) Implement robust monitoring for kernel oops or unusual system crashes that may indicate triggering of this vulnerability. 5) Test patches in controlled environments to ensure stability before wide deployment, given the kernel-level nature of the fix. 6) Maintain updated incident response plans to quickly address potential DoS events caused by this or similar kernel issues. 7) Collaborate with Linux distribution vendors and security communities for timely updates and advisories.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-11-19T17:17:24.981Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9824c4522896dcbdf969

Added to database: 5/21/2025, 9:08:52 AM

Last enriched: 6/28/2025, 2:54:30 PM

Last updated: 8/17/2025, 5:03:58 PM

Views: 9

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats