Bug 2347876 (CVE-2022-49359)

Summary: CVE-2022-49359 kernel: drm/panfrost: Job should reference MMU not file_priv
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: dfreiber, drow, jburrell, vkumar
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2025-02-26 03:09:49 UTC 
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.
Comment 1 Avinash Hanwate 2025-02-26 10:59:02 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022644-CVE-2022-49359-f054@gregkh/T
Comment 2 Avinash Hanwate 2025-02-26 15:22:10 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022644-CVE-2022-49359-f054@gregkh/T