CVE-2022-49359
published 2025-02-26CVE-2022-49359: 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…
PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.27%
18.9th percentile
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
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 5.10.67 < 5.11 | 5.11 |
| linux | linux | >= 5.13.19 < 5.14 | 5.14 |
| linux | linux | >= 5.14.6 < 5.15 | 5.15 |
| linux | linux | >= 7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 < 8c8e8cc91a6ffc79865108279a74fd57d9070a17 | 8c8e8cc91a6ffc79865108279a74fd57d9070a17 |
| linux | linux | >= 7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 < 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2 | 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2 |
| linux | linux | >= 7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 < 6e516faf04317db2c46cbec4e3b78b4653a5b109 | 6e516faf04317db2c46cbec4e3b78b4653a5b109 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 5.10.67 < 5.11 | 5.11 |
| linux | linux_kernel | >= 5.13.19 < 5.14 | 5.14 |
| linux | linux_kernel | >= 5.14.6 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-gvx3-72r6-pv8h: 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 a
ghsa_unreviewed·2025-02-27
CVE-2022-49359 [HIGH] CWE-416 GHSA-gvx3-72r6-pv8h: 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 a
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.
OSV
CVE-2022-49359: 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 all
osv·2025-02-26·CVSS 7.8
CVE-2022-49359 [HIGH] CVE-2022-49359: 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 all
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.
Red Hat
kernel: drm/panfrost: Job should reference MMU not file_priv
vendor_redhat·2025-02-26·CVSS 7.8
CVE-2022-49359 [HIGH] CWE-416 kernel: drm/panfrost: Job should reference MMU not file_priv
kernel: drm/panfrost: Job should reference MMU not file_priv
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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7)
Debian
CVE-2022-49359: linux - In the Linux kernel, the following vulnerability has been resolved: drm/panfros...
vendor_debian·2022·CVSS 7.8
CVE-2022-49359 [HIGH] CVE-2022-49359: linux - In the Linux kernel, the following vulnerability has been resolved: drm/panfros...
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.
Scope: local
bookworm: resolved (fixed in 5.18.5-1)
bullseye: open
forky: resolved (fixed in 5.18.5-1)
sid: resolved (fixed in 5.18.5-1)
trixie: resolved (fixed in 5.18.5-1)
No detection rules found.
No public exploits indexed.
2025-02-26
Published