Linux Kernel up to 5.18.2 mdp5_pipe_release initialization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.9$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.18.2 and classified as problematic. Affected by this vulnerability is the function mdp5_pipe_release. The manipulation results in initialization. This vulnerability is known as CVE-2022-49490. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 5.18.2. Affected is the function mdp5_pipe_release. The manipulation with an unknown input leads to a initialization vulnerability. CWE is classifying the issue as CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected mdp5_get_global_state runs the risk of hitting a -EDEADLK when acquiring the modeset lock, but currently mdp5_pipe_release doesn't check for if an error is returned. Because of this, there is a possibility of mdp5_pipe_release hitting a NULL dereference error. To avoid this, let's have mdp5_pipe_release check if mdp5_get_global_state returns an error and propogate that error. Changes since v1: - Separated declaration and initialization of *new_state to avoid compiler warning - Fixed some spelling mistakes in commit message Changes since v2: - Return 0 in case where hwpipe is NULL as this is considered normal behavior - Added 2nd patch in series to fix a similar NULL dereference issue in mdp5_mixer_release Patchwork: https://patchwork.freedesktop.org/patch/485179/

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2022-49490 since 02/26/2025. The exploitability is told to be difficult. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 232643 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14 or 5.18.3 eliminates this vulnerability. Applying the patch 776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b/b2aa2c4efe93e2580d6a8774b04fe2b99756a322/49dc28b4b2e28ef7564e355c91487996c1cbebd7/04bef5f1ba8ea6d7c1c8f5f65e0395c62db59cb8/19964dfb39bda4d7716a71009488f0668ecbcf52/33dc5aac46e0fad8f5eb193e5906ed0eb6b66ceb/d59be579fa932c46b908f37509f319cbd4ca9a68 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 (232643). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Initialization
CWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 232643
Nessus Name: SUSE SLES12 Security Update : kernel (SUSE-SU-2025:0834-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 4.19.247/5.4.198/5.10.121/5.15.46/5.17.14/5.18.3
Patch: 776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b/b2aa2c4efe93e2580d6a8774b04fe2b99756a322/49dc28b4b2e28ef7564e355c91487996c1cbebd7/04bef5f1ba8ea6d7c1c8f5f65e0395c62db59cb8/19964dfb39bda4d7716a71009488f0668ecbcf52/33dc5aac46e0fad8f5eb193e5906ed0eb6b66ceb/d59be579fa932c46b908f37509f319cbd4ca9a68

Timelineinfo

02/26/2025 🔍
02/26/2025 +0 days 🔍
02/26/2025 +0 days 🔍
10/23/2025 +238 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49490 (🔍)
GCVE (CVE): GCVE-0-2022-49490
GCVE (VulDB): GCVE-100-297000

Entryinfo

Created: 02/26/2025 09:40
Updated: 10/23/2025 01:02
Changes: 02/26/2025 09:40 (8), 02/26/2025 09:41 (10), 02/26/2025 09:44 (39), 03/12/2025 17:29 (2), 10/23/2025 01:02 (12)
Complete: 🔍
Committer: sany
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!