CVE-2023-54153

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

ext4: turn quotas off if mount failed after enabling quotas

Yi found during a review of the patch "ext4: don't BUG on inconsistent journal feature" that when ext4_mark_recovery_complete() returns an error value, the error handling path does not turn off the enabled quotas, which triggers the following kmemleak:

================================================================ unreferenced object 0xffff8cf68678e7c0 (size 64): comm "mount", pid 746, jiffies 4294871231 (age 11.540s) hex dump (first 32 bytes): 00 90 ef 82 f6 8c ff ff 00 00 00 00 41 01 00 00 ............A... c7 00 00 00 bd 00 00 00 0a 00 00 00 48 00 00 00 ............H... backtrace: [<00000000c561ef24>] __kmem_cache_alloc_node+0x4d4/0x880 [<00000000d4e621d7>] kmalloc_trace+0x39/0x140 [<00000000837eee74>] v2_read_file_info+0x18a/0x3a0 [<0000000088f6c877>] dquot_load_quota_sb+0x2ed/0x770 [<00000000340a4782>] dquot_load_quota_inode+0xc6/0x1c0 [<0000000089a18bd5>] ext4_enable_quotas+0x17e/0x3a0 [ext4] [<000000003a0268fa>] __ext4_fill_super+0x3448/0x3910 [ext4] [<00000000b0f2a8a8>] ext4_fill_super+0x13d/0x340 [ext4] [<000000004a9489c4>] get_tree_bdev+0x1dc/0x370 [<000000006e723bf1>] ext4_get_tree+0x1d/0x30 [ext4] [<00000000c7cb663d>] vfs_get_tree+0x31/0x160 [<00000000320e1bed>] do_new_mount+0x1d5/0x480 [<00000000c074654c>] path_mount+0x22e/0xbe0 [<0000000003e97a8e>] do_mount+0x95/0xc0 [<000000002f3d3736>] __x64_sys_mount+0xc4/0x160 [<0000000027d2140c>] do_syscall_64+0x3f/0x90 ================================================================

To solve this problem, we add a "failed_mount10" tag, and call ext4_quota_off_umount() in this tag to release the enabled qoutas.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

ext4: turn quotas off if mount failed after enabling quotas - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/deef86fa3005cbb61ae8aa5729324c09b3f4ba73
generic

ext4: turn quotas off if mount failed after enabling quotas - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d13f99632748462c32fc95d729f5e754bab06064
generic

ext4: turn quotas off if mount failed after enabling quotas - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c327b83c59ee938792a0300df646efac39c7d6a7
generic

ext4: turn quotas off if mount failed after enabling quotas - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/77c3ca1108eb4a26db4f256c42b271a430cebc7d

Vendor Advisories for CVE-2023-54153(4)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatrhel9/flatpak-sdk:el9-9040020240312160503.17302525132024-11-07redhat
redhatkernel-0:5.14.0-427.42.1.el9_42024-10-30redhat
linuxKernel @ 5.15.121—osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)6.1.52-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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.

