Answer in brief
CVE-2024-36965 records a Unknown severity vulnerability in remoteproc: mediatek: Make sure IPI buffer fits in L2TCM. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <00548ac6b14428719c970ef90adae2b3b48c0cdf || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <1d9e2de24533daca36cbf09e8d8596bf72b526b2 || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <26c6d7dc8c6a9fde9d362ab2eef6390efeff145e || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <838b49e211d59fa827ff9df062d4020917cffbdf || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <36c79eb4845551e9f6d28c663b38ce0ab03b84a9 || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <331f91d86f71d0bb89a44217cc0b2a22810bbd42 | 00548ac6b14428719c970ef90adae2b3b48c0cdf, 1d9e2de24533daca36cbf09e8d8596bf72b526b2, 26c6d7dc8c6a9fde9d362ab2eef6390efeff145e, 838b49e211d59fa827ff9df062d4020917cffbdf, 36c79eb4845551e9f6d28c663b38ce0ab03b84a9, 331f91d86f71d0bb89a44217cc0b2a22810bbd42 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Jun 8, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-36965 records a Unknown severity vulnerability in remoteproc: mediatek: Make sure IPI buffer fits in L2TCM. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <00548ac6b14428719c970ef90adae2b3b48c0cdf || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <1d9e2de24533daca36cbf09e8d8596bf72b526b2 || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <26c6d7dc8c6a9fde9d362ab2eef6390efeff145e || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <838b49e211d59fa827ff9df062d4020917cffbdf || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <36c79eb4845551e9f6d28c663b38ce0ab03b84a9 || >=3efa0ea743b77d1611501f7d8b4f320d032d73ae <331f91d86f71d0bb89a44217cc0b2a22810bbd42 | 00548ac6b14428719c970ef90adae2b3b48c0cdf, 1d9e2de24533daca36cbf09e8d8596bf72b526b2, 26c6d7dc8c6a9fde9d362ab2eef6390efeff145e, 838b49e211d59fa827ff9df062d4020917cffbdf, 36c79eb4845551e9f6d28c663b38ce0ab03b84a9, 331f91d86f71d0bb89a44217cc0b2a22810bbd42 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Jun 8, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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).
Quoted source text, attributed separately from HOL analysis.