From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
syzbot+1f53a30781af65d2c955@syzkaller.appspotmail.com,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read
Date: Tue, 10 Oct 2023 09:28:33 +0200 [thread overview]
Message-ID: <2023101025-sulfur-blurred-93ab@gregkh> (raw)
In-Reply-To: <87r0m3c56e.fsf@48ers.dk>
On Tue, Oct 10, 2023 at 09:22:49AM +0200, Peter Korsgaard wrote:
> >>>>> "Greg" == Greg KH <gregkh@linuxfoundation.org> writes:
>
> > On Tue, Oct 10, 2023 at 08:19:48AM +0200, Peter Korsgaard wrote:
> >> >>>>> "Greg" == Greg KH <gregkh@linuxfoundation.org> writes:
> >>
> >> > On Tue, Oct 10, 2023 at 12:26:14AM +0200, Javier Carrasco wrote:
> >> >> syzbot has found an uninit-value bug triggered by the dm9601 driver [1].
> >> >>
> >> >> This error happens because the variable res is not updated if the call
> >> >> to dm_read_shared_word returns an error. In this particular case -EPROTO
> >> >> was returned and res stayed uninitialized.
> >> >>
> >> >> This can be avoided by checking the return value of dm_read_shared_word
> >> >> and propagating the error if the read operation failed.
> >> >>
> >> >> [1] https://syzkaller.appspot.com/bug?extid=1f53a30781af65d2c955
> >> >>
> >> >> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> >> >> Reported-and-tested-by: syzbot+1f53a30781af65d2c955@syzkaller.appspotmail.com
> >> >> ---
> >> >> Changes in v2:
> >> >> - Remove unnecessary 'err == 0' case
> >> >> - Link to v1: https://lore.kernel.org/r/20231009-topic-dm9601_uninit_mdio_read-v1-1-d4d775e24e3b@gmail.com
> >> >> ---
> >> >> drivers/net/usb/dm9601.c | 7 ++++++-
> >> >> 1 file changed, 6 insertions(+), 1 deletion(-)
> >>
> >> > What commit id does this fix?
> >>
> >> It has been there since the beginning, so:
> >>
> >> Fixes: d0374f4f9c35cdfbee0 ("USB: Davicom DM9601 usbnet driver")
> >>
> >> Acked-by: Peter Korsgaard <peter@korsgaard.com>
>
> > Great, can someone add a cc: stable@ tag for this too please?
>
> Cc: stable@vger.kernel.org
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2023-10-10 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231009-topic-dm9601_uninit_mdio_read-v2-1-f2fe39739b6c@gmail.com>
[not found] ` <2023101036-fleshy-dude-aec0@gregkh>
[not found] ` <87v8bfc83f.fsf@48ers.dk>
[not found] ` <2023101018-venomous-uncured-47cf@gregkh>
2023-10-10 7:22 ` [PATCH v2] net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read Peter Korsgaard
2023-10-10 7:28 ` Greg KH [this message]
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=2023101025-sulfur-blurred-93ab@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter@korsgaard.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+1f53a30781af65d2c955@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