Answer in brief
CVE-2022-49359 records a Unknown severity vulnerability in drm/panfrost: Job should reference MMU not file_priv. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <8c8e8cc91a6ffc79865108279a74fd57d9070a17 || >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <472dd7ea5e19a1aeabf1711ddc756777e05ee7c2 || >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <6e516faf04317db2c46cbec4e3b78b4653a5b109 || c29485e34e63198dca6289639aa711f99d88e76e || 626adede2642f00c8918999a2451bd0a644ab9b7 || cf461fa9250a634e8afc4433d82ae0decea8136e || >=5.10.67 <5.11 || >=5.13.19 <5.14 || >=5.14.6 <5.15 | 8c8e8cc91a6ffc79865108279a74fd57d9070a17, 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2, 6e516faf04317db2c46cbec4e3b78b4653a5b109, 5.11, 5.14, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49359 records a Unknown severity vulnerability in drm/panfrost: Job should reference MMU not file_priv. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <8c8e8cc91a6ffc79865108279a74fd57d9070a17 || >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <472dd7ea5e19a1aeabf1711ddc756777e05ee7c2 || >=7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 <6e516faf04317db2c46cbec4e3b78b4653a5b109 || c29485e34e63198dca6289639aa711f99d88e76e || 626adede2642f00c8918999a2451bd0a644ab9b7 || cf461fa9250a634e8afc4433d82ae0decea8136e || >=5.10.67 <5.11 || >=5.13.19 <5.14 || >=5.14.6 <5.15 | 8c8e8cc91a6ffc79865108279a74fd57d9070a17, 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2, 6e516faf04317db2c46cbec4e3b78b4653a5b109, 5.11, 5.14, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.