mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: Alexey Khoroshilov <khoroshilov@ispras.ru>
Cc: linux-kernel@vger.kernel.org, linux-cve-announce@vger.kernel.org,
	"Карпов Юра" <ykarpov@ispras.ru>
Subject: Re: CVE-2026-43503: net: skbuff: preserve shared-frag marker during coalescing
Date: Mon, 1 Jun 2026 16:38:24 +0200	[thread overview]
Message-ID: <2026060140-unison-failing-781e@gregkh> (raw)
In-Reply-To: <da89996a-49b6-2677-3880-0700102ae605@ispras.ru>

On Mon, Jun 01, 2026 at 01:08:34PM +0300, Alexey Khoroshilov wrote:
> On 23.05.2026 14:44, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <gregkh@kernel.org>
> > 
> > Description
> > ===========
> > 
> > In the Linux kernel, the following vulnerability has been resolved:
> > 
> > net: skbuff: preserve shared-frag marker during coalescing
> 
> CVE with this title is published at
> https://www.cve.org/CVERecord/?id=CVE-2026-46300
> 
> > 
> > Unaffected versions might change over time as fixes are backported to
> > older supported kernel versions.  The official CVE entry at
> > 	https://cve.org/CVERecord/?id=CVE-2026-43503
> > will be updated if fixes are backported, please check that for the most
> > up to date information about this issue.
> 
> By the link at CVE-2026-43503 we see
> 
> Updated: 2026-05-30
> Published: 2026-05-23
> 
> Title: net: skbuff: propagate shared-frag marker through frag-transfer
> helpers
> 
> 
> Looks like a bit of a mix-up. What is a correct mapping?

The correct mapping should be what is on cve.org.  If it is incorrect,
please let us know.  See the cve.org git repo for the changes that were
made here, or the vulns.git repo for the explaination of what happened
if you want more details.

thanks,

greg k-h

      reply	other threads:[~2026-06-01 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026052309-CVE-2026-43503-b134@gregkh>
2026-06-01 10:08 ` Alexey Khoroshilov
2026-06-01 14:38   ` Greg Kroah-Hartman [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=2026060140-unison-failing-781e@gregkh \
    --to=gregkh@kernel.org \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ykarpov@ispras.ru \
    /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®