mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Eric Dumazet <edumazet@kernel.org>,
	"zdi-disclosures@trendmicro.com" <zdi-disclosures@trendmicro.com>,
	"security@kernel.org" <security@kernel.org>,
	"maintainer:NETWORKING [GENERAL" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	"open list:NETWORKING [GENERAL" <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: ZDI-CAN-33367: New Vulnerability Report
Date: Thu, 22 Oct 2026 18:00:29 +0200	[thread overview]
Message-ID: <atozHXYYSBvz9L_s@1wt.eu> (raw)
In-Reply-To: <willemdebruijn.kernel.178cac71d218b@gmail.com>

On Thu, Oct 22, 2026 at 11:28:49AM -0400, Willem de Bruijn wrote:
> Eric Dumazet wrote:
> > Le mer. 21 oct. 2026 à 23:47, zdi-disclosures@trendmicro.com
> > <zdi-disclosures@trendmicro.com> a écrit :
> > >
> > > ZDI-CAN-33367: Linux Kernel skbuff skb_zerocopy Improper Ownership Management Local Privilege Escalation Vulnerability
> > >
> > > -- CVSS -----------------------------------------
> > >
> > > 7.8: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
> > >
> > > -- ABSTRACT -------------------------------------
> > >
> > > Trend Micro's Zero Day Initiative has identified a vulnerability affecting the following products:
> > > Linux - Kernel
> > >
> > > -- VULNERABILITY DETAILS ------------------------
> > > * Version Tested:7.3-rc1
> > > * Platform Tested:debian trixie
> > >
> > 
> > I had to cut this report. Way too long, I could not see a patch in it.
> 
> Right. For future reports: please review the documentation on how to
> share such findings:
> 
> https://docs.kernel.org/process/security-bugs.html

Rest assured that we've been asking for this many times. The situation
has improved a bit, now we no longer receive the report in a password
protected Zip file and maintainers are finally in Cc. But it looks like
having a direct communication channel with the initial reporter to be
able to discuss and test a patch remains way too far stretched for now.

Despite their sincere efforts, I personally think that the ZDI reports
remain by far the worst we're seeing in terms of efficiency, and among
those which generate the most round trips.

Fortunately most reports these days likely come from AI tools so they
also come in parallel from other channels where communication is
direct. Maybe one day this will further improve, I don't know.

Willy

  reply	other threads:[~2026-10-22 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 21:46 zdi-disclosures
2026-10-22  4:28 ` Eric Dumazet
2026-10-22 15:28   ` Willem de Bruijn
2026-10-22 16:00     ` Willy Tarreau [this message]
2026-10-22 16:02     ` Peter Zijlstra
2026-10-22 18:51       ` zdi-disclosures

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=atozHXYYSBvz9L_s@1wt.eu \
    --to=w@1wt.eu \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=security@kernel.org \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=zdi-disclosures@trendmicro.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

all inboxes | Powered by JetHome®