Skip to main content

CVE-2024-44997: Vulnerability in Linux Linux

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

Description

In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb() When there are multiple ap interfaces on one band and with WED on, turning the interface down will cause a kernel panic on MT798X. Previously, cb_priv was freed in mtk_wed_setup_tc_block() without marking NULL,and mtk_wed_setup_tc_block_cb() didn't check the value, too. Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL in mtk_wed_setup_tc_block_cb(). ---------- Unable to handle kernel paging request at virtual address 0072460bca32b4f5 Call trace: mtk_wed_setup_tc_block_cb+0x4/0x38 0xffffffc0794084bc tcf_block_playback_offloads+0x70/0x1e8 tcf_block_unbind+0x6c/0xc8 ... ---------

AI-Powered Analysis

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

Technical Analysis

CVE-2024-44997 is a use-after-free vulnerability identified in the Linux kernel's MediaTek Wireless Ethernet Driver (mtk_wed), specifically affecting the function mtk_wed_setup_tc_block_cb(). The issue arises when multiple access point (AP) interfaces operate on the same wireless band with Wireless Ethernet Driver (WED) enabled. Under these conditions, shutting down one of the interfaces triggers a kernel panic on devices using the MT798X chipset. The root cause is that the callback private data pointer (cb_priv) is freed in mtk_wed_setup_tc_block() without being set to NULL afterward. Consequently, mtk_wed_setup_tc_block_cb() does not verify whether cb_priv is NULL before dereferencing it, leading to a use-after-free scenario. This results in an invalid kernel memory access, causing a kernel panic and potential denial of service. The vulnerability is specific to the MediaTek MT798X platform integrated into the Linux kernel's networking stack. The patch involves assigning NULL to cb_priv immediately after freeing it and adding a NULL check in the callback function to prevent dereferencing freed memory. The kernel panic trace shows the failure occurs during traffic control block operations, indicating the vulnerability impacts network interface management when multiple AP interfaces coexist on the same band with WED enabled. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with MediaTek MT798X chipsets that utilize multiple AP interfaces on the same band with WED enabled. The impact includes potential kernel panics leading to system crashes and denial of service, which could disrupt network connectivity and critical services relying on these wireless interfaces. Organizations deploying embedded Linux devices, such as routers, gateways, or IoT infrastructure using affected MediaTek chipsets, may face operational instability. While the vulnerability does not appear to allow remote code execution or privilege escalation directly, the denial of service could be exploited to disrupt network availability, impacting business continuity. In sectors like telecommunications, manufacturing, or critical infrastructure where such hardware is deployed, this could lead to significant operational downtime. Additionally, the kernel panic could complicate incident response and recovery, especially in environments with limited physical access to affected devices. Given the specificity of the vulnerability to MediaTek MT798X and WED configurations, the broader impact on general Linux server infrastructure is limited but should not be overlooked in embedded and network edge devices.

Mitigation Recommendations

To mitigate CVE-2024-44997, European organizations should: 1) Identify and inventory all Linux-based devices using MediaTek MT798X chipsets, particularly those configured with multiple AP interfaces on the same band and WED enabled. 2) Apply the official Linux kernel patches that fix the use-after-free by setting cb_priv to NULL after free and adding NULL checks in mtk_wed_setup_tc_block_cb(). If official patches are not yet available, monitor Linux kernel mailing lists and vendor advisories for updates. 3) Temporarily disable WED or reduce the number of AP interfaces operating simultaneously on the same band as a workaround to prevent triggering the vulnerability. 4) Implement robust monitoring for kernel panics and unexpected reboots on affected devices to detect exploitation attempts or instability. 5) For embedded devices, coordinate with hardware vendors or device manufacturers to obtain updated firmware incorporating the kernel fix. 6) Harden network segmentation and access controls to limit exposure of vulnerable devices to untrusted networks, reducing the risk of remote triggering. 7) Conduct thorough testing of patches in staging environments to ensure stability before deployment in production, given the critical nature of kernel-level changes.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 682d9826c4522896dcbe0e2b

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

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

Last updated: 8/14/2025, 3:53:10 PM

Views: 15

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