[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061846-CVE-2022-50051-57ac@gregkh>
Date: Wed, 18 Jun 2025 13:01:56 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50051: ASoC: SOF: debug: Fix potential buffer overflow by snprintf()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: debug: Fix potential buffer overflow by snprintf()
snprintf() returns the would-be-filled size when the string overflows
the given buffer size, hence using this value may result in the buffer
overflow (although it's unrealistic).
This patch replaces with a safer version, scnprintf() for papering
over such a potential issue.
The Linux kernel CVE team has assigned CVE-2022-50051 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 5b10b62989219aa527ee4fa555d1995a3b70981b and fixed in 5.15.63 with commit b318b9dd2ac67f39d0338ce563879d1f59a0347a
Issue introduced in 5.11 with commit 5b10b62989219aa527ee4fa555d1995a3b70981b and fixed in 5.19.4 with commit a67971a17604ae7de278fb09243432459afc51e1
Issue introduced in 5.11 with commit 5b10b62989219aa527ee4fa555d1995a3b70981b and fixed in 6.0 with commit 1eb123ce985e6cf302ac6e3f19862d132d86fa8f
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-50051
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:
sound/soc/sof/debug.c
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/b318b9dd2ac67f39d0338ce563879d1f59a0347a
https://git.kernel.org/stable/c/a67971a17604ae7de278fb09243432459afc51e1
https://git.kernel.org/stable/c/1eb123ce985e6cf302ac6e3f19862d132d86fa8f
Powered by blists - more mailing lists