CVE-2026-45985

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
Trending — 5 sources updated this week
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

A fix is available — apply it.

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

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O

When allocating blocks during within-EOF DIO and writeback with dioread_nolock enabled, EXT4_GET_BLOCKS_PRE_IO was set to split an existing large unwritten extent. However, EXT4_GET_BLOCKS_CONVERT was set when calling ext4_split_convert_extents(), which may potentially result in stale data issues.

Assume we have an unwritten extent, and then DIO writes the second half.

[UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree |<- ->| ----> dio write this range

First, ext4_iomap_alloc() call ext4_map_blocks() with EXT4_GET_BLOCKS_PRE_IO, EXT4_GET_BLOCKS_UNWRIT_EXT and EXT4_GET_BLOCKS_CREATE flags set. ext4_map_blocks() find this extent and call ext4_split_convert_extents() with EXT4_GET_BLOCKS_CONVERT and the above flags set.

Then, ext4_split_convert_extents() calls ext4_split_extent() with EXT4_EXT_MAY_ZEROOUT, EXT4_EXT_MARK_UNWRIT2 and EXT4_EXT_DATA_VALID2 flags set, and it calls ext4_split_extent_at() to split the second half with EXT4_EXT_DATA_VALID2, EXT4_EXT_MARK_UNWRIT1, EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_MARK_UNWRIT2 flags set. However, ext4_split_extent_at() failed to insert extent since a temporary lack -ENOSPC. It zeroes out the first half but convert the entire on-disk extent to written since the EXT4_EXT_DATA_VALID2 flag set, but left the second half as unwritten in the extent status tree.

[0000000000SSSSSS] data S: stale data, 0: zeroed [WWWWWWWWWWWWWWWW] on-disk extent W: written extent [WWWWWWWWWWUUUUUU] extent status tree

Finally, if the DIO failed to write data to the disk, the stale data in the second half will be exposed once the cached extent entry is gone.

Fix this issue by not passing EXT4_GET_BLOCKS_CONVERT when splitting an unwritten extent before submitting I/O, and make ext4_split_convert_extents() to zero out the entire extent range to zero for this case, and also mark the extent in the extent status tree for consistency.

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
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (7)

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

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77e407967cd872cd75d7e4a691908e49c8e6b4d4
generic

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/716e7439a5a9b18c3ff882c2f8c834b9ced1aaec
generic

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67cdb7bd7442bd3cdc6d6088bbb2df9be2fe936c
generic

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37555690f39f78ef69af347d9aff897e07445949
generic

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2920ec61c98b9476781359f05b94da84e80f54d4
generic

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2698731d25823267c29190cb578da9296a0c0d7b

Vendor Advisories for CVE-2026-45985(1)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-14ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-14ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
linuxKernel @ 5.10.253osv

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 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 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.19~rc8-1~exp1 (116 versions)6.19.6-1

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 209 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45985?
CVE-2026-45985 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: don't set EXT4GETBLOCKS_CONVERT when splitting before submitting I/O When allocating blocks during within-EOF DIO and writeback with dioreadnolock enabled, EXT4GETBLOCKSPRE_IO was set to split an existing large unwritten…
When was CVE-2026-45985 disclosed?
CVE-2026-45985 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45985 actively exploited?
CVE-2026-45985 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45985?
CVE-2026-45985 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45985?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45985, 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-45985

Explore →

Is Your Infrastructure Affected by CVE-2026-45985?

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