Go to homepageCyberStrike

Menu

Star on GitHub · 3.4k
Sign inDownload

CVE-2024-36965

7.8 · HIGH

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…

Published Jun 8, 2024EPSS 0.22%

Overview

CVE-2024-36965 is a high-severity vulnerability. It was published on June 8, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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).

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/00548ac6b14428719c970ef90adae2b3b48c0cdfRefgit.kernel.org/stable/c/1d9e2de24533daca36cbf09e8d8596bf72b526b2Refgit.kernel.org/stable/c/26c6d7dc8c6a9fde9d362ab2eef6390efeff145eRefgit.kernel.org/stable/c/331f91d86f71d0bb89a44217cc0b2a22810bbd42Refgit.kernel.org/stable/c/36c79eb4845551e9f6d28c663b38ce0ab03b84a9Refgit.kernel.org/stable/c/838b49e211d59fa827ff9df062d4020917cffbdfRefgit.kernel.org/stable/c/00548ac6b14428719c970ef90adae2b3b48c0cdfRefgit.kernel.org/stable/c/1d9e2de24533daca36cbf09e8d8596bf72b526b2Refgit.kernel.org/stable/c/26c6d7dc8c6a9fde9d362ab2eef6390efeff145eRefgit.kernel.org/stable/c/331f91d86f71d0bb89a44217cc0b2a22810bbd42

How CyberStrike helps

Frequently asked questions

What is CVE-2024-36965?

CVE-2024-36965 is a high-severity vulnerability. It was published on June 8, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2024-36965?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2024-36965?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-36965?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-36965 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999
Watch the demo →