Linux Kernel up to 5.17.14/5.18.3 panfrost file_priv use after free

Summaryinfo

A vulnerability labeled as critical has been found in Linux Kernel up to 5.17.14/5.18.3. Affected is the function file_priv of the component panfrost. The manipulation results in use after free. This vulnerability is reported as CVE-2022-49359. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.17.14/5.18.3. Affected is the function file_priv of the component panfrost. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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 advisory is available at git.kernel.org. This vulnerability is traded as CVE-2022-49359 since 02/26/2025. The exploitability is told to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 03/05/2025).

The vulnerability scanner Nessus provides a plugin with the ID 225800 (Linux Distros Unpatched Vulnerability : CVE-2022-49359), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.17.15 or 5.18.4 eliminates this vulnerability. Applying the patch 8c8e8cc91a6ffc79865108279a74fd57d9070a17/472dd7ea5e19a1aeabf1711ddc756777e05ee7c2/6e516faf04317db2c46cbec4e3b78b4653a5b109 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (225800). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.17.0
• 5.17.1
• 5.17.2
• 5.17.3
• 5.17.4
• 5.17.5
• 5.17.6
• 5.17.7
• 5.17.8
• 5.17.9
• 5.17.10
• 5.17.11
• 5.17.12
• 5.17.13
• 5.17.14
• 5.18.0
• 5.18.1
• 5.18.2
• 5.18.3

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion