CVE-2023-54153: ext4: turn quotas off if mount failed after enabling quotas
Noroxi assessment
Priority: Monitor (action score 31/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4.15, 4.20, 5.5.
Low priority for now. Upgrade to Linux Linux 4.15, 4.20, 5.5 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: 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.
- Published
- Dec 24, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 60e2824ab30a19c7aaf5a3932bc155d18b2cd816, a6d49257cbe53c7bca1a0353a6443f53cbed9cc7, 2e7312ddaf629eecf4702b662da477a3bc39c31a, d558851e5ff443b020245b7a1a455c55accf740b, 5.9affected
- 11215630aada28307ba555a43138db6ac54fa825 and later · before c327b83c59ee938792a0300df646efac39c7d6a7affected · git
- 11215630aada28307ba555a43138db6ac54fa825 and later · before deef86fa3005cbb61ae8aa5729324c09b3f4ba73affected · git
- 11215630aada28307ba555a43138db6ac54fa825 and later · before 77c3ca1108eb4a26db4f256c42b271a430cebc7daffected · git
- 11215630aada28307ba555a43138db6ac54fa825 and later · before d13f99632748462c32fc95d729f5e754bab06064affected · git
- 4.14.196 and later · before 4.15affected · semver
- 4.19.143 and later · before 4.20affected · semver
- 5.4.62 and later · before 5.5affected · semver
- 5.8.6 and later · before 5.9affected · semver
- before 5.9not 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.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.11-1 | 6.4.11-1 |
| Red Hat:enterprise_linux:9::appstream | bpftool-debuginfo | before 0:7.3.0-427.42.1.el9_4 | 0:7.3.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-devel | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-devel | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-devel | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-devel-matched | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-doc | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
| Red Hat:enterprise_linux:9::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.42.1.el9_4 | 0:5.14.0-427.42.1.el9_4 |
+56
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-54151Dec 24, 2025 · f2fs: Fix system crash due to lack of free space in LFS31Monitor
- ← EarlierCVE-2023-54152Dec 24, 2025 · can: j1939: prevent deadlock by moving j1939_sk_errqueue()0Monitor
- Later →CVE-2023-54154Dec 24, 2025 · scsi: target: core: Fix target_cmd_counter leak0Monitor
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 | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5.9 | Vendor (CNA) |
| Linux Linux | 77c3ca1108eb4a26db4f256c42b271a430cebc7d | Vendor (CNA) |
| Linux Linux | c327b83c59ee938792a0300df646efac39c7d6a7 | Vendor (CNA) |
| Linux Linux | d13f99632748462c32fc95d729f5e754bab06064 | Vendor (CNA) |
| Linux Linux | deef86fa3005cbb61ae8aa5729324c09b3f4ba73 | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.42.1.el9_4 · Red Hat:enterprise_linux:9::appstream | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.