CVE-2023-53149

MEDIUMNVD 5.55.5—Trending — 4 sources updated this week

5.5

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)
EPSS: 3.8%
KEV: Not listed

Published

September 15, 2025

Last Modified

November 25, 2025

References (3)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/00d873c17e29cc32d90ca852b82685f1673acaa5
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2ec97dc90df40c50e509809dc9a198638a7e18b6
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/4b4340bf04ce9a52061f15000ecedd126abc093c

Vendor Advisories for CVE-2023-53149(1)

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

CVE-2023-53149
Microsoft Security Response Center (MSRC)Medium
ext4: avoid deadlock in fs reclaim with page writeback

Patch Availability(1)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
redhat	kernel-0:5.14.0-427.13.1.el9_4	2024-04-30	redhat

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.

CWE-667

All Vendor Advisories

(1)

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.

Red HatRHSA-2024:2394MODERATE2025-09-15
RHSA-2024:2394 — Moderate

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 22:55 UTCEG score recompute
2026-05-29 22:55 UTCVendor advisory
2026-05-29 22:55 UTCGHSA enrichment
2026-05-29 13:43 UTCepss_batch

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 3.8% 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

See which npm, PyPI, Go, and Maven packages are affected by 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

CVE-2023-53149

Published

Last Modified

References (3)

Vendor Advisories for CVE-2023-53149(1)

Patch Availability(1)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2023-53149?

Same vendor

Same CWE

CVE-2023-53149

📅 Published

🔄 Last Modified

🔗 References (3)

📣 Vendor Advisories for CVE-2023-53149(1)

Patch Availability(1)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2023-53149?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (3)

Vendor Advisories for CVE-2023-53149(1)

Frequently asked(5)

Related CVEs(same vendor + same CWE)