mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Artem Dinaburg <artem@trailofbits.com>
To: stable@vger.kernel.org
Cc: axboe@kernel.dk, cel@kernel.org, hare@kernel.org, hch@lst.de,
	kbusch@kernel.org, linux-kernel@vger.kernel.org,
	linux-nvme@lists.infradead.org, neil@brown.name,
	sagi@grimberg.me
Subject: [PATCH 6.6.y 0/2] CVE-2025-38264: backport fix series
Date: Wed, 14 Oct 2026 15:12:34 -0400	[thread overview]
Message-ID: <20261014191236.23696-1-artem@trailofbits.com> (raw)

Hi,

Please consider this backport series for CVE-2025-38264 to 6.6.y.

Apply the patches in this order:
1. llist: add interface to check if a node is on a list. (prerequisite)
2. nvme-tcp: sanitize request list handling (fix)

Patch 1 adds llist helpers to mark an unused node, test its membership,
and restore the unused state after dequeue.

Patch 2 initializes and resets NVMe/TCP request-list membership and
rejects R2T processing while the request remains queued. The code changes
in both patches are identical to upstream.

The complete fix is already present in 6.12.y, 6.18.y and 7.2.y.

Build-tested only as part of a cumulative 6.6.y series: x86_64 objects
(allmodconfig, CONFIG_WERROR=y); no runtime testing.

An LLM assisted with preparing these backports.

Thanks,
Artem Dinaburg

             reply	other threads:[~2026-10-14 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 19:12 Artem Dinaburg [this message]
2026-10-14 19:12 ` [PATCH 6.6.y 1/2] llist: add interface to check if a node is on a list Artem Dinaburg
2026-10-14 19:12 ` [PATCH 6.6.y 2/2] nvme-tcp: sanitize request list handling Artem Dinaburg
2026-10-15 19:35 ` [PATCH 6.6.y 0/2] CVE-2025-38264: backport fix series Sasha Levin

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=20261014191236.23696-1-artem@trailofbits.com \
    --to=artem@trailofbits.com \
    --cc=axboe@kernel.dk \
    --cc=cel@kernel.org \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=neil@brown.name \
    --cc=sagi@grimberg.me \
    --cc=stable@vger.kernel.org \
    /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®