From: Nicolas Escande <nico.escande@gmail.com>
To: ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH v2 0/3] fix leaks in some WMI error path
Date: Wed, 6 May 2026 15:42:37 +0200 [thread overview]
Message-ID: <20260506134240.2284016-1-nico.escande@gmail.com> (raw)
So this is similar work to what has been posted here [0] for ath12k.
When we use the pattern 'return ath11k_wmi_cmd_send(...)' without
explicitly checking the return value we fail to free the allocated skb.
This has been split into 2 patches per Jeff's guidance to hopefully
ease the backporting process.
[0] https://lore.kernel.org/linux-wireless/20260422163258.3013872-1-nico.escande@gmail.com/
---
Changes from v1:
- Added patch to also fix ath11k_tm_cmd_wmi_ftm() as per Rameshkumar's remark
Nicolas Escande (3):
wifi: ath11k: fix leak in error path of some WOW related WMI commands
wifi: ath11k: fix error path leaks in some WMI calls
wifi: ath11k: fix error path leak in ath11k_tm_cmd_wmi_ftm()
drivers/net/wireless/ath/ath11k/testmode.c | 1 +
drivers/net/wireless/ath/ath11k/wmi.c | 131 ++++++++++++++++++---
2 files changed, 113 insertions(+), 19 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-06 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 13:42 Nicolas Escande [this message]
2026-05-06 13:42 ` [PATCH v2 1/3] wifi: ath11k: fix error path leaks in some WMI WOW calls Nicolas Escande
2026-05-06 13:42 ` [PATCH v2 2/3] wifi: ath11k: fix error path leaks in some WMI calls Nicolas Escande
2026-05-06 13:42 ` [PATCH v2 3/3] wifi: ath11k: fix error path leak in ath11k_tm_cmd_wmi_ftm() Nicolas Escande
2026-05-06 18:15 ` Rameshkumar Sundaram
2026-05-06 18:16 ` [PATCH v2 0/3] fix leaks in some WMI error path Rameshkumar Sundaram
2026-05-11 4:56 ` Baochen Qiang
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=20260506134240.2284016-1-nico.escande@gmail.com \
--to=nico.escande@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox