public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation•org>
To: Wade Sparks <wsparks@vulncheck•com>
Cc: Andrew Lunn <andrew@lunn•ch>,
	netdev@vger•kernel.org, security@kernel•org,
	Disclosures <disclosure@vulncheck•com>
Subject: Re: Unidentified Fragnesia Variant with Public PoC
Date: Thu, 28 May 2026 21:22:52 +0200	[thread overview]
Message-ID: <2026052803-repulsive-outlying-b566@gregkh> (raw)
In-Reply-To: <CAA1v+SiTtZA74PONT8vsipoze7ZpdxncRO3vMNjRWy=jsRoDKA@mail.gmail.com>

On Thu, May 28, 2026 at 12:25:44PM -0400, Wade Sparks wrote:
> Hello Andrew,
> 
> Thanks for your response.
> 
> The proof of concept for this finding is already public and was *not*
> published by VulnCheck but by an entity referred to as V12 Security.
> Additionally, we were able to reproduce the issue ourselves and can confirm
> that the exploit is valid (albeit on a downstream kernel).
> 
> While our team works to reproduce the issue against the latest version of
> the upstream kernel, we wanted to share our findings with the kernel.org
> security team. Apologies for adding in the wrong maintainer distro - we
> will redirect accordingly.

Please read:
	https://docs.kernel.org/process/security-bugs.html
for what the security@kernel•org alias is for.

thanks,

greg k-h

  parent reply	other threads:[~2026-05-28 19:23 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
     [not found]   ` <CAA1v+SiTtZA74PONT8vsipoze7ZpdxncRO3vMNjRWy=jsRoDKA@mail.gmail.com>
2026-05-28 19:22     ` Greg KH [this message]
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=2026052803-repulsive-outlying-b566@gregkh \
    --to=gregkh@linuxfoundation$(echo .)org \
    --cc=andrew@lunn$(echo .)ch \
    --cc=disclosure@vulncheck$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=security@kernel$(echo .)org \
    --cc=wsparks@vulncheck$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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