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

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?

--
Alexey

       reply	other threads:[~2026-06-01 10:08 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 [this message]
2026-06-01 14:38   ` Greg Kroah-Hartman

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=da89996a-49b6-2677-3880-0700102ae605@ispras.ru \
    --to=khoroshilov@ispras.ru \
    --cc=gregkh@kernel.org \
    --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®