From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+cc867e537e4bd36f69bb@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] wifi: cfg80211: validate IEs in cfg80211_wext_siwgenie()
Date: Sun, 26 Jul 2026 13:48:22 -0700 [thread overview]
Message-ID: <df56bee8-2347-4909-8859-384a0f87de11@oss.qualcomm.com> (raw)
In-Reply-To: <20260725142028.32560-1-kartikey406@gmail.com>
On 7/25/2026 7:20 AM, Deepanshu Kartikey wrote:
> The KASAN allocation trace shows that a malformed IE buffer is
> stored via SIOCSIWGENIE (cfg80211_wext_siwgenie()) without any
> validation. The crash trace shows that a subsequent SIOCSIWESSID
> triggers a connection attempt which calls cfg80211_sme_get_conn_ies()
> to process the stored IE buffer, causing:
>
> - An out-of-bounds read in skip_ie() which reads ies[pos+1]
> (the length byte) past the end of the 1-byte buffer.
>
> - An integer underflow in the memcpy size argument when offs
> returned by ieee80211_ie_split() exceeds ies_len, causing
> unsigned subtraction to wrap to SIZE_MAX and triggering a
> fortify panic.
>
> Fix this by validating the IE buffer in cfg80211_wext_siwgenie()
> before storing it. First reject buffers smaller than 2 bytes since
> a valid IE requires at least a type and length field. Then use
> for_each_element() and for_each_element_completed() to verify all
> elements are well-formed. Return -EINVAL if validation fails.
>
> Reported-by: syzbot+cc867e537e4bd36f69bb@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=cc867e537e4bd36f69bb
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
>
> ---
> v2: Use for_each_element() and for_each_element_completed() instead
> of open-coded validation loop, as suggested by Johannes Berg.
> Also add explicit ie_len < 2 check to handle the case where
> for_each_element_completed() returns true for a 1-byte buffer.
> ---
> net/wireless/wext-sme.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/net/wireless/wext-sme.c b/net/wireless/wext-sme.c
> index 573b6b15a446..51fc2617a1c3 100644
> --- a/net/wireless/wext-sme.c
> +++ b/net/wireless/wext-sme.c
> @@ -319,6 +319,18 @@ int cfg80211_wext_siwgenie(struct net_device *dev,
> return 0;
>
> if (ie_len) {
> + const struct element *elem;
> +
> + /* IE must have at least Type + Length bytes */
> + if (ie_len < 2)
> + return -EINVAL;
doesn't for_each_element() already handle this?
(const u8 *)(_data) + (_datalen) - (const u8 *)_elem >= \
(int)sizeof(*_elem) && \
> + for_each_element(elem, extra, ie_len) {
> + /* nothing */
> + }
> +
> + if (!for_each_element_completed(elem, extra, ie_len))
> + return -EINVAL;
perhaps this sequence should be refactored into a separate helper that is used
here, and by the existing functions that have the same pattern?
validate_beacon_head()
validate_ie_attr()
> +
> ie = kmemdup(extra, ie_len, GFP_KERNEL);
> if (!ie)
> return -ENOMEM;
next prev parent reply other threads:[~2026-07-26 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 14:20 Deepanshu Kartikey
2026-07-26 20:48 ` Jeff Johnson [this message]
2026-07-29 1:41 ` Deepanshu Kartikey
2026-07-29 6:34 ` Johannes Berg
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=df56bee8-2347-4909-8859-384a0f87de11@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=syzbot+cc867e537e4bd36f69bb@syzkaller.appspotmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®