drm/panthor: harden firmware build-info bounds checks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.517.2.57.3In the Linux kernel, the following vulnerability has been resolved:
drm/panthor: harden firmware build-info bounds checks
panthor_fw_read_build_info() checks whether the metadata range fits in the firmware image with hdr.meta_start + hdr.meta_size. Both fields are u32, so the addition can wrap and let an out-of-bounds range pass validation.
The function also reads the "git_sha: " prefix without first checking that the metadata is long enough, and meta_size == 0 can underflow the NULL terminator index.
Use subtraction-based bounds checking and reject metadata that is too short to contain the expected prefix and trailing NULL byte.
From the CVE record · Linux
The Linux kernel's drm/panthor firmware build-info parser has bounds-checking errors that can let an out-of-bounds metadata range pass validation. Short or empty metadata can also cause an out-of-bounds prefix read or an underflow when indexing the NULL terminator. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel with drm/panthor should check their exposure; affected versions are not specified.