drm/amd/display: avoid using null object of framebuffer
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 093ee72ed35c2338c87c26b6ba6f0b7789c9e14e, Kernel 3b9a33235c773c7a3768060cf1d2cf8a9153bc37, Kernel 49e1b214f3239b78967c6ddb8f8ec47ae047b051 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: avoid using null object of framebuffer Instead of using state->fb->obj[0] directly, get object from framebuffer by calling drm_gem_fb_get_obj() and return error code when object is null to avoid using null object of framebuffer. (cherry picked from commit 73dd0ad9e5dad53766ea3e631303430116f834b3)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.0, >=5d945cbcd4b16a29d6470a80dfb19738f9a4319f <093ee72ed35c2338c87c26b6ba6f0b7789c9e14e, >=5d945cbcd4b16a29d6470a80dfb19738f9a4319f <3b9a33235c773c7a3768060cf1d2cf8a9153bc37, >=5d945cbcd4b16a29d6470a80dfb19738f9a4319f <49e1b214f3239b78967c6ddb8f8ec47ae047b051, >=5d945cbcd4b16a29d6470a80dfb19738f9a4319f <f6f5e39a3fe7cbdba190f42b28b40bdff03c8cf0 | 093ee72ed35c2338c87c26b6ba6f0b7789c9e14e, 3b9a33235c773c7a3768060cf1d2cf8a9153bc37, 49e1b214f3239b78967c6ddb8f8ec47ae047b051, f6f5e39a3fe7cbdba190f42b28b40bdff03c8cf0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket