From: Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@gmail.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: kvalo@kernel.org, ath12k@lists.infradead.org,
jjohnson@kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless-next] wifi: ath12k: Fix out-of-bounds read
Date: Sat, 7 Dec 2024 11:40:27 +0530 [thread overview]
Message-ID: <Z1Pm0xsOVbV3rpjc@HOME-PC> (raw)
In-Reply-To: <8c019176-6bb5-467c-bcea-10517675de7d@oss.qualcomm.com>
On Fri, Dec 06, 2024 at 12:06:51PM -0800, Jeff Johnson wrote:
Hi Jeff,
Thank you for taking the time to provide valuable feedback. I will make the
necessary changes and send the patch.
> On 12/5/2024 11:35 PM, Dheeraj Reddy Jonnalagadda wrote:
>
> The subject should be as specific as possible while still fitting on one line.
> Ideally the subject should be unique. So at a minimum I'd add "in
> ath12k_mac_vdev_create()"
>
> > This patch addresses the Out-of-bounds read issue detected by
> > Coverity (CID 1602214). The function ath12k_mac_vdev_create() accesses
> > the vif->link_conf array using link_id, which is derived from
> > arvif->link_id. In cases where arvif->link_id equals 15, the index
>
> How can arvif->link_id equal 15? Does Coverity actually identify a code path
> where this can occur?
In the code below, when the first condition in the if statement is true and
the second condition is false, it implies that arvif->link_id equals 15 and
the else branch is taken, therefore, assigning link_id to 15. The same
code path is shown by coverity. I will attach the link to the coverity report
to the updated patch.
if (arvif->link_id == ATH12K_DEFAULT_SCAN_LINK && vif->valid_links)
link_id = ffs(vif->valid_links) - 1;
else
link_id = arvif->link_id;
>
> > exceeds the bounds of the array, which contains only 15 elements.This
>
> nit: space after .
>
> > results in an out-of-bounds read.
> >
> > This issue occurs in the following branch of the code:
> >
> > if (arvif->link_id == ATH12K_DEFAULT_SCAN_LINK && vif->valid_links)
> > link_id = ffs(vif->valid_links) - 1;
> > else
> > link_id = arvif->link_id;
> >
> > When arvif->link_id equals 15 and the else branch is taken, link_id is
> > set to 15.
> >
> > This patch adds a bounds check to ensure that link_id does not exceed
>
> See
> <https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes>
> and specifically:
> <quote>
> Describe your changes in imperative mood, e.g. “make xyzzy do frotz” instead
> of “[This patch] makes xyzzy do frotz” or “[I] changed xyzzy to do frotz”, as
> if you are giving orders to the codebase to change its behaviour.
> </quote>
>
> So this should start: "Add a bounds check...
>
> > the valid range of the vif->link_conf array. If the check fails, a
> > warning is logged, and the function returns an error code (-EINVAL).
>
> again use imperative mood (log a warning, return an error)
>
> >
>
> Prior to the SOB you should at least have two other tags:
> Fixes: <refer to the patch that introduced the bug>
> Closes: <the public url of the coverity report>
>
> > Signed-off-by: Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@gmail.com>
> > ---
> > drivers/net/wireless/ath/ath12k/mac.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/net/wireless/ath/ath12k/mac.c b/drivers/net/wireless/ath/ath12k/mac.c
> > index 129607ac6c1a..c19b10e66f4a 100644
> > --- a/drivers/net/wireless/ath/ath12k/mac.c
> > +++ b/drivers/net/wireless/ath/ath12k/mac.c
> > @@ -7725,6 +7725,12 @@ int ath12k_mac_vdev_create(struct ath12k *ar, struct ath12k_link_vif *arvif)
> > else
> > link_id = arvif->link_id;
> >
> > + if (link_id >= ARRAY_SIZE(vif->link_conf)) {
> > + ath12k_warn(ar->ab, "link_id %u exceeds max valid links for vif %pM\n",
> > + link_id, vif->addr);
> > + return -EINVAL;
> > + }
> > +
> > link_conf = wiphy_dereference(hw->wiphy, vif->link_conf[link_id]);
> > if (!link_conf) {
> > ath12k_warn(ar->ab, "unable to access bss link conf in vdev create for vif %pM link %u\n",
>
next prev parent reply other threads:[~2024-12-07 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 7:35 [PATCH wireless-next] wifi: ath12k: Fix out-of-bounds read Dheeraj Reddy Jonnalagadda
2024-12-06 20:06 ` Jeff Johnson
2024-12-07 6:10 ` Dheeraj Reddy Jonnalagadda [this message]
2024-12-09 12:39 ` Kalle Valo
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=Z1Pm0xsOVbV3rpjc@HOME-PC \
--to=dheeraj.linuxdev@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).