CVE-2026-63820

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

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

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

f2fs: fix missing read bio submission on large folio error

f2fs_read_data_large_folio() can keep a read bio across multiple readahead folios. If a later folio hits an error before any of its blocks are added to the bio, folio_in_bio is false and the current error path returns immediately after ending that folio.

This can leave the bio accumulated for earlier folios unsubmitted. Those folios then never receive read completion, and readers can wait indefinitely on the locked folios.

Route errors through the common out path so any pending bio is submitted before returning. Stop consuming more readahead folios once an error is seen, and only wait on and clear the current folio when it was actually added to the bio.

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%
EPSS %ILE
10%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

References (2)

Vendor Advisories for CVE-2026-63820(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (153 versions)7.1.3-1—

Data Freshness Timeline

(refreshed 8× in last 7d / 37× 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-08-30 03:18 UTCGHSA enrichment
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 22:29 UTCGHSA enrichment
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-23 15:01 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 10:12 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 05:25 UTCNVD update
  17. 2026-08-17 05:23 UTCGHSA enrichment
  18. 2026-08-17 05:05 UTCMITRE cvelistV5
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-15 22:50 UTCGHSA enrichment
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 18:00 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 70 more
  1. 2026-08-09 13:47 UTCEPSS rescore
  2. 2026-08-09 13:11 UTCGHSA enrichment
  3. 2026-08-06 13:47 UTCEPSS rescore
  4. 2026-08-06 08:22 UTCGHSA enrichment
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:39 UTCEPSS rescore
  9. 2026-08-03 10:36 UTCEPSS rescore
  10. 2026-08-03 03:33 UTCGHSA enrichment
  11. 2026-08-02 02:27 UTCEPSS rescore
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-30 22:43 UTCEG score recompute
  14. 2026-07-30 22:43 UTCGHSA enrichment
  15. 2026-07-30 16:28 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-30 01:30 UTCEPSS rescore
  18. 2026-07-28 15:37 UTCEPSS rescore
  19. 2026-07-27 17:53 UTCGHSA enrichment
  20. 2026-07-27 14:14 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:54 UTCEPSS rescore
  23. 2026-07-26 11:08 UTCEG score recompute
  24. 2026-07-26 11:08 UTCGHSA enrichment
  25. 2026-07-24 14:18 UTCEPSS rescore
  26. 2026-07-24 14:18 UTCEPSS rescore
  27. 2026-07-23 14:18 UTCEPSS rescore
  28. 2026-07-23 14:18 UTCEPSS rescore
  29. 2026-07-23 03:22 UTCEG score recompute
  30. 2026-07-22 14:08 UTCEPSS rescore
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:25 UTCEPSS rescore
  33. 2026-07-21 15:25 UTCEPSS rescore
  34. 2026-07-20 17:44 UTCEG score recompute
  35. 2026-07-20 17:44 UTCGHSA enrichment
  36. 2026-07-20 17:08 UTCEPSS rescore
  37. 2026-07-19 15:39 UTCGHSA enrichment
  38. 2026-07-19 15:26 UTCGHSA enrichment
  39. 2026-07-19 15:18 UTCGHSA enrichment
  40. 2026-07-19 15:16 UTCGHSA enrichment
  41. 2026-07-19 15:15 UTCGHSA enrichment
  42. 2026-07-19 15:15 UTCGHSA enrichment
  43. 2026-07-19 15:14 UTCGHSA enrichment
  44. 2026-07-19 15:13 UTCGHSA enrichment
  45. 2026-07-19 15:12 UTCGHSA enrichment
  46. 2026-07-19 15:09 UTCGHSA enrichment
  47. 2026-07-19 15:05 UTCGHSA enrichment
  48. 2026-07-19 14:59 UTCGHSA enrichment
  49. 2026-07-19 14:52 UTCGHSA enrichment
  50. 2026-07-19 14:37 UTCGHSA enrichment
  51. 2026-07-19 14:27 UTCGHSA enrichment
  52. 2026-07-19 14:25 UTCGHSA enrichment
  53. 2026-07-19 14:16 UTCGHSA enrichment
  54. 2026-07-19 14:13 UTCGHSA enrichment
  55. 2026-07-19 14:08 UTCGHSA enrichment
  56. 2026-07-19 13:59 UTCGHSA enrichment
  57. 2026-07-19 13:53 UTCGHSA enrichment
  58. 2026-07-19 13:50 UTCGHSA enrichment
  59. 2026-07-19 13:49 UTCGHSA enrichment
  60. 2026-07-19 13:46 UTCGHSA enrichment
  61. 2026-07-19 13:21 UTCGHSA enrichment
  62. 2026-07-19 13:18 UTCGHSA enrichment
  63. 2026-07-19 13:13 UTCGHSA enrichment
  64. 2026-07-19 13:06 UTCGHSA enrichment
  65. 2026-07-19 13:00 UTCGHSA enrichment
  66. 2026-07-19 12:57 UTCGHSA enrichment
  67. 2026-07-19 12:33 UTCGHSA enrichment
  68. 2026-07-19 12:26 UTCNVD update
  69. 2026-07-19 12:13 UTCEG score recompute
  70. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63820?
CVE-2026-63820 is a publicly disclosed vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix missing read bio submission on large folio error f2fsreaddatalargefolio() can keep a read bio across multiple readahead folios. If a later folio hits an error before any of its blocks are added to the bio, folioinbio is…
When was CVE-2026-63820 disclosed?
CVE-2026-63820 was first published in the National Vulnerability Database on July 19, 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-63820 actively exploited?
CVE-2026-63820 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 90.5% of all scored CVEs.
How do I remediate CVE-2026-63820?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63820, 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-63820

Explore →

Is Your Infrastructure Affected by CVE-2026-63820?

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

Start Free Scan →Browse All CVEs