CVE-2026-74373

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

md/raid1,raid10: fix bio accounting for split md cloned bios

Use md_cloned_bio() to control bio accounting instead of relying on r1bio_existed in raid1 or the io_accounting flag in raid10.

The previous logic does not reliably reflect whether a bio is an md cloned bio. When a failed bio is split and resubmitted via bio_submit_split_bioset() on the error path, this can lead to either double accounting for md cloned bios, or missing accounting for bios returned from bio_submit_split_bioset()

Fix this by using md_cloned_bio() to detect md cloned bios and skip accounting accordingly.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

References (2)

Vendor Advisories for CVE-2026-74373(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 03:28 UTCVendor advisory
  3. 2026-10-04 03:28 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 20:59 UTCEG score recompute
  7. 2026-09-30 20:59 UTCVendor advisory
  8. 2026-09-30 20:59 UTCGHSA enrichment
  9. 2026-09-29 15:24 UTCEPSS rescore
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-27 08:27 UTCVendor advisory
  13. 2026-09-27 08:27 UTCGHSA enrichment
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-26 00:28 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-22 08:06 UTCGHSA enrichment
  19. 2026-09-21 21:09 UTCEPSS rescore
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-19 01:47 UTCGHSA enrichment
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:15 UTCEPSS rescore
  25. 2026-09-15 19:20 UTCGHSA enrichment
Show 43 more
  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-12 12:12 UTCGHSA enrichment
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-09 05:56 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-06 13:48 UTCEPSS rescore
  9. 2026-09-05 23:39 UTCGHSA enrichment
  10. 2026-09-04 05:07 UTCEPSS rescore
  11. 2026-09-02 17:23 UTCGHSA enrichment
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-08-30 19:18 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 07:37 UTCGHSA enrichment
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-27 01:20 UTCGHSA enrichment
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-24 14:18 UTCEPSS rescore
  24. 2026-08-23 19:03 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-21 23:49 UTCEPSS rescore
  27. 2026-08-20 22:56 UTCEPSS rescore
  28. 2026-08-20 12:47 UTCGHSA enrichment
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-18 13:49 UTCEPSS rescore
  31. 2026-08-18 13:49 UTCEPSS rescore
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-17 06:26 UTCGHSA enrichment
  34. 2026-08-17 06:22 UTCNVD update
  35. 2026-08-17 05:26 UTCEG score recompute
  36. 2026-08-17 05:26 UTCGHSA enrichment
  37. 2026-08-17 05:24 UTCMITRE cvelistV5
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 02:15 UTCEPSS rescore
  41. 2026-08-15 06:23 UTCNVD update
  42. 2026-08-15 06:14 UTCEG score recompute
  43. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74373?
CVE-2026-74373 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: md/raid1,raid10: fix bio accounting for split md cloned bios Use mdclonedbio() to control bio accounting instead of relying on r1bioexisted in raid1 or the ioaccounting flag in raid10. The previous logic does not reliably reflect…
When was CVE-2026-74373 disclosed?
CVE-2026-74373 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74373 actively exploited?
CVE-2026-74373 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74373?
No fix for CVE-2026-74373 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-74373 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74373

Explore →

Is Your Infrastructure Affected by CVE-2026-74373?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs