LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36965: remoteproc: mediatek: Make sure IPI buffer fits in L2TCM

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-36965 is a Linux kernel bug in MediaTek remote processor support. The driver trusted a firmware-provided IPI buffer location without confirming it fit inside expected SRAM. On affected MediaTek systems, this can cause out-of-bounds kernel reads or writes and at least a system crash.

Executive priority

Treat as targeted operational-risk remediation, not broad emergency response. Prioritize affected MediaTek Linux devices where kernel panic could disrupt business operations, especially embedded, mobile, appliance, or edge deployments.

Technical view

The MediaTek remoteproc driver reads the SCP IPI buffer address from loaded firmware. Without validating the buffer against the L2TCM size from devicetree, the driver can access memory outside L2TCM. The upstream fix refuses to boot the SCP core when the IPI buffer does not fit.

Likely exposure

Exposure appears limited to Linux systems using MediaTek System Companion Processor remoteproc support. General Linux servers without this hardware or driver path are unlikely to be affected. The bundle does not provide CPEs or distributor-specific package ranges.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit details, or a CVSS score. The documented impact is out-of-bounds kernel read/write, with kernel panic explicitly named as a likely outcome.

Researcher notes

Key evidence is the upstream Linux fix rationale. The attack preconditions are not fully described in the bundle, so avoid assuming remote exploitability. Focus analysis on firmware-provided IPI buffer metadata, L2TCM devicetree sizing, and SCP boot refusal behavior after patching.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check your Linux distribution or device vendor advisory for backported patches.
  • Prioritize MediaTek-based devices using SCP remoteproc functionality.
  • If no update exists, follow vendor guidance before disabling hardware functionality.

Validation and detection

  • Inventory Linux devices with MediaTek SoCs or SCP remoteproc support.
  • Compare running kernel builds against vendor-fixed packages or referenced stable commits.
  • Review boot logs for MediaTek SCP remoteproc initialization failures or crashes.
  • Confirm patched kernels reject oversized SCP IPI buffers during validation testing.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-36965 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3efa0ea743b77d1611501f7d8b4f320d032d73ae, 3efa0ea743b77d1611501f7d8b4f320d032d73ae, 3efa0ea743b77d1611501f7d8b4f320d032d73ae, 3efa0ea743b77d1611501f7d8b4f320d032d73ae, 3efa0ea743b77d1611501f7d8b4f320d032d73ae, 3efa0ea743b77d1611501f7d8b4f320d032d73aeunaffected
LinuxLinux5.11, 0, 5.15.160, 6.1.92, 6.6.32, 6.8.11, 6.9.2, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.