Tracker / CVE-2022-49359
CVE-2022-49359
High 7.8
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 products and versions
| linux | linux_kernel |
|---|---|
| linux | linux_kernel · 5.10.67 → 5.11 |
| linux | linux_kernel · 5.13.19 → 5.14 |
| linux | linux_kernel · 5.14.6 → 5.17.15 |
| linux | linux_kernel · 5.18 → 5.18.4 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.