[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110832-CVE-2024-50180-40c4@gregkh>
Date: Fri, 8 Nov 2024 06:38:33 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50180: fbdev: sisfb: Fix strbuf array overflow
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fbdev: sisfb: Fix strbuf array overflow
The values of the variables xres and yres are placed in strbuf.
These variables are obtained from strbuf1.
The strbuf1 array contains digit characters
and a space if the array contains non-digit characters.
Then, when executing sprintf(strbuf, "%ux%ux8", xres, yres);
more than 16 bytes will be written to strbuf.
It is suggested to increase the size of the strbuf array to 24.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
The Linux kernel CVE team has assigned CVE-2024-50180 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.227 with commit 252f147b1826
Fixed in 5.15.168 with commit 41cf6f26abe4
Fixed in 6.1.113 with commit 889304120ecb
Fixed in 6.6.57 with commit 688872c4ea4a
Fixed in 6.11.4 with commit 11c0d49093b8
Fixed in 6.12-rc1 with commit 9cf14f5a2746
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-2024-50180
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:
drivers/video/fbdev/sis/sis_main.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/252f147b1826cbb30ae0304cf86b66d3bb12b743
https://git.kernel.org/stable/c/41cf6f26abe4f491b694c54bd1aa2530369b7510
https://git.kernel.org/stable/c/889304120ecb2ca30674d89cd4ef15990b6a571c
https://git.kernel.org/stable/c/688872c4ea4a528cd6a057d545c83506b533ee1f
https://git.kernel.org/stable/c/11c0d49093b82f6c547fd419c41a982d26bdf5ef
https://git.kernel.org/stable/c/9cf14f5a2746c19455ce9cb44341b5527b5e19c3
Powered by blists - more mailing lists