From: Ben Hutchings <benh@debian.org>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Massimiliano Pellizzer <mpellizzer.dev@gmail.com>
Cc: Dominik Grzegorzek <dominik.grzegorzek@oracle.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"lwn@lwn.net" <lwn@lwn.net>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"jslaby@suse.cz" <jslaby@suse.cz>
Subject: Re: Linux 5.15.205
Date: Fri, 08 May 2026 16:38:45 +0200 [thread overview]
Message-ID: <036ef29e143799f9117792463d640916490fa61a.camel@debian.org> (raw)
In-Reply-To: <2026050815-length-yummy-f8b6@gregkh>
[-- Attachment #1: Type: text/plain, Size: 3057 bytes --]
On Fri, 2026-05-08 at 16:30 +0200, gregkh@linuxfoundation.org wrote:
> On Fri, May 08, 2026 at 04:07:31PM +0200, Massimiliano Pellizzer wrote:
> > On Fri, May 8, 2026 at 3:50 PM gregkh@linuxfoundation.org
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Fri, May 08, 2026 at 03:13:51PM +0200, Massimiliano Pellizzer wrote:
> > > > On Fri, May 8, 2026 at 2:44 PM gregkh@linuxfoundation.org
> > > > <gregkh@linuxfoundation.org> wrote:
> > > > >
> > > > > On Fri, May 08, 2026 at 12:05:02PM +0000, Dominik Grzegorzek wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I may be mistaken, but I think there might be a small typo in this hunk in net/ipv4/ip_output.c:
> > > > > >
> > > > > > skb_shinfo(skb)->tx_flags |= SKBFL_SHARED_FRAG;
> > > > > >
> > > > > > Would this need to be:
> > > > > >
> > > > > > skb_shinfo(skb)->flags |= SKBFL_SHARED_FRAG;
> > > > > >
> > > > > > My understanding is that SKBFL_SHARED_FRAG is a bit in skb_shared_info->flags, and skb_has_shared_frag() checks skb_shinfo(skb)->flags.
> > > > >
> > > > > Adding Ben who did the 5.10 backport so he can comment on this.
> > > > >
> > > > > thanks,
> > > > >
> > > > > greg k-h
> > > > >
> > > >
> > > > Hi,
> > > >
> > > > The new released kernel 5.15.205 is still vulnerable to CVE-2026-43284.
> > > >
> > > > ```
> > > > $ ./run.sh
> > > > === Stage 1 — overwrite 'systemd-timesync' line (89 bytes) with
> > > > 'sick::0:0:<pad>:/:/bin/bash'
> > > > === Stage 2 — verify
> > > > sick::0:0:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:/:/bin/bash
> > > > === Stage 3 — su - sick (empty password via PAM nullok)
> > > > [i] state saved to /var/tmp/.cf2.state — run './run.sh --clean' to revert
> > > > # uname -r
> > > > 5.15.205
> > > > ```
> > > >
> > >
> > > Does the patch below fix this up?
> > >
> > > thanks,
> > >
> > > greg k-h
> > >
> > > ------------------
> > >
> > >
> > > diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
> > > index 68509e1f89b5..5d8f8a5901bc 100644
> > > --- a/net/ipv4/ip_output.c
> > > +++ b/net/ipv4/ip_output.c
> > > @@ -1443,7 +1443,7 @@ ssize_t ip_append_page(struct sock *sk, struct flowi4 *fl4, struct page *page,
> > > goto error;
> > > }
> > >
> > > - skb_shinfo(skb)->tx_flags |= SKBFL_SHARED_FRAG;
> > > + skb_shinfo(skb)->flags |= SKBFL_SHARED_FRAG;
> > >
> > > if (skb->ip_summed == CHECKSUM_NONE) {
> > > __wsum csum;
> >
> > Yes, this works.
>
> Wait, is this also needed in the 6.1.y backport as well?
>
> Ben, I'm guessing you tested the 6.1.y backport, right?
Yes, but on 6.1 the PoC never succeeded for me even without the patch.
(On 5.10 and 6.12 it does.) So unfortunately that testing could not
show whether my attempted fix was correct.
Sorry for screwing this one up.
Ben.
--
Ben Hutchings - Debian developer, member of kernel, installer and LTS
teams
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-08 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:50 Linux 5.15.205 Greg Kroah-Hartman
2026-05-08 10:50 ` Greg Kroah-Hartman
2026-05-08 12:05 ` Dominik Grzegorzek
2026-05-08 12:41 ` gregkh
2026-05-08 13:13 ` Massimiliano Pellizzer
2026-05-08 13:50 ` gregkh
2026-05-08 14:07 ` Massimiliano Pellizzer
2026-05-08 14:21 ` gregkh
2026-05-08 14:30 ` gregkh
2026-05-08 14:38 ` Ben Hutchings [this message]
2026-05-08 14:50 ` gregkh
2026-05-08 19:06 ` Ron Economos
2026-05-08 19:33 ` Ben Hutchings
2026-05-08 19:44 ` Woody Suwalski
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=036ef29e143799f9117792463d640916490fa61a.camel@debian.org \
--to=benh@debian.org \
--cc=akpm@linux-foundation.org \
--cc=dominik.grzegorzek@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=mpellizzer.dev@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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