From: Artem Dinaburg <artem@trailofbits.com>
To: stable@vger.kernel.org
Cc: axboe@kernel.dk, kbusch@kernel.org, kch@nvidia.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 6.6.y 0/2] CVE-2026-64017: backport fix series
Date: Fri, 16 Oct 2026 14:47:51 -0400 [thread overview]
Message-ID: <20261016184753.27189-1-artem@trailofbits.com> (raw)
Hi,
Please consider this backport series for CVE-2026-64017 to 6.6.y.
Apply the patches in this order:
1. blk-mq: pop cached request if it is usable (fix)
2. blk-mq: reinsert cached request to the list (correction)
Patch 1 removes a compatible request from the older cached_rq list before
preparation and QoS throttling, then initializes it after preparation. A
plug flush can therefore no longer reuse the request while submission is
in progress.
Patch 2 returns that request to the single cached_rq list with
rq_list_add() on each of the target's three preparation or merge exits,
replacing upstream's shared-exit handling.
The complete fix is already present in 6.12.y, 6.18.y and 7.2.y.
Build-tested as part of a cumulative 6.6.y series on x86_64
(allmodconfig, CONFIG_WERROR=y).
This backport is considerably more involved than usual.
We performed runtime testing to check validity and stability,
but would still greatly apprciate another set of eyes on it.
It was runtime-tested on v6.6.158 in a QEMU/KVM guest (KASAN, lockdep,
hung-task detection) against an unpatched baseline: blktests block
group and fio on null_blk (none, mq-deadline, bfq), virtio-blk and
ext4. No new blktests failures and no kernel warnings on the patched
kernel; no small sequential write throughput drop over 5%.
An LLM assisted with preparing these backports.
Thanks,
Artem Dinaburg
next reply other threads:[~2026-10-16 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 18:47 Artem Dinaburg [this message]
2026-10-16 18:47 ` [PATCH 6.6.y 1/2] blk-mq: pop cached request if it is usable Artem Dinaburg
2026-10-16 18:47 ` [PATCH 6.6.y 2/2] blk-mq: reinsert cached request to the list Artem Dinaburg
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=20261016184753.27189-1-artem@trailofbits.com \
--to=artem@trailofbits.com \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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