From: Jakub Kicinski <kuba@kernel.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Lorenzo Colitti <lorenzo@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Pietro Borrello <borrello@diag.uniroma1.it>,
netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] tun/tap: set sk_uid from current_fsuid()
Date: Thu, 3 Aug 2023 09:43:43 -0700 [thread overview]
Message-ID: <20230803094343.698b3c34@kernel.org> (raw)
In-Reply-To: <20230731164237.48365-1-lersek@redhat.com>
On Mon, 31 Jul 2023 18:42:35 +0200 Laszlo Ersek wrote:
> The original patches fixing CVE-2023-1076 are incorrect in my opinion.
> This small series fixes them up; see the individual commit messages for
> explanation.
>
> I have a very elaborate test procedure demonstrating the problem for
> both tun and tap; it involves libvirt, qemu, and "crash". I can share
> that procedure if necessary, but it's indeed quite long (I wrote it
> originally for our QE team).
>
> The patches in this series are supposed to "re-fix" CVE-2023-1076; given
> that said CVE is classified as Low Impact (CVSSv3=5.5), I'm posting this
> publicly, and not suggesting any embargo. Red Hat Product Security may
> assign a new CVE number later.
>
> I've tested the patches on top of v6.5-rc4, with "crash" built at commit
> c74f375e0ef7.
FTR this was applied yesterday to net. Thanks!
prev parent reply other threads:[~2023-08-03 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 16:42 [PATCH 0/2] tun/tap: set sk_uid from current_fsuid() Laszlo Ersek
2023-07-31 16:42 ` [PATCH 1/2] net: tun_chr_open(): " Laszlo Ersek
2023-07-31 16:42 ` [PATCH 2/2] net: tap_open(): " Laszlo Ersek
2023-08-03 16:43 ` Jakub Kicinski [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=20230803094343.698b3c34@kernel.org \
--to=kuba@kernel.org \
--cc=borrello@diag.uniroma1.it \
--cc=edumazet@google.com \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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).