drm/radeon: Do not kfree() devres managed rdev
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.12.586.17.86.18In the Linux kernel, the following vulnerability has been resolved:
drm/radeon: Do not kfree() devres managed rdev
Since the allocation of the drivers main structure was changed to devm_drm_dev_alloc() rdev is managed by devres and we shouldn't be calling kfree() on it.
This fixes things exploding if the driver probe fails and devres cleans up the rdev after we already free'd it.
(cherry picked from commit 16c0681617b8a045773d4d87b6140002fa75b03b)
From the CVE record · Linux
The Linux kernel’s Radeon driver can free a device structure that is also managed by devres. If driver probe fails, devres may clean up the already-freed structure, causing a crash. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the Radeon driver should check their kernel version; affected versions are not specified.