linux-cve-announce - CVE-2022-49359: drm/panfrost: Job should reference MMU not file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022644-CVE-2022-49359-f054@gregkh>
Date: Wed, 26 Feb 2025 03:10:33 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49359: drm/panfrost: Job should reference MMU not file_priv

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.

The Linux kernel CVE team has assigned CVE-2022-49359 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.15 with commit 7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 and fixed in 5.17.15 with commit 8c8e8cc91a6ffc79865108279a74fd57d9070a17
	Issue introduced in 5.15 with commit 7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 and fixed in 5.18.4 with commit 472dd7ea5e19a1aeabf1711ddc756777e05ee7c2
	Issue introduced in 5.15 with commit 7fdc48cc63a30fa3480d18bdd8c5fff2b9b15212 and fixed in 5.19 with commit 6e516faf04317db2c46cbec4e3b78b4653a5b109
	Issue introduced in 5.10.67 with commit c29485e34e63198dca6289639aa711f99d88e76e
	Issue introduced in 5.13.19 with commit 626adede2642f00c8918999a2451bd0a644ab9b7
	Issue introduced in 5.14.6 with commit cf461fa9250a634e8afc4433d82ae0decea8136e

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-49359
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/gpu/drm/panfrost/panfrost_drv.c
	drivers/gpu/drm/panfrost/panfrost_job.c
	drivers/gpu/drm/panfrost/panfrost_job.h


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/8c8e8cc91a6ffc79865108279a74fd57d9070a17
	https://git.kernel.org/stable/c/472dd7ea5e19a1aeabf1711ddc756777e05ee7c2
	https://git.kernel.org/stable/c/6e516faf04317db2c46cbec4e3b78b4653a5b109