drm/panthor: reject firmware sections with oversized data
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: reject firmware sections with oversized data In panthor_fw_load_section_entry(), the data size to copy is calculated without validating it against the allocated section_size: section->data.size = hdr.data.end - hdr.data.start; If a crafted firmware sets data.size larger than the allocated memory, this could cause a heap buffer overflow in panthor_fw_init_section_mem() memcpy(section->mem->kmap, section->data.buf, section->data.size); Additionally, if the section->data.size exceeds the BO size, could this memset underflow the size calculation, leading to a massive out-of-bounds zeroing of kernel memory? memset(section->mem->kmap + section->data.size, 0, panthor_kernel_bo_size(section->mem) - section->data.size); Reject section entries whose initial data is larger than the section size.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.103, 6.18.44, 7.1.8
- CVEs
- CVE-2026-74452
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 11:00 UTC · Revision 1
Source evidence
drm/panthor: reject firmware sections with oversized data
core-osv · Original sourcePublished 15 Aug 2026, 12:26 UTC
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: reject firmware sections with oversized data In panthor_fw_load_section_entry(), the data size to copy is calculated without validating it against the allocated section_size: section->data.size = hdr.data.end - hdr.data.start; If a crafted firmware sets data.size larger than the allocated memory, this could cause a heap buffer overflow in panthor_fw_init_section_mem() memcpy(section->mem->kmap, section->data.buf, section->data.size); Additionally, if the section->data.size exceeds the BO size, could this memset underflow the size calculation, leading to a massive out-of-bounds zeroing of kernel memory? memset(section->mem->kmap + section->data.size, 0, panthor_kernel_bo_size(section->mem) - section->data.size); Reject section entries whose initial data is larger than the section size.
osv:CVE-2026-74452
Kernel
Fixed versions: 6.12.103, 6.18.44, 7.1.8
Complete source record
{
"id": "6aea2cb70a53c61be49a14a405bdc9cd71b73b227206f62991ac6da5f9436b8c",
"url": "https://osv.dev/vulnerability/CVE-2026-74452",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "drm/panthor: reject firmware sections with oversized data",
"summary": "In the Linux kernel, the following vulnerability has been resolved: drm/panthor: reject firmware sections with oversized data In panthor_fw_load_section_entry(), the data size to copy is calculated without validating it against the allocated section_size: section->data.size = hdr.data.end - hdr.data.start; If a crafted firmware sets data.size larger than the allocated memory, this could cause a heap buffer overflow in panthor_fw_init_section_mem() memcpy(section->mem->kmap, section->data.buf, section->data.size); Additionally, if the section->data.size exceeds the BO size, could this memset underflow the size calculation, leading to a massive out-of-bounds zeroing of kernel memory? memset(section->mem->kmap + section->data.size, 0, panthor_kernel_bo_size(section->mem) - section->data.size); Reject section entries whose initial data is larger than the section size.",
"evidence": "osv:CVE-2026-74452",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.12.103",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.44",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-74452",
"aliases": [
"CVE-2026-74452"
],
"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": "2718d91816eeed03c09c8abe872e45f59078768c"
},
{
"fixed": "0e57165ca025a67d8dfd17efd2765fdd4925fdab"
},
{
"fixed": "2a761b9be5863e1d26a584f0c2d1e114a684ed9a"
},
{
"fixed": "7f4674d986c15c74327cb6ac6e2e2afecf061e04"
},
{
"fixed": "a3caaa06809248b996254be5b47e10804a3494e2"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74452.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.10.0"
},
{
"fixed": "6.12.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74452.json"
}
}
],
"modified": "2026-10-28T02:30:50.548762410Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0e57165ca025a67d8dfd17efd2765fdd4925fdab",
"https://git.kernel.org/stable/c/2a761b9be5863e1d26a584f0c2d1e114a684ed9a",
"https://git.kernel.org/stable/c/7f4674d986c15c74327cb6ac6e2e2afecf061e04",
"https://git.kernel.org/stable/c/a3caaa06809248b996254be5b47e10804a3494e2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74452.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-74452",
"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/2026/74xxx/CVE-2026-74452.json"
}
},
"related_cves": [
{
"value": "CVE-2026-74452",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 519073,
"published_at": "2026-08-15T12:26:56.331+00:00"
}