[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110939-CVE-2024-50259-b07b@gregkh>
Date: Sat, 9 Nov 2024 11:16:07 +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-50259: netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write()
This was found by a static analyzer.
We should not forget the trailing zero after copy_from_user()
if we will further do some string operations, sscanf() in this
case. Adding a trailing zero will ensure that the function
performs properly.
The Linux kernel CVE team has assigned CVE-2024-50259 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit c6385c0b67c5 and fixed in 5.15.171 with commit c2150f666c6f
Issue introduced in 5.13 with commit c6385c0b67c5 and fixed in 6.1.116 with commit bcba86e03b3a
Issue introduced in 5.13 with commit c6385c0b67c5 and fixed in 6.6.60 with commit 6a604877160f
Issue introduced in 5.13 with commit c6385c0b67c5 and fixed in 6.11.7 with commit 27bd7a742e17
Issue introduced in 5.13 with commit c6385c0b67c5 and fixed in 6.12-rc6 with commit 4ce1f56a1eac
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-50259
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/net/netdevsim/fib.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/c2150f666c6fc301d5d1643ed0f92251f1a0ff0d
https://git.kernel.org/stable/c/bcba86e03b3aac361ea671672cf48eed11f9011c
https://git.kernel.org/stable/c/6a604877160fe5ab2e1985d5ce1ba6a61abe0693
https://git.kernel.org/stable/c/27bd7a742e171362c9eb52ad5d1d71d3321f949f
https://git.kernel.org/stable/c/4ce1f56a1eaced2523329bef800d004e30f2f76c
Powered by blists - more mailing lists