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).
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.160, 6.1.92, 6.6.32, 6.8.11, 6.9.2
- CVEs
- CVE-2024-36965
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 15:46 UTC · Revision 1
Source evidence
remoteproc: mediatek: Make sure IPI buffer fits in L2TCM
core-osv · Original sourcePublished 8 Jun 2024, 12:52 UTC
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).
osv:CVE-2024-36965
Kernel
Fixed versions: 5.15.160, 6.1.92, 6.6.32, 6.8.11, 6.9.2
Complete source record
{
"id": "3cd3e1a57febfd1d6d59d6f2aeef449ba0dddf590dea0ba2ad84f2608afbefc2",
"url": "https://osv.dev/vulnerability/CVE-2024-36965",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "remoteproc: mediatek: Make sure IPI buffer fits in L2TCM",
"summary": "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).",
"evidence": "osv:CVE-2024-36965",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.92",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.32",
"evidence": "/affected/1/ranges"
},
{
"value": "6.8.11",
"evidence": "/affected/1/ranges"
},
{
"value": "6.9.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-36965",
"aliases": [
"CVE-2024-36965"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3efa0ea743b77d1611501f7d8b4f320d032d73ae"
},
{
"fixed": "00548ac6b14428719c970ef90adae2b3b48c0cdf"
},
{
"fixed": "1d9e2de24533daca36cbf09e8d8596bf72b526b2"
},
{
"fixed": "26c6d7dc8c6a9fde9d362ab2eef6390efeff145e"
},
{
"fixed": "838b49e211d59fa827ff9df062d4020917cffbdf"
},
{
"fixed": "36c79eb4845551e9f6d28c663b38ce0ab03b84a9"
},
{
"fixed": "331f91d86f71d0bb89a44217cc0b2a22810bbd42"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36965.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.92"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.32"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.8.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.9.0"
},
{
"fixed": "6.9.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36965.json"
}
}
],
"modified": "2026-10-28T02:30:30.208666510Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/00548ac6b14428719c970ef90adae2b3b48c0cdf",
"https://git.kernel.org/stable/c/1d9e2de24533daca36cbf09e8d8596bf72b526b2",
"https://git.kernel.org/stable/c/26c6d7dc8c6a9fde9d362ab2eef6390efeff145e",
"https://git.kernel.org/stable/c/331f91d86f71d0bb89a44217cc0b2a22810bbd42",
"https://git.kernel.org/stable/c/36c79eb4845551e9f6d28c663b38ce0ab03b84a9",
"https://git.kernel.org/stable/c/838b49e211d59fa827ff9df062d4020917cffbdf",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36965.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-36965",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36965.json"
}
},
"related_cves": [
{
"value": "CVE-2024-36965",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 496967,
"published_at": "2024-06-08T12:52:58.404+00:00"
}