Linux Kernel up to 5.17.0 open_mutex allocation of resources

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.17.0. It has been rated as problematic. Impacted is the function open_mutex. This manipulation causes allocation of resources. This vulnerability is tracked as CVE-2022-49288. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 5.17.0. Affected by this vulnerability is the function open_mutex. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent prealloc proc writes We have no protection against concurrent PCM buffer preallocation changes via proc files, and it may potentially lead to UAF or some weird problem. This patch applies the PCM open_mutex to the proc write operation for avoiding the racy proc writes and the PCM stream open (and further operations).

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2022-49288 since 02/26/2025. The exploitation appears to be difficult. Technical details are known, but no exploit is available.

Upgrading to version 4.14.279, 4.19.243, 5.4.193, 5.10.109, 5.15.32, 5.16.18 or 5.17.1 eliminates this vulnerability. Applying the patch e7786c445bb67a9a6e64f66ebd6b7215b153ff7d/e14dca613e0a6ddc2bf6e360f16936a9f865205b/37b12c16beb6f6c1c3c678c1aacbc46525c250f7/b560d670c87d7d40b3cf6949246fa4c7aa65a00a/51fce708ab8986a9879ee5da946a2cc120f1036d/a21d2f323b5a978dedf9ff1d50f101f85e39b3f2/5ed8f8e3c4e59d0396b9ccf2e639711e24295bb6/69534c48ba8ce552ce383b3dfdb271ffe51820c3 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.14.278
• 4.19.242
• 5.0
• 5.1
• 5.2
• 5.3
• 5.4
• 5.4.192
• 5.5
• 5.6
• 5.7
• 5.8
• 5.9
• 5.10
• 5.10.108
• 5.11
• 5.12
• 5.13
• 5.14
• 5.15
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.16
• 5.16.0
• 5.16.1
• 5.16.2
• 5.16.3
• 5.16.4
• 5.16.5
• 5.16.6
• 5.16.7
• 5.16.8
• 5.16.9
• 5.16.10
• 5.16.11
• 5.16.12
• 5.16.13
• 5.16.14
• 5.16.15
• 5.16.16
• 5.16.17
• 5.17.0

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion