Skip to main content

CVE-2024-53215: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-53215cvecve-2024-53215
Published: Fri Dec 27 2024 (12/27/2024, 13:50:00 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: svcrdma: fix miss destroy percpu_counter in svc_rdma_proc_init() There's issue as follows: RPC: Registered rdma transport module. RPC: Registered rdma backchannel transport module. RPC: Unregistered rdma transport module. RPC: Unregistered rdma backchannel transport module. BUG: unable to handle page fault for address: fffffbfff80c609a PGD 123fee067 P4D 123fee067 PUD 123fea067 PMD 10c624067 PTE 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI RIP: 0010:percpu_counter_destroy_many+0xf7/0x2a0 Call Trace: <TASK> __die+0x1f/0x70 page_fault_oops+0x2cd/0x860 spurious_kernel_fault+0x36/0x450 do_kern_addr_fault+0xca/0x100 exc_page_fault+0x128/0x150 asm_exc_page_fault+0x26/0x30 percpu_counter_destroy_many+0xf7/0x2a0 mmdrop+0x209/0x350 finish_task_switch.isra.0+0x481/0x840 schedule_tail+0xe/0xd0 ret_from_fork+0x23/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> If register_sysctl() return NULL, then svc_rdma_proc_cleanup() will not destroy the percpu counters which init in svc_rdma_proc_init(). If CONFIG_HOTPLUG_CPU is enabled, residual nodes may be in the 'percpu_counters' list. The above issue may occur once the module is removed. If the CONFIG_HOTPLUG_CPU configuration is not enabled, memory leakage occurs. To solve above issue just destroy all percpu counters when register_sysctl() return NULL.

AI-Powered Analysis

AILast updated: 06/28/2025, 10:54:52 UTC

Technical Analysis

CVE-2024-53215 is a vulnerability identified in the Linux kernel, specifically related to the svcrdma module, which handles RDMA (Remote Direct Memory Access) transport for RPC (Remote Procedure Call) services. The issue arises in the svc_rdma_proc_init() function where percpu counters are initialized but may not be properly destroyed if the register_sysctl() call returns NULL. This improper cleanup leads to residual percpu counters remaining in the system when the module is removed, particularly if the CONFIG_HOTPLUG_CPU kernel configuration is enabled. This can cause a kernel BUG due to an unhandled page fault, as indicated by the kernel oops trace provided. If CONFIG_HOTPLUG_CPU is disabled, the vulnerability manifests as a memory leak instead. The root cause is that svc_rdma_proc_cleanup() does not destroy the percpu counters initialized in svc_rdma_proc_init() when register_sysctl() fails, leading to resource mismanagement. The vulnerability can cause kernel crashes (denial of service) or memory exhaustion, impacting system stability. The fix involves ensuring all percpu counters are destroyed when register_sysctl() returns NULL, preventing residual nodes and memory leaks. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet. The affected versions are specific Linux kernel commits identified by the hash df971cd853c05778ae1175e8aeb80a04bb9d4be5, indicating a narrow range of impacted kernel builds.

Potential Impact

For European organizations, this vulnerability primarily threatens the stability and availability of Linux-based systems that utilize the svcrdma module, which is common in high-performance computing, data centers, and environments relying on RDMA for low-latency network communication. A successful exploitation could lead to kernel crashes causing denial of service, potentially disrupting critical services and applications. Memory leaks could degrade system performance over time, leading to increased maintenance and downtime. Organizations running Linux kernels with CONFIG_HOTPLUG_CPU enabled are at higher risk of system crashes, while those without it face memory exhaustion issues. Given the widespread use of Linux in European enterprises, cloud providers, and research institutions, the vulnerability could impact a broad range of sectors including finance, telecommunications, manufacturing, and government infrastructure. Although no active exploits are known, the vulnerability's presence in kernel-level code means that exploitation could be severe if triggered, especially in multi-tenant or virtualized environments where stability is paramount.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2024-53215 as soon as it becomes available. Until patches are applied, administrators should audit systems for the use of the svcrdma module and consider disabling it if RDMA transport is not required, reducing the attack surface. Monitoring kernel logs for oops or page fault errors related to percpu_counter_destroy_many can help detect attempts to trigger this vulnerability. For systems with CONFIG_HOTPLUG_CPU enabled, careful management of CPU hotplug events and module unloading procedures is advised to minimize risk. Additionally, organizations should implement robust kernel crash recovery and memory monitoring tools to quickly respond to instability or memory leaks. In environments where svcrdma is critical, testing kernel updates in staging before production deployment is recommended to ensure stability. Finally, maintaining strict access controls and limiting module loading/unloading privileges to trusted administrators will reduce the risk of exploitation.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 682d9823c4522896dcbdef71

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

Last enriched: 6/28/2025, 10:54:52 AM

Last updated: 8/14/2025, 12:48:12 PM

Views: 12

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