All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tristan Madani <tristmd@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Kalle Valo <kvalo@kernel.org>, Po-Hao Huang <phhuang@realtek.com>,
	Chin-Yen Lee <timlee@realtek.com>,
	linux-wireless@vger.kernel.org, stable@vger.kernel.org,
	Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH wireless v2 0/2] wifi: rtw89: fix IE length passed to cfg80211_find_ie()
Date: Wed,  7 Oct 2026 16:17:19 +0000	[thread overview]
Message-ID: <20261007161721.261452-1-tristmd@gmail.com> (raw)

From: Tristan Madani <tristan@talencesecurity.com>

Two callers of cfg80211_find_ie() in rtw89 pass skb->len as the IE
data length, but since ies points past the management frame header
and fixed fields, the correct length is skb->len minus the header
offset. This causes cfg80211_find_ie() to potentially read past the
IE data boundary.

Changes since v1:
  - Straightened the cfg80211_find_ie() call in wow.c to a single line
  - Removed unnecessary blank line in wow.c
  Both per Ping-Ke Shih review feedback.

Tristan Madani (2):
  wifi: rtw89: fix IE length passed to cfg80211_find_ie() in 6 GHz probe
  wifi: rtw89: fix IE length passed to cfg80211_find_ie() in WoW AKM

 drivers/net/wireless/realtek/rtw89/core.c | 6 +++++-
 drivers/net/wireless/realtek/rtw89/wow.c  | 6 +++++-
 2 files changed, 10 insertions(+), 2 deletions(-)

--
2.47.3

             reply	other threads:[~2026-10-07 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 16:17 Tristan Madani [this message]
2026-10-07 16:17 ` [PATCH wireless v2 1/2] wifi: rtw89: fix IE length passed to cfg80211_find_ie() in 6 GHz probe Tristan Madani
2026-10-08  0:47   ` Ping-Ke Shih
2026-10-07 16:17 ` [PATCH wireless v2 2/2] wifi: rtw89: fix IE length passed to cfg80211_find_ie() in WoW AKM Tristan Madani
2026-10-08  1:20   ` Ping-Ke Shih
2026-10-08  5:31   ` Ping-Ke Shih

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=20261007161721.261452-1-tristmd@gmail.com \
    --to=tristmd@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@realtek.com \
    --cc=pkshih@realtek.com \
    --cc=stable@vger.kernel.org \
    --cc=timlee@realtek.com \
    --cc=tristan@talencesecurity.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 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.