drm/panfrost: Job should reference MMU not file_priv
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8c8e8cc91a6ffc79865108279a74fd57d9070a17, Kernel 5.11, Kernel 5.14 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Job should reference MMU not file_priv For a while now it's been allowed for a MMU context to outlive it's corresponding panfrost_priv, however the job structure still references panfrost_priv to get hold of the MMU context. If panfrost_priv has been freed this is a use-after-free which I've been able to trigger resulting in a splat. To fix this, drop the reference to panfrost_priv in the job structure and add a direct reference to the MMU structure which is what's actually needed.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <8c8e8cc91a6ffc79865108279a74fd57d9070a17, >=5.10.67 <5.11, >=5.13.19 <5.14, >=5.14.6 <5.15, >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <472dd7ea5e19a1aeabf1711ddc756777e05ee7c2, >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <6e516faf04317db2c46cbec4e3b78b4653a5b109, =5.15, =626adede2642f00c8918999a2451bd0a644ab9b7, =c29485e34e63198dca6289639aa711f99d88e76e, =cf461fa9250a634e8afc4433d82ae0decea8136e | 8c8e8cc91a6ffc79865108279a74fd57d9070a17, 5.11, 5.14, 5.15, 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2, 6e516faf04317db2c46cbec4e3b78b4653a5b109 |
| linux-kernel: Kernel | >=5.13.19 <5.14, >=5.14.6 <5.15, >=5.15.0 <5.17.15, >=5.18.0 <5.18.4, >=5.10.67 <5.11 | 5.14, 5.15, 5.17.15, 5.18.4, 5.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket