CVE-2026-64053

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

block: don't overwrite bip_vcnt in bio_integrity_copy_user()

bio_integrity_add_page() already sets bip_vcnt to 1 for the bounce segment. Overwriting it with nr_vecs breaks bip_vcnt <= bip_max_vcnt on WRITE (bip_max_vcnt is 1), so the gap-merge checks in block/blk.h read past the bip_vec[] flex array. On READ the read is in bounds but lands on a saved user bvec instead of the bounce.

The line was added for split propagation, but bio_integrity_clone() doesn't copy bip_vcnt and BIP_CLONE_FLAGS excludes BIP_COPY_USER.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

block: don't overwrite bip_vcnt in bio_integrity_copy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d18160c9525c63c203656fefd847e94b538cd4a4
generic

block: don't overwrite bip_vcnt in bio_integrity_copy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/637ad3a56a3b889527d1dacea6fea2a8bd648140
generic

block: don't overwrite bip_vcnt in bio_integrity_copy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d48654af4d1390c888389206cc13b51b82c30e6
generic

block: don't overwrite bip_vcnt in bio_integrity_copy_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/066be1439593a381b1a29663becfcfe0c92363e7

Vendor Advisories for CVE-2026-64053(1)

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

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 32× in last 7d / 170× 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.

Showing the most recent 100 of 219 total refreshes for this CVE.

  1. 2026-08-30 02:51 UTCEG score recompute
  2. 2026-08-30 02:51 UTCVendor advisory
  3. 2026-08-30 02:50 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 22:39 UTCEG score recompute
  7. 2026-08-27 22:39 UTCVendor advisory
  8. 2026-08-27 22:39 UTCGHSA enrichment
  9. 2026-08-27 11:49 UTCVendor advisory
  10. 2026-08-27 11:49 UTCGHSA enrichment
  11. 2026-08-26 22:18 UTCEG score recompute
  12. 2026-08-26 22:18 UTCVendor advisory
  13. 2026-08-26 22:18 UTCGHSA enrichment
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-26 07:23 UTCVendor advisory
  16. 2026-08-26 07:23 UTCGHSA enrichment
  17. 2026-08-25 20:17 UTCEG score recompute
  18. 2026-08-25 20:17 UTCVendor advisory
  19. 2026-08-25 20:17 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 09:24 UTCVendor advisory
  22. 2026-08-25 09:24 UTCGHSA enrichment
  23. 2026-08-24 22:31 UTCEG score recompute
  24. 2026-08-24 22:31 UTCVendor advisory
  25. 2026-08-24 22:31 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 11:41 UTCEG score recompute
  2. 2026-08-24 11:41 UTCVendor advisory
  3. 2026-08-24 11:41 UTCGHSA enrichment
  4. 2026-08-24 00:51 UTCVendor advisory
  5. 2026-08-24 00:51 UTCGHSA enrichment
  6. 2026-08-23 14:01 UTCVendor advisory
  7. 2026-08-23 14:01 UTCGHSA enrichment
  8. 2026-08-23 03:12 UTCEG score recompute
  9. 2026-08-23 03:12 UTCVendor advisory
  10. 2026-08-23 03:12 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 16:14 UTCVendor advisory
  13. 2026-08-22 16:14 UTCGHSA enrichment
  14. 2026-08-22 05:15 UTCEG score recompute
  15. 2026-08-22 05:15 UTCVendor advisory
  16. 2026-08-22 05:15 UTCGHSA enrichment
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 18:25 UTCVendor advisory
  19. 2026-08-21 18:25 UTCGHSA enrichment
  20. 2026-08-21 07:30 UTCEG score recompute
  21. 2026-08-21 07:30 UTCVendor advisory
  22. 2026-08-21 07:30 UTCGHSA enrichment
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 20:40 UTCVendor advisory
  25. 2026-08-20 20:40 UTCGHSA enrichment
  26. 2026-08-20 09:49 UTCVendor advisory
  27. 2026-08-20 09:49 UTCGHSA enrichment
  28. 2026-08-19 22:59 UTCEG score recompute
  29. 2026-08-19 22:59 UTCVendor advisory
  30. 2026-08-19 22:59 UTCGHSA enrichment
  31. 2026-08-19 17:04 UTCEPSS rescore
  32. 2026-08-19 06:50 UTCVendor advisory
  33. 2026-08-19 06:50 UTCGHSA enrichment
  34. 2026-08-18 19:47 UTCEG score recompute
  35. 2026-08-18 19:47 UTCVendor advisory
  36. 2026-08-18 19:47 UTCGHSA enrichment
  37. 2026-08-18 13:48 UTCEPSS rescore
  38. 2026-08-18 08:00 UTCGHSA enrichment
  39. 2026-08-17 21:08 UTCEG score recompute
  40. 2026-08-17 21:08 UTCVendor advisory
  41. 2026-08-17 21:08 UTCGHSA enrichment
  42. 2026-08-17 13:47 UTCEPSS rescore
  43. 2026-08-17 07:27 UTCVendor advisory
  44. 2026-08-17 07:27 UTCGHSA enrichment
  45. 2026-08-16 20:38 UTCEG score recompute
  46. 2026-08-16 20:38 UTCVendor advisory
  47. 2026-08-16 20:38 UTCGHSA enrichment
  48. 2026-08-16 14:56 UTCEPSS rescore
  49. 2026-08-16 09:47 UTCEG score recompute
  50. 2026-08-16 09:47 UTCGHSA enrichment
  51. 2026-08-15 22:58 UTCVendor advisory
  52. 2026-08-15 22:58 UTCGHSA enrichment
  53. 2026-08-15 12:08 UTCEG score recompute
  54. 2026-08-15 12:08 UTCVendor advisory
  55. 2026-08-15 12:08 UTCGHSA enrichment
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-15 01:18 UTCVendor advisory
  58. 2026-08-15 01:18 UTCGHSA enrichment
  59. 2026-08-14 14:28 UTCVendor advisory
  60. 2026-08-14 14:28 UTCGHSA enrichment
  61. 2026-08-14 03:39 UTCEG score recompute
  62. 2026-08-14 03:39 UTCVendor advisory
  63. 2026-08-14 03:39 UTCGHSA enrichment
  64. 2026-08-13 22:00 UTCEPSS rescore
  65. 2026-08-13 16:49 UTCVendor advisory
  66. 2026-08-13 16:49 UTCGHSA enrichment
  67. 2026-08-13 05:29 UTCVendor advisory
  68. 2026-08-13 05:29 UTCGHSA enrichment
  69. 2026-08-12 18:40 UTCEG score recompute
  70. 2026-08-12 18:40 UTCVendor advisory
  71. 2026-08-12 18:40 UTCGHSA enrichment
  72. 2026-08-12 13:51 UTCEPSS rescore
  73. 2026-08-12 07:50 UTCVendor advisory
  74. 2026-08-12 07:50 UTCGHSA enrichment
  75. 2026-08-11 21:00 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-64053?
CVE-2026-64053 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: block: don't overwrite bipvcnt in biointegritycopyuser() biointegrityaddpage() already sets bipvcnt to 1 for the bounce segment. Overwriting it with nrvecs breaks bipvcnt <= bipmaxvcnt on WRITE (bipmaxvcnt is 1), so the gap-merge…
When was CVE-2026-64053 disclosed?
CVE-2026-64053 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64053 actively exploited?
CVE-2026-64053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64053?
CVE-2026-64053 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64053?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64053, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64053?

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