Showing the most recent 100 of 191 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-14 05:49 UTCOSV refresh
  7. 2026-09-13 16:45 UTCEPSS rescore
  8. 2026-09-12 14:58 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:34 UTCEPSS rescore
  11. 2026-09-08 21:58 UTCEPSS rescore
  12. 2026-09-07 15:59 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-05 15:26 UTCEPSS rescore
  15. 2026-09-04 13:58 UTCEPSS rescore
  16. 2026-09-04 05:04 UTCEPSS rescore
  17. 2026-09-02 14:10 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-09-01 04:36 UTCEPSS rescore
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-26 06:43 UTCOSV refresh
Show 75 more
  1. 2026-08-25 13:47 UTCEPSS rescore
  2. 2026-08-21 23:47 UTCEPSS rescore
  3. 2026-08-20 22:53 UTCEPSS rescore
  4. 2026-08-19 17:02 UTCEPSS rescore
  5. 2026-08-18 13:46 UTCEPSS rescore
  6. 2026-08-16 14:54 UTCEPSS rescore
  7. 2026-08-16 02:12 UTCEPSS rescore
  8. 2026-08-15 01:28 UTCEPSS rescore
  9. 2026-08-13 21:58 UTCEPSS rescore
  10. 2026-08-12 13:49 UTCEPSS rescore
  11. 2026-08-11 13:40 UTCEPSS rescore
  12. 2026-08-10 23:58 UTCEPSS rescore
  13. 2026-08-09 22:46 UTCEG score recompute
  14. 2026-08-09 22:46 UTCVendor advisory
  15. 2026-08-09 22:46 UTCGHSA enrichment
  16. 2026-08-09 13:44 UTCEPSS rescore
  17. 2026-08-08 16:35 UTCEPSS rescore
  18. 2026-08-08 05:25 UTCEG score recompute
  19. 2026-08-08 05:25 UTCVendor advisory
  20. 2026-08-08 05:25 UTCGHSA enrichment
  21. 2026-08-07 16:25 UTCEPSS rescore
  22. 2026-08-06 13:45 UTCEPSS rescore
  23. 2026-08-06 07:09 UTCEG score recompute
  24. 2026-08-06 07:09 UTCVendor advisory
  25. 2026-08-06 07:09 UTCGHSA enrichment
  26. 2026-08-05 19:15 UTCEPSS rescore
  27. 2026-08-05 19:15 UTCEPSS rescore
  28. 2026-08-05 10:12 UTCEG score recompute
  29. 2026-08-05 10:12 UTCVendor advisory
  30. 2026-08-05 10:12 UTCGHSA enrichment
  31. 2026-08-04 11:27 UTCEG score recompute
  32. 2026-08-04 11:27 UTCVendor advisory
  33. 2026-08-04 11:27 UTCGHSA enrichment
  34. 2026-08-04 10:36 UTCEPSS rescore
  35. 2026-08-04 10:23 UTCEG score recompute▲ 7.80
  36. 2026-08-04 10:23 UTCVendor advisory
  37. 2026-08-04 10:22 UTCGHSA enrichment
  38. 2026-08-04 10:19 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  39. 2026-08-03 10:34 UTCEPSS rescore
  40. 2026-08-02 02:25 UTCEPSS rescore
  41. 2026-08-02 02:25 UTCEPSS rescore
  42. 2026-08-01 04:14 UTCEPSS rescore
  43. 2026-07-30 16:26 UTCEPSS rescore
  44. 2026-07-30 01:29 UTCEPSS rescore
  45. 2026-07-28 15:34 UTCEPSS rescore
  46. 2026-07-28 15:34 UTCEPSS rescore
  47. 2026-07-27 03:39 UTCOSV refresh
  48. 2026-07-26 14:53 UTCEPSS rescore
  49. 2026-07-25 14:16 UTCEPSS rescore
  50. 2026-07-24 14:16 UTCEPSS rescore
  51. 2026-07-23 14:16 UTCEPSS rescore
  52. 2026-07-23 02:30 UTCEG score recompute
  53. 2026-07-22 23:16 UTCEG score recompute
  54. 2026-07-22 14:07 UTCEPSS rescore
  55. 2026-07-22 14:07 UTCEPSS rescore
  56. 2026-07-21 15:23 UTCEPSS rescore
  57. 2026-07-20 17:06 UTCEPSS rescore
  58. 2026-07-19 02:27 UTCEPSS rescore
  59. 2026-07-19 02:27 UTCEPSS rescore
  60. 2026-07-18 10:03 UTCEPSS rescore
  61. 2026-07-18 10:03 UTCEPSS rescore
  62. 2026-07-16 17:01 UTCEPSS rescore
  63. 2026-07-15 16:56 UTCEPSS rescore
  64. 2026-07-15 01:59 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-13 22:28 UTCEPSS rescore
  67. 2026-07-13 22:28 UTCEPSS rescore
  68. 2026-07-13 06:11 UTCEPSS rescore
  69. 2026-07-12 05:45 UTCEPSS rescore
  70. 2026-07-12 05:45 UTCEPSS rescore
  71. 2026-07-11 08:26 UTCEPSS rescore
  72. 2026-07-09 22:17 UTCOSV refresh
  73. 2026-07-09 19:08 UTCEPSS rescore
  74. 2026-07-08 15:13 UTCEPSS rescore
  75. 2026-07-07 13:45 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2023-54153?
CVE-2023-54153 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: turn quotas off if mount failed after enabling quotas Yi found during a review of the patch "ext4: don't BUG on inconsistent journal feature" that when ext4markrecovery_complete() returns an error value, the error handling…
When was CVE-2023-54153 disclosed?
CVE-2023-54153 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54153 actively exploited?
CVE-2023-54153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2023-54153?
CVE-2023-54153 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54153, 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-54153

Explore →

Is Your Infrastructure Affected by CVE-2023-54153?

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

Start Free Scan →Browse All CVEs