CVE-2026-74376: Linux kernel · md/raid10: reset read_slot when reusing r10bio for discard
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in 5.15.0-1117.124~20.04.1 : patch Linux kernel as a priority.
Data as of 28 Oct 2026, 00:59 UTC
- Patch
- Available – fixed in 5.15.0-1117.124~20.04.1, 5.15.0-1123.132~20.04.1, 5.15.0-1122.131~20.04.1 +57
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8781-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8876-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8878-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8877-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8875-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8888-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8888-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-74376 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-74376 (opens in a new tab)
- git.kernel.org/linus/6b8a26af065ddc93de2aa5c9f0df98dce9723442 (opens in a new tab)
- git.kernel.org/stable/c/3cb2a606ce4902eceabe68338df0653312f861f8 (opens in a new tab)
- git.kernel.org/stable/c/561c9711e4f545d6464a023168bdee03b00fa945 (opens in a new tab)
- git.kernel.org/stable/c/6b8a26af065ddc93de2aa5c9f0df98dce9723442 (opens in a new tab)
- git.kernel.org/stable/c/742e4afd247d9c972695227716b03d432a7e1d26 (opens in a new tab)
- git.kernel.org/stable/c/b7313f23ea5a79b199a007bfad64a866cc2c22e7 (opens in a new tab)
- git.kernel.org/stable/c/ce3030e92f14362880055de5fe3c258971118853 (opens in a new tab)
- git.kernel.org/stable/c/eb04e3e9c14ed15914f5fd2eae8b6435f54f095f (opens in a new tab)
- ubuntu.com/security/notices/USN-8781-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8816-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8876-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8878-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8877-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8875-1 (opens in a new tab)