CVE-2026-74307

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:

ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT

Reject the EXT4_IOC_MOVE_EXT ioctl early if the donor file does not belong to the same superblock as the original file. Currently, this validation is performed inside ext4_move_extents() by mext_check_validity(), but only after lock_two_nondirectories() has already acquired the inode locks. When the donor fd refers to a file on a different filesystem (e.g., overlayfs), this late validation creates a circular lock dependency:

CPU0 (overlayfs write) CPU1 (ext4 ioctl) ---- ---- inode_lock(ovl_inode) mnt_want_write_file(filp) sb_start_write(ext4_sb) [sb_writers] backing_file_write_iter() vfs_iter_write(real_file) file_start_write(real_file) sb_start_write(ext4_sb) [blocked by freeze] lock_two_nondirectories() inode_lock(ovl_inode) [blocked]

With a concurrent freeze operation holding sb_writers write side, this forms a deadlock cycle: CPU0 waits for freeze to complete, freeze waits for CPU1's sb_writers reader to exit, CPU1 waits for CPU0's inode lock.

Since EXT4_IOC_MOVE_EXT exchanges physical extents between two files, it fundamentally requires both files to reside on the same ext4 filesystem. Moving the superblock check before any lock acquisition is both semantically correct and eliminates the circular dependency by ensuring that cross-filesystem donor fds are rejected before sb_writers or inode locks are taken.

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
9th
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-74307(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
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 / 35× 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-03 19:32 UTCVendor advisory
  3. 2026-10-03 19:32 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 21:00 UTCEG score recompute
  7. 2026-09-30 21:00 UTCVendor advisory
  8. 2026-09-30 21:00 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:28 UTCVendor advisory
  13. 2026-09-27 08:28 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-23 06:28 UTCGHSA enrichment
  19. 2026-09-21 21:09 UTCEPSS rescore
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 11:07 UTCGHSA enrichment
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-17 15:46 UTCGHSA enrichment
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 44 more
  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-14 20:10 UTCGHSA enrichment
  3. 2026-09-12 15:02 UTCEPSS rescore
  4. 2026-09-11 23:50 UTCGHSA enrichment
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-10 09:35 UTCEPSS rescore
  7. 2026-09-09 03:59 UTCGHSA enrichment
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-06 13:48 UTCEPSS rescore
  10. 2026-09-05 22:13 UTCGHSA enrichment
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-03 02:50 UTCGHSA enrichment
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-31 07:29 UTCGHSA enrichment
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-28 11:59 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 16:37 UTCGHSA enrichment
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 14:18 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
  26. 2026-08-22 21:16 UTCGHSA enrichment
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-20 22:56 UTCEPSS rescore
  29. 2026-08-20 01:49 UTCGHSA enrichment
  30. 2026-08-19 17:04 UTCEPSS rescore
  31. 2026-08-18 13:49 UTCEPSS rescore
  32. 2026-08-18 13:49 UTCEPSS rescore
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 06:27 UTCGHSA enrichment
  35. 2026-08-17 06:22 UTCNVD update
  36. 2026-08-17 05:27 UTCEG score recompute
  37. 2026-08-17 05:27 UTCGHSA enrichment
  38. 2026-08-17 05:24 UTCMITRE cvelistV5
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 14:56 UTCEPSS rescore
  41. 2026-08-16 02:15 UTCEPSS rescore
  42. 2026-08-15 06:23 UTCNVD update
  43. 2026-08-15 06:16 UTCEG score recompute
  44. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74307?
CVE-2026-74307 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: validate donor file superblock early in EXT4IOCMOVE_EXT Reject the EXT4IOCMOVE_EXT ioctl early if the donor file does not belong to the same superblock as the original file. Currently, this validation is performed inside…
When was CVE-2026-74307 disclosed?
CVE-2026-74307 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-74307 actively exploited?
CVE-2026-74307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74307?
No fix for CVE-2026-74307 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-74307 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-74307

Explore →

Is Your Infrastructure Affected by CVE-2026-74307?

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

Book a Demo →Browse All CVEs