Linux Kernel up to 5.17.0 hw_params/hw_free buffer overflow

Summaryinfo

A vulnerability labeled as critical has been found in Linux Kernel up to 5.17.0. This affects the function hw_params/hw_free. Executing a manipulation can lead to buffer overflow. This vulnerability is registered as CVE-2022-49291. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 5.17.0 and classified as critical. This vulnerability affects the function hw_params/hw_free. The manipulation with an unknown input leads to a buffer overflow vulnerability. The CWE definition for the vulnerability is CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent hw_params and hw_free calls Currently we have neither proper check nor protection against the concurrent calls of PCM hw_params and hw_free ioctls, which may result in a UAF. Since the existing PCM stream lock can't be used for protecting the whole ioctl operations, we need a new mutex to protect those racy calls. This patch introduced a new mutex, runtime->buffer_mutex, and applies it to both hw_params and hw_free ioctl code paths. Along with it, the both functions are slightly modified (the mmap_count check is moved into the state-check block) for code simplicity.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2022-49291 since 02/26/2025. The exploitation appears to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 02/26/2025).

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 a42aa926843acca96c0dfbde2e835b8137f2f092/9cb6c40a6ebe4a0cfc9d6a181958211682cffea9/fbeb492694ce0441053de57699e1e2b7bc148a69/0f6947f5f5208f6ebd4d76a82a4757e2839a23f8/33061d0fba51d2bf70a2ef9645f703c33fe8e438/0090c13cbbdffd7da079ac56f80373a9a1be0bf8/1bbf82d9f961414d6c76a08f7f843ea068e0ab7b/92ee3c60ec9fe64404dc035e7c41277d74aa26cb 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.

Once again VulDB remains the best source for 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

Once again VulDB remains the best source for vulnerability data.

Discussion