[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025100646-strategy-spindle-ae8a@gregkh>
Date: Mon, 6 Oct 2025 10:14:23 +0200
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Siddh Raman Pant <siddh.raman.pant@...cle.com>
Cc: "cve@...nel.org" <cve@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: CVE-2025-39751: ALSA: hda/ca0132: Fix buffer overflow in
add_tuning_control
On Mon, Oct 06, 2025 at 07:07:00AM +0000, Siddh Raman Pant wrote:
> On Thu, 11 Sep 2025 18:52:52 +0200, Greg Kroah-Hartman wrote:
> > ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control
> >
> > The 'sprintf' call in 'add_tuning_control' may exceed the 44-byte
> > buffer if either string argument is too long. This triggers a compiler
> > warning.
> > Replaced 'sprintf' with 'snprintf' to limit string lengths to prevent
> > overflow.
> >
> > The Linux kernel CVE team has assigned CVE-2025-39751 to this issue.
>
> While the change is good for defensive reasons, there isn't actually
> any buffer overflow as it is to "fix".
>
> The largest string possible is "Wedge Angle Playback Volume", whose
> length is less than 44.
Thanks for the info. What was the compiler warning about then if it
could detect just how big the string would always be as these are static
values?
Should this CVE be rejected?
thanks,
greg k-h
Powered by blists - more mailing lists