From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49405: staging: r8188eu: prevent ->Ssid overflow in rtw_wx_set_scan()
Date: Wed, 26 Feb 2025 03:11:19 +0100 [thread overview]
Message-ID: <2025022651-CVE-2022-49405-7627@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
staging: r8188eu: prevent ->Ssid overflow in rtw_wx_set_scan()
This code has a check to prevent read overflow but it needs another
check to prevent writing beyond the end of the ->Ssid[] array.
The Linux kernel CVE team has assigned CVE-2022-49405 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 2b42bd58b32155a1be4dd78991845dec05aaef9e and fixed in 5.15.46 with commit ac2eab7de458f5e1210ce1237afab40a307075c8
Issue introduced in 5.15 with commit 2b42bd58b32155a1be4dd78991845dec05aaef9e and fixed in 5.17.14 with commit c4bd6b72df4f01aa866ceb298466d6d07a6bd525
Issue introduced in 5.15 with commit 2b42bd58b32155a1be4dd78991845dec05aaef9e and fixed in 5.18.3 with commit 476bfda0be0f9669add92bff604ca78226cf53d1
Issue introduced in 5.15 with commit 2b42bd58b32155a1be4dd78991845dec05aaef9e and fixed in 5.19 with commit bc10916e890948d8927a5c8c40fb5dc44be5e1b8
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-49405
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/staging/r8188eu/os_dep/ioctl_linux.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/ac2eab7de458f5e1210ce1237afab40a307075c8
https://git.kernel.org/stable/c/c4bd6b72df4f01aa866ceb298466d6d07a6bd525
https://git.kernel.org/stable/c/476bfda0be0f9669add92bff604ca78226cf53d1
https://git.kernel.org/stable/c/bc10916e890948d8927a5c8c40fb5dc44be5e1b8
reply other threads:[~2025-02-26 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022651-CVE-2022-49405-7627@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.