Linux kernel CVE announcements
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74376: md/raid10: reset read_slot when reusing r10bio for discard
Date: Sat, 15 Aug 2026 15:11:43 +0900	[thread overview]
Message-ID: <2026081504-CVE-2026-74376-e253@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

md/raid10: reset read_slot when reusing r10bio for discard

put_all_bios() always drops devs[i].bio, but it only drops
devs[i].repl_bio when r10_bio->read_slot < 0. If discard reuses an
r10bio that was previously used for a read, read_slot can still be
non-negative, and discard cleanup can skip bio_put() on repl_bio.

Reset read_slot to -1 when preparing an r10bio for discard so the
replacement bio is always released correctly.

The Linux kernel CVE team has assigned CVE-2026-74376 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 5.15.212 with commit 3cb2a606ce4902eceabe68338df0653312f861f8
	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 6.1.178 with commit 561c9711e4f545d6464a023168bdee03b00fa945
	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 6.6.145 with commit ce3030e92f14362880055de5fe3c258971118853
	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 6.12.97 with commit 742e4afd247d9c972695227716b03d432a7e1d26
	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 6.18.40 with commit b7313f23ea5a79b199a007bfad64a866cc2c22e7
	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 7.1.5 with commit eb04e3e9c14ed15914f5fd2eae8b6435f54f095f
	Issue introduced in 5.13 with commit d30588b2731fb01e1616cf16c3fe79a1443e29aa and fixed in 7.2-rc1 with commit 6b8a26af065ddc93de2aa5c9f0df98dce9723442

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

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-74376
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/md/raid10.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/3cb2a606ce4902eceabe68338df0653312f861f8
	https://git.kernel.org/stable/c/561c9711e4f545d6464a023168bdee03b00fa945
	https://git.kernel.org/stable/c/ce3030e92f14362880055de5fe3c258971118853
	https://git.kernel.org/stable/c/742e4afd247d9c972695227716b03d432a7e1d26
	https://git.kernel.org/stable/c/b7313f23ea5a79b199a007bfad64a866cc2c22e7
	https://git.kernel.org/stable/c/eb04e3e9c14ed15914f5fd2eae8b6435f54f095f
	https://git.kernel.org/stable/c/6b8a26af065ddc93de2aa5c9f0df98dce9723442

                 reply	other threads:[~2026-08-15  6:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2026081504-CVE-2026-74376-e253@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@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