CVE-2023-53149

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-09-15. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

ext4: avoid deadlock in fs reclaim with page writeback

Ext4 has a filesystem wide lock protecting ext4_writepages() calls to avoid races with switching of journalled data flag or inode format. This lock can however cause a deadlock like:

CPU0 CPU1

ext4_writepages() percpu_down_read(sbi->s_writepages_rwsem); ext4_change_inode_journal_flag() percpu_down_write(sbi->s_writepages_rwsem);

  • blocks, all readers block from now on
ext4_do_writepages() ext4_init_io_end() kmem_cache_zalloc(io_end_cachep, GFP_KERNEL) fs_reclaim frees dentry... dentry_unlink_inode() iput() - last ref => iput_final() - inode dirty => write_inode_now()... ext4_writepages() tries to acquire sbi->s_writepages_rwsem and blocks forever

Make sure we cannot recurse into filesystem reclaim from writeback code to avoid the deadlock.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
—
EPSS
1.5%
KEV
Not listed

Published

September 15, 2025

Last Modified

November 25, 2025

References (3)

Vendor Advisories for CVE-2023-53149(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
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× 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-07-22 23:16 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-18 10:03 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-16 17:01 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-15 01:59 UTCEPSS rescore
  12. 2026-07-15 01:59 UTCEPSS rescore
  13. 2026-07-13 22:28 UTCEPSS rescore
  14. 2026-07-13 22:28 UTCEPSS rescore
  15. 2026-07-09 19:08 UTCEPSS rescore
  16. 2026-07-08 15:13 UTCEPSS rescore
  17. 2026-07-07 13:45 UTCEPSS rescore
  18. 2026-07-07 13:44 UTCEPSS rescore
  19. 2026-07-06 14:41 UTCOSV refresh
  20. 2026-07-05 02:29 UTCEPSS rescore
  21. 2026-07-04 06:29 UTCEPSS rescore
  22. 2026-07-01 15:05 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-29 14:05 UTCEPSS rescore
Show 52 more
  1. 2026-06-28 14:06 UTCEPSS rescore
  2. 2026-06-28 14:06 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-27 03:07 UTCEPSS rescore
  5. 2026-06-25 13:48 UTCEPSS rescore
  6. 2026-06-25 13:48 UTCEPSS rescore
  7. 2026-06-24 14:04 UTCEPSS rescore
  8. 2026-06-24 14:04 UTCEPSS rescore
  9. 2026-06-23 21:31 UTCEPSS rescore
  10. 2026-06-23 21:31 UTCEPSS rescore
  11. 2026-06-22 14:24 UTCEPSS rescore
  12. 2026-06-22 14:24 UTCEPSS rescore
  13. 2026-06-21 14:55 UTCEPSS rescore
  14. 2026-06-21 14:55 UTCEPSS rescore
  15. 2026-06-19 19:24 UTCEPSS rescore
  16. 2026-06-19 19:24 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-18 03:05 UTCOSV refresh
  19. 2026-06-17 17:51 UTCEPSS rescore
  20. 2026-06-16 17:51 UTCEPSS rescore
  21. 2026-06-16 17:51 UTCEPSS rescore
  22. 2026-06-15 17:47 UTCEPSS rescore
  23. 2026-06-14 23:16 UTCEPSS rescore
  24. 2026-06-13 22:59 UTCEPSS rescore
  25. 2026-06-13 22:59 UTCEPSS rescore
  26. 2026-06-12 23:11 UTCEPSS rescore
  27. 2026-06-11 13:59 UTCEPSS rescore
  28. 2026-06-10 22:17 UTCEPSS rescore
  29. 2026-06-10 13:21 UTCEPSS rescore
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-07 15:24 UTCEPSS rescore
  34. 2026-06-06 13:46 UTCEPSS rescore
  35. 2026-06-06 13:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 06:09 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-02 20:12 UTCEPSS rescore
  43. 2026-06-02 20:12 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 00:15 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-29 22:55 UTCEG score recompute
  50. 2026-05-29 22:55 UTCVendor advisory
  51. 2026-05-29 22:55 UTCGHSA enrichment
  52. 2026-05-29 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-53149?
CVE-2023-53149 is a medium vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: avoid deadlock in fs reclaim with page writeback Ext4 has a filesystem wide lock protecting ext4_writepages() calls to avoid races with switching of journalled data flag or inode format. This lock can however cause a deadlock…
When was CVE-2023-53149 disclosed?
CVE-2023-53149 was first published in the National Vulnerability Database on September 15, 2025, with the most recent update on November 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-53149 actively exploited?
CVE-2023-53149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-53149?
CVE-2023-53149 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53149, 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

Explore the affected products and dependency analysis for CVE-2023-53149

Explore →

Is Your Infrastructure Affected by CVE-2023-53149?

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

Start Free Scan →Browse All CVEs