Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-36965, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 3efa0ea743b77d1611501f7d8b4f320d032d73ae – < 00548ac6b14428719c970ef90adae2b3b48c0cdf
    • affected 3efa0ea743b77d1611501f7d8b4f320d032d73ae – < 1d9e2de24533daca36cbf09e8d8596bf72b526b2
    • affected 3efa0ea743b77d1611501f7d8b4f320d032d73ae – < 26c6d7dc8c6a9fde9d362ab2eef6390efeff145e
    • affected 3efa0ea743b77d1611501f7d8b4f320d032d73ae – < 838b49e211d59fa827ff9df062d4020917cffbdf
    • affected 3efa0ea743b77d1611501f7d8b4f320d032d73ae – < 36c79eb4845551e9f6d28c663b38ce0ab03b84a9
    • affected 3efa0ea743b77d1611501f7d8b4f320d032d73ae – < 331f91d86f71d0bb89a44217cc0b2a22810bbd42
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.160 – ≤ 5.15.*
    • unaffected 6.1.92 – ≤ 6.1.*
    • unaffected 6.6.32 – ≤ 6.6.*
    • unaffected 6.8.11 – ≤ 6.8.*
    • unaffected 6.9.2 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-36965 badge
[![CVE-2024-36965](https://cveledger.app/badge/CVE-2024-36965.svg)](https://cveledger.app/cve/CVE-2024-36965)

Record last updated .