From: Paolo Abeni <pabeni@redhat.com>
To: Qasim Ijaz <qasdev00@gmail.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org,
syzbot <syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] net: fix uninitialised access in mii_nway_restart() and cleanup error handling
Date: Tue, 18 Mar 2025 11:29:15 +0100 [thread overview]
Message-ID: <491430dd-71ad-4472-b3e1-0531da6d4ecc@redhat.com> (raw)
In-Reply-To: <20250311161157.49065-1-qasdev00@gmail.com>
On 3/11/25 5:11 PM, Qasim Ijaz wrote:
> In mii_nway_restart() during the line:
>
> bmcr = mii->mdio_read(mii->dev, mii->phy_id, MII_BMCR);
>
> The code attempts to call mii->mdio_read which is ch9200_mdio_read().
>
> ch9200_mdio_read() utilises a local buffer, which is initialised
> with control_read():
>
> unsigned char buff[2];
>
> However buff is conditionally initialised inside control_read():
>
> if (err == size) {
> memcpy(data, buf, size);
> }
>
> If the condition of "err == size" is not met, then buff remains
> uninitialised. Once this happens the uninitialised buff is accessed
> and returned during ch9200_mdio_read():
>
> return (buff[0] | buff[1] << 8);
>
> The problem stems from the fact that ch9200_mdio_read() ignores the
> return value of control_read(), leading to uinit-access of buff.
>
> To fix this we should check the return value of control_read()
> and return early on error.
>
> Furthermore the get_mac_address() function has a similar problem where
> it does not directly check the return value of each control_read(),
> instead it sums up the return values and checks them all at the end
> which means if any call to control_read() fails the function just
> continues on.
>
> Handle this by validating the return value of each call and fail fast
> and early instead of continuing.
>
> Lastly ch9200_bind() ignores the return values of multiple
> control_write() calls.
>
> Validate each control_write() call to ensure it succeeds before
> continuing with the next call.
>
> Reported-by: syzbot <syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com>
> Closes: https://syzkaller.appspot.com/bug?extid=3361c2d6f78a3e0892f9
> Tested-by: syzbot <syzbot+3361c2d6f78a3e0892f9@syzkaller.appspotmail.com>
> Fixes: 4a476bd6d1d9 ("usbnet: New driver for QinHeng CH9200 devices")
> Cc: stable@vger.kernel.org
> Signed-off-by: Qasim Ijaz <qasdev00@gmail.com>
Please split the patch in a small series, as suggested by Simon.
Please additionally include the target tree name ('net', in this case)
in the subj prefix.
Thanks,
Paolo
next prev parent reply other threads:[~2025-03-18 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 16:11 Qasim Ijaz
2025-03-17 17:51 ` Simon Horman
2025-03-18 10:29 ` Paolo Abeni [this message]
2025-03-19 11:40 ` Qasim Ijaz
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=491430dd-71ad-4472-b3e1-0531da6d4ecc@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qasdev00@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+3361c2d6f78a3e0892f9@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®