Skip to main content

CVE-2024-36965: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2024-36965cvecve-2024-36965
Published: Sat Jun 08 2024 (06/08/2024, 12:52:58 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: remoteproc: mediatek: Make sure IPI buffer fits in L2TCM The IPI buffer location is read from the firmware that we load to the System Companion Processor, and it's not granted that both the SRAM (L2TCM) size that is defined in the devicetree node is large enough for that, and while this is especially true for multi-core SCP, it's still useful to check on single-core variants as well. Failing to perform this check may make this driver perform R/W operations out of the L2TCM boundary, resulting (at best) in a kernel panic. To fix that, check that the IPI buffer fits, otherwise return a failure and refuse to boot the relevant SCP core (or the SCP at all, if this is single core).

AI-Powered Analysis

AILast updated: 06/29/2025, 10:41:53 UTC

Technical Analysis

CVE-2024-36965 is a vulnerability identified in the Linux kernel's remoteproc subsystem, specifically affecting the MediaTek platform integration. The issue arises from improper validation of the Inter-Processor Interrupt (IPI) buffer size relative to the L2TCM (Level 2 Tightly Coupled Memory) SRAM boundaries. The IPI buffer address is obtained from firmware loaded onto the System Companion Processor (SCP). However, the Linux kernel driver did not verify whether the buffer fits within the allocated L2TCM memory region as defined in the device tree. This lack of boundary checking can cause the driver to perform read/write operations outside the L2TCM memory limits. Such out-of-bounds memory access can lead to undefined behavior, including kernel panics or system crashes. The vulnerability is particularly relevant for multi-core SCP configurations but also affects single-core SCP variants. The patch implemented ensures that the driver checks the IPI buffer size against the L2TCM size and refuses to boot the SCP core if the buffer does not fit, thereby preventing out-of-bounds memory access. No known exploits are currently reported in the wild, and the vulnerability was published on June 8, 2024. The affected Linux kernel versions are identified by specific commit hashes, indicating that this is a low-level kernel issue rather than a user-space application vulnerability.

Potential Impact

For European organizations, the impact of CVE-2024-36965 primarily concerns systems running Linux kernels on MediaTek hardware platforms that utilize the remoteproc subsystem and SCP cores. This includes embedded devices, IoT gateways, and potentially some industrial control systems that rely on Linux with MediaTek SoCs. The vulnerability can cause kernel panics or system crashes, leading to denial of service (DoS) conditions. While it does not directly enable privilege escalation or remote code execution, the resulting instability can disrupt critical services, especially in environments requiring high availability such as telecommunications, manufacturing, and critical infrastructure. Organizations deploying Linux-based edge devices or embedded systems with MediaTek chips should be aware of this risk. The absence of known exploits reduces immediate threat levels, but unpatched systems remain vulnerable to accidental or malicious triggering of the bug, potentially causing operational outages.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernel versions to include the patch that validates the IPI buffer size against the L2TCM memory boundaries. Since the vulnerability is at the kernel driver level, kernel upgrades or backported patches from trusted Linux distributions are essential. For embedded and IoT devices where kernel updates may be challenging, vendors should be engaged to provide firmware and kernel patches. Additionally, organizations should audit their device inventories to identify systems using MediaTek SoCs with remoteproc and SCP cores. Implementing monitoring for kernel panics and system crashes can help detect exploitation attempts or accidental triggers. Where possible, isolating vulnerable devices from critical network segments can reduce impact. Finally, testing updates in controlled environments before deployment is recommended to ensure system stability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-05-30T15:25:07.081Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9829c4522896dcbe27f3

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

Last enriched: 6/29/2025, 10:41:53 AM

Last updated: 7/27/2025, 1:52:26 AM

Views: 13

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