From: Pedro Falcato <pfalcato@suse.de>
To: Takao Sato <takaosato1997@gmail.com>
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com, w@1wt.eu,
davem@davemloft.net, herbert@gondor.apana.org.au,
chopps@chopps.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3] xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()
Date: Mon, 25 May 2026 11:22:32 +0100 [thread overview]
Message-ID: <ahQiuEhVjnes7gUb@pedro-suse> (raw)
In-Reply-To: <20260522142504.1394864-1-takaosato1997@gmail.com>
On Fri, May 22, 2026 at 11:25:04AM -0300, Takao Sato wrote:
> iptfs_consume_frags() transfers paged fragments from one socket buffer
> to another but fails to propagate the SKBFL_SHARED_FRAG flag. This is
> the same class of bug that was fixed in skb_try_coalesce() for
> CVE-2026-46300: when fragments backed by read-only page-cache pages are
> merged, the marker indicating their shared nature must be preserved so
> that ESP can decide correctly whether in-place encryption is safe.
>
> Apply the same two-line fix used in skb_try_coalesce() to
> iptfs_consume_frags().
>
> Fixes: b96ba312e21c ("xfrm: iptfs: share page fragments of inner packets")
> Cc: stable@vger.kernel.org # 6.8+
Why? This code seems to have only been introduced in 6.14, aka the only LTS
version this applies to is 6.18. Typo?
--
Pedro
next prev parent reply other threads:[~2026-05-25 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 14:25 [PATCH net v3] xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags() Takao Sato
2026-05-24 6:19 ` Christian Hopps
2026-05-25 10:22 ` Pedro Falcato [this message]
2026-05-26 0:35 ` [PATCH net v4] " Takao Sato
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=ahQiuEhVjnes7gUb@pedro-suse \
--to=pfalcato@suse.de \
--cc=chopps@chopps.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=takaosato1997@gmail.com \
--cc=w@1wt.eu \
/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