CVE-2023-54311: ext4: fix deadlock when converting an inline directory in nojournal mode
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 0b1c4357bb21d9770451a1bdb8d419ea10bada88, 5f8b55136ad787aed2c184f7cb3e93772ae637a3, 640c8c365999c6f23447ac766437236ad88317c5.
Low priority for now. Upgrade to Linux Linux 0b1c4357bb21d9770451a1bdb8d419ea10bada88, 5f8b55136ad787aed2c184f7cb3e93772ae637a3, 640c8c365999c6f23447ac766437236ad88317c5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock when converting an inline directory in nojournal mode In no journal mode, ext4_finish_convert_inline_dir() can self-deadlock by calling ext4_handle_dirty_dirblock() when it already has taken the directory lock. There is a similar self-deadlock in ext4_incvert_inline_data_nolock() for data files which we'll fix at the same time. A simple reproducer demonstrating the problem: mke2fs -Fq -t ext2 -O inline_data -b 4k /dev/vdc 64 mount -t ext4 -o dirsync /dev/vdc /vdc cd /vdc mkdir file0 cd file0 touch file0 touch file1 attr -s BurnSpaceInEA -V abcde . touch supercalifragilisticexpialidocious
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.8affected
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before b4fa4768c9acff77245d672d855d2c88294850b1affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 5f8b55136ad787aed2c184f7cb3e93772ae637a3affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 640c8c365999c6f23447ac766437236ad88317c5affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 665cc3ba50330049524c1d275bc840a8f28dde73affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 0b1c4357bb21d9770451a1bdb8d419ea10bada88affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 804de0c72cd473e186ca4e1f6287d45431b14e5aaffected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before f4ce24f54d9cca4f09a395f3eecce20d6bec4663affected · git
- before 3.8not affected · semver
- 5.4.243 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54309Dec 30, 2025 · tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation0Monitor
- ← EarlierCVE-2023-54310Dec 30, 2025 · scsi: message: mptlan: Fix use after free bug in mptlan_remove() due to race condition31Monitor
- Later →CVE-2023-54312Dec 30, 2025 · samples/bpf: Fix buffer overflow in tcp_basertt0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0b1c4357bb21d9770451a1bdb8d419ea10bada88 | Vendor (CNA) |
| Linux Linux | 5f8b55136ad787aed2c184f7cb3e93772ae637a3 | Vendor (CNA) |
| Linux Linux | 640c8c365999c6f23447ac766437236ad88317c5 | Vendor (CNA) |
| Linux Linux | 665cc3ba50330049524c1d275bc840a8f28dde73 | Vendor (CNA) |
| Linux Linux | 804de0c72cd473e186ca4e1f6287d45431b14e5a | Vendor (CNA) |
| Linux Linux | b4fa4768c9acff77245d672d855d2c88294850b1 | Vendor (CNA) |
| Linux Linux | f4ce24f54d9cca4f09a395f3eecce20d6bec4663 | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/5f8b55136ad787aed2c184f7cb3e93772ae637a3
- git.kernel.org/stable/c/640c8c365999c6f23447ac766437236ad88317c5
- git.kernel.org/stable/c/665cc3ba50330049524c1d275bc840a8f28dde73
- git.kernel.org/stable/c/804de0c72cd473e186ca4e1f6287d45431b14e5a
- git.kernel.org/stable/c/b4fa4768c9acff77245d672d855d2c88294850b1
- git.kernel.org/stable/c/f4ce24f54d9cca4f09a395f3eecce20d6bec4663
Vendor advisories and official records. Exploit/PoC links are deliberately left out.