Skip to main content

CVE-2024-45001: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-45001cvecve-2024-45001
Published: Wed Sep 04 2024 (09/04/2024, 19:54:44 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix RX buf alloc_size alignment and atomic op panic The MANA driver's RX buffer alloc_size is passed into napi_build_skb() to create SKB. skb_shinfo(skb) is located at the end of skb, and its alignment is affected by the alloc_size passed into napi_build_skb(). The size needs to be aligned properly for better performance and atomic operations. Otherwise, on ARM64 CPU, for certain MTU settings like 4000, atomic operations may panic on the skb_shinfo(skb)->dataref due to alignment fault. To fix this bug, add proper alignment to the alloc_size calculation. Sample panic info: [ 253.298819] Unable to handle kernel paging request at virtual address ffff000129ba5cce [ 253.300900] Mem abort info: [ 253.301760] ESR = 0x0000000096000021 [ 253.302825] EC = 0x25: DABT (current EL), IL = 32 bits [ 253.304268] SET = 0, FnV = 0 [ 253.305172] EA = 0, S1PTW = 0 [ 253.306103] FSC = 0x21: alignment fault Call trace: __skb_clone+0xfc/0x198 skb_clone+0x78/0xe0 raw6_local_deliver+0xfc/0x228 ip6_protocol_deliver_rcu+0x80/0x500 ip6_input_finish+0x48/0x80 ip6_input+0x48/0xc0 ip6_sublist_rcv_finish+0x50/0x78 ip6_sublist_rcv+0x1cc/0x2b8 ipv6_list_rcv+0x100/0x150 __netif_receive_skb_list_core+0x180/0x220 netif_receive_skb_list_internal+0x198/0x2a8 __napi_poll+0x138/0x250 net_rx_action+0x148/0x330 handle_softirqs+0x12c/0x3a0

AI-Powered Analysis

AILast updated: 06/28/2025, 23:40:21 UTC

Technical Analysis

CVE-2024-45001 is a vulnerability identified in the Linux kernel's MANA network driver, specifically related to the RX buffer allocation size alignment in the napi_build_skb() function. The vulnerability arises because the size of the RX buffer allocation (alloc_size) passed to napi_build_skb() is not properly aligned. This misalignment affects skb_shinfo(skb), a structure located at the end of the socket buffer (SKB), which is critical for managing network packet metadata. On ARM64 architectures, certain Maximum Transmission Unit (MTU) settings, such as an MTU of 4000 bytes, can trigger atomic operation panics due to alignment faults on the skb_shinfo(skb)->dataref field. This results in kernel panics caused by alignment faults during atomic operations, which are essential for performance and correctness in concurrent environments. The vulnerability manifests as a kernel paging request failure and an alignment fault, leading to system instability and potential denial of service (DoS). The root cause is the lack of proper alignment in the alloc_size calculation, which has been addressed by adding the necessary alignment adjustments to prevent these panics. The issue is specific to ARM64 CPUs and certain network configurations, making it a niche but critical problem for affected systems. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, the impact of CVE-2024-45001 can be significant, particularly for those relying on ARM64-based Linux systems in network infrastructure roles, such as routers, firewalls, or specialized network appliances. The vulnerability can cause kernel panics leading to system crashes and denial of service, disrupting network operations and potentially affecting business continuity. Organizations with high network throughput requirements or custom MTU configurations (e.g., 4000 bytes) are at higher risk. The instability could affect critical services, including cloud infrastructure, telecommunications, and industrial control systems that use ARM64 Linux kernels. While the vulnerability does not directly expose data confidentiality or integrity, the availability impact is substantial. Recovery from kernel panics may require manual intervention or system reboots, increasing operational overhead and risk of downtime. Given the increasing adoption of ARM64 architectures in data centers and edge computing within Europe, this vulnerability poses a tangible risk to network reliability and service availability.

Mitigation Recommendations

To mitigate CVE-2024-45001, European organizations should: 1) Apply the latest Linux kernel patches that include the alignment fix for the MANA driver as soon as they become available. Monitor Linux kernel release notes and security advisories for updates addressing this issue. 2) Review and, if possible, avoid using non-standard MTU sizes such as 4000 on ARM64 systems until patches are applied, as these configurations trigger the vulnerability. 3) Implement robust monitoring for kernel panics and system crashes on ARM64 Linux hosts, enabling rapid detection and response to potential exploitation or instability. 4) For critical network devices running ARM64 Linux kernels, consider deploying redundancy and failover mechanisms to minimize service disruption in case of kernel panics. 5) Conduct thorough testing of network configurations and kernel versions in staging environments before deploying to production, ensuring that the vulnerability is not triggered under operational conditions. 6) Engage with hardware and software vendors to confirm ARM64 Linux kernel versions in use are patched and supported. 7) Maintain updated backups and incident response plans to handle potential downtime caused by this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-08-21T05:34:56.678Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9826c4522896dcbe0e43

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

Last enriched: 6/28/2025, 11:40:21 PM

Last updated: 8/18/2025, 3:52:54 PM

Views: 17

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