drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2fc5703abda201f138faf63bdca743d04dbf4b1a · < dd1801aa01bba1760357f2a641346ae149686713| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()
On the off chance that command stream passed from userspace via ioctl() call to radeon_vce_cs_parse() is weirdly crafted and first command to execute is to encode (case 0x03000001), the function in question will attempt to call radeon_vce_cs_reloc() with size argument that has not been properly initialized. Specifically, 'size' will point to 'tmp' variable before the latter had a chance to be assigned any value.
Play it safe and init 'tmp' with 0, thus ensuring that radeon_vce_cs_reloc() will catch an early error in cases like these.
Found by Linux Verification Center (linuxtesting.org) with static analysis tool SVACE.
(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)
From the CVE record · Linux
The Linux kernel’s Radeon VCE command parser can pass an uninitialized size to a relocation function when a specially crafted command stream starts with an encode command. A local user can supply that stream through an ioctl call; the input does not specify a further impact.
Engineers running Linux kernels with the Radeon VCE driver should check their versions; affected versions were not specified.