From: Lukas Wunner <lukas@wunner.de>
To: Oliver Neukum <oneukum@suse.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jann Horn <jannh@google.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Oleksij Rempel <linux@rempel-privat.de>,
Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>, Jacky Chou <jackychou@asix.com.tw>,
Willy Tarreau <w@1wt.eu>, Lino Sanfilippo <LinoSanfilippo@gmx.de>,
Philipp Rosenberger <p.rosenberger@kunbus.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: [PATCH net-next v2 0/1] linkwatch use-after-free fix
Date: Sun, 12 Jun 2022 11:07:46 +0200 [thread overview]
Message-ID: <cover.1655024266.git.lukas@wunner.de> (raw)
Discussion on v1 of this patch fizzled out in April without it being applied:
https://lore.kernel.org/netdev/18b3541e5372bc9b9fc733d422f4e698c089077c.1650177997.git.lukas@wunner.de/#r
This is a vulnerability, we can't just ignore it. Paolo Abeni asked
me to explore whether the issue can be fixed in USB Ethernet drivers
instead of core networking code. I've done that and presented a patch,
but consider it an inferior approach.
I'm explaining why in the updated commit message of this patch and
I'm rebasing it on net-next. Otherwise it's the same as v1, I still
believe that this is the best solution to the problem.
Thanks!
Lukas Wunner (1):
net: linkwatch: ignore events for unregistered netdevs
net/core/dev.c | 17 -----------------
net/core/dev.h | 1 -
net/core/link_watch.c | 10 ++--------
3 files changed, 2 insertions(+), 26 deletions(-)
--
2.35.2
next reply other threads:[~2022-06-12 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 9:07 Lukas Wunner [this message]
2022-06-12 9:08 ` [PATCH net-next v2 1/1] net: linkwatch: ignore events for unregistered netdevs Lukas Wunner
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=cover.1655024266.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=LinoSanfilippo@gmx.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jackychou@asix.com.tw \
--cc=jannh@google.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=oneukum@suse.com \
--cc=p.rosenberger@kunbus.com \
--cc=pabeni@redhat.com \
--cc=w@1wt.eu \
/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).