CVE-2026-45892

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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:

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout

When splitting an unwritten extent in the middle and converting it to initialized in ext4_split_extent() with the EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_DATA_VALID2 flags set, it could leave a stale unwritten extent.

Assume we have an unwritten file and buffered write in the middle of it without dioread_nolock enabled, it will allocate blocks as written extent.

0 A B N [UUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUU] extent status tree [--DDDDDDDD--] D: valid data |<- ->| ----> this range needs to be initialized

ext4_split_extent() first try to split this extent at B with EXT4_EXT_DATA_PARTIAL_VALID1 and EXT4_EXT_MAY_ZEROOUT flag set, but ext4_split_extent_at() failed to split this extent due to temporary lack of space. It zeroout B to N and leave the entire extent as unwritten.

0 A B N [UUUUUUUUUUUU] on-disk extent [UUUUUUUUUUUU] extent status tree [--DDDDDDDDZZ] Z: zeroed data

ext4_split_extent() then try to split this extent at A with EXT4_EXT_DATA_VALID2 flag set. This time, it split successfully and leave an written extent from A to N.

0 A B N [UUWWWWWWWWWW] on-disk extent W: written extent [UUUUUUUUUUUU] extent status tree [--DDDDDDDDZZ]

Finally ext4_map_create_blocks() only insert extent A to B to the extent status tree, and leave an stale unwritten extent in the status tree.

0 A B N [UUWWWWWWWWWW] on-disk extent W: written extent [UUWWWWWWWWUU] extent status tree [--DDDDDDDDZZ]

Fix this issue by always cached extent status entry after zeroing out the second part.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (6)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d882ea3b0931b43530d44149b79fcd4ffc13030
generic

Revert "ext4: don't zero the entire extent if EXT4_EXT_DATA_PARTIAL_VALID1" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28db4bfc6f82fd20e2aadb7fc162244109a4eb31

Vendor Advisories for CVE-2026-45892(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.168—osv

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (100 versions)6.18.14-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 51× 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 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45892?
CVE-2026-45892 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: drop extent cache after doing PARTIAL_VALID1 zeroout When splitting an unwritten extent in the middle and converting it to initialized in ext4splitextent() with the EXT4EXTMAY_ZEROOUT and EXT4EXTDATA_VALID2 flags set, it…
When was CVE-2026-45892 disclosed?
CVE-2026-45892 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45892 actively exploited?
CVE-2026-45892 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 94.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45892?
CVE-2026-45892 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45892, 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-45892

Explore →

Is Your Infrastructure Affected by CVE-2026-45892?

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

Start Free Scan →Browse All CVEs