Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Wade Sparks <wsparks@vulncheck.com>
Cc: netdev@vger.kernel.org, security@kernel.org,
	Disclosures <disclosure@vulncheck.com>
Subject: Re: Unidentified Fragnesia Variant with Public PoC
Date: Thu, 28 May 2026 18:16:53 +0200	[thread overview]
Message-ID: <73b5b45c-08df-47db-b749-b4b7cd625b3f@lunn.ch> (raw)
In-Reply-To: <CAA1v+Sj=THjpUA6m0wX26DVQWMe8=YMZ5HwMo8K8ArjZopCKxg@mail.gmail.com>

On Thu, May 28, 2026 at 11:12:32AM -0400, Wade Sparks wrote:
> Hello netdev team,
> (cc: security@kernel.org)

security@kernel.org is for embargoed reports. You posted this
publicly, so it cannot be embargoed. Please don't waste the time of
the people on security@kernel.org.

> The original Fragnesia patch only addressed the coalesce path, leaving the
> segmentation path independently exploitable. We confirmed the PoC works on the
> latest Ubuntu kernel release as of 2026-05-27 (we are in the process of
> re-testing against v7.0.10 of the kernel.org release). The variant is distinct
> enough to warrant its own patch, as it operates in a different function with a
> different trigger path that survives the existing fix.
> 
> If there is an existing patch that apparently has not made it's way to Ubuntu
> distributions, we'd greatly appreciate if you could flag so that we may
> initiate the CVE assignment process with kernel.org CNA.

netdev does not really care about downstream kernels. Please report
any networking issues against Mainline, ideally net or net-next.

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html

   Andrew

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 15:12 Unidentified Fragnesia Variant with Public PoC Wade Sparks
2026-05-28 16:16 ` Andrew Lunn [this message]
     [not found]   ` <CAA1v+SiTtZA74PONT8vsipoze7ZpdxncRO3vMNjRWy=jsRoDKA@mail.gmail.com>
2026-05-28 19:22     ` Greg KH
2026-05-29  6:37 ` Jiayuan Chen

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=73b5b45c-08df-47db-b749-b4b7cd625b3f@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=disclosure@vulncheck.com \
    --cc=netdev@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=wsparks@vulncheck.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