# CVE-2022-49359: linux: In the Linux kernel, the following vulnerability has been resolved:  drm/panfrost: Job should reference MMU not file_...

CVE-2022-49359 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49359, released February 26, 2025. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2022-49359
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0027
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 26, 2025

## Description

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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 5.18.5-1 | [DEBIAN-CVE-2022-49359](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49359.md) | Feb 26, 2025 |
| Linux | linux Debian 13.5 (trixie) | 5.18.5-1 | [DEBIAN-CVE-2022-49359](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49359.md) | Feb 26, 2025 |
| Linux | linux Debian 14 | 5.18.5-1 | [DEBIAN-CVE-2022-49359](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49359.md) | Feb 26, 2025 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.