The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Linus Torvalds <torvalds@linuxfoundation.org>, yuri08 <nvt031@gmail.com>
Cc: linux-kernel@vger.kernel.org, security@kernel.org, davem@davemloft.net
Subject: Re: [SECURITY] Bypass of Page Cache Protection in IPsec ESP TX Path via Incorrect skb_cow_data() Semantic
Date: Sun, 10 May 2026 18:48:43 +0200	[thread overview]
Message-ID: <agC262QXRmlGBTnm@1wt.eu> (raw)
In-Reply-To: <CAHk-=wgRij4Uuskue+SsuUBjFe5HrKnwJnjhviU7GbO7EMO+=w@mail.gmail.com>

On Sun, May 10, 2026 at 09:18:12AM -0700, Linus Torvalds wrote:
> On Sun, 10 May 2026 at 08:22, yuri08 <nvt031@gmail.com> wrote:
> >
> > In net/core/skbuff.c (Function __skb_cow_data): The core issue lies here:
> 
> Is this all just AI hallucination? There is no such function with
> double underscores, and the other "quoted" code seems to also be of
> the kind "almost, but not actually match reality".

Pretty disturbing indeed! It looks like a context with too strong
quantization where "tailbits" became "tailroom" and some other parts
were poorly remmebered when dumped.

@yuri08 please revisit entirely your report to fix it or trash it if
not valid. Please don't send unvalidated crap out of AI tools, it's
just wasting precious maintainers' time that would be better spent
doing something useful.

Please also recheck everything you may have previously shared, and
retract your claims if you spot anything dubious. I'm seeing at least
one patch about UAF on algif_aead shared with maintainers and LKML,
that we don't know anymore if we should trust it or not.

thanks,
Willy

      reply	other threads:[~2026-05-10 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFpG_BGdfzTwd3szJX5999LK+sDE35A49dLauRC4hYbZkDAJqw@mail.gmail.com>
2026-05-10 16:18 ` [SECURITY] Bypass of Page Cache Protection in IPsec ESP TX Path via Incorrect skb_cow_data() Semantic Linus Torvalds
2026-05-10 16:48   ` Willy Tarreau [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=agC262QXRmlGBTnm@1wt.eu \
    --to=w@1wt.eu \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvt031@gmail.com \
    --cc=security@kernel.org \
    --cc=torvalds@linuxfoundation.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