Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-54311ext4: fix deadlock when converting an inline directory in nojournal mode

Description

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < b4fa4768c9acff77245d672d855d2c88294850b1
    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < 5f8b55136ad787aed2c184f7cb3e93772ae637a3
    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < 640c8c365999c6f23447ac766437236ad88317c5
    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < 665cc3ba50330049524c1d275bc840a8f28dde73
    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < 0b1c4357bb21d9770451a1bdb8d419ea10bada88
    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < 804de0c72cd473e186ca4e1f6287d45431b14e5a
    • affected 3c47d54170b6a678875566b1b8d6dcf57904e49b – < f4ce24f54d9cca4f09a395f3eecce20d6bec4663
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.112 – ≤ 5.15.*
    • unaffected 6.1.29 – ≤ 6.1.*
    • unaffected 6.2.16 – ≤ 6.2.*
    • unaffected 6.3.3 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54311 badge
[![CVE-2023-54311](https://cveledger.app/badge/CVE-2023-54311.svg)](https://cveledger.app/cve/CVE-2023-54311)

Record last updated .