Kernel availability loss via uninitialized inode quota
Published Sep 16, 2025 · Updated Sep 16, 2025
Use of an uninitialized resource in Linux ext4 before 6.2 allows local users to trigger a kernel warning through a file rename. In ext4_rename, the old inode is marked dirty before its quota state is initialized, so extra_isize expansion can allocate a block against uninitialized quota state. A local user must be able to rename a file on an ext4 filesystem; the resulting filesystem warning can impair kernel availability.
Summary
What happened
Use of an uninitialized resource in Linux ext4 before 6.2 allows local users to trigger a kernel warning through a file rename. In ext4_rename, the old inode is marked dirty before its quota state is initialized, so extra_isize expansion can allocate a block against uninitialized quota state. A local user must be able to rename a file on an ext4 filesystem; the resulting filesystem warning can impair kernel availability.
The record
- CVE
- CVE-2022-50346
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <13271fbbe85d73a7c47058f56a52f2a7f00d6e39
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <135ba9146f4d38abed48a540ef8a8770ff0bd34f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <33fd7031d634f3b46e59f61adfbb0ea9fe514fef
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <67f6d5a4043f3db0c6bb0e14a0d97a7be8bfb8b5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7dfb8259f66faafa68d23a261b284d2c2c67649b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <84a2f2ed49d6a4d92b354219077434c57d334620
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <def7a39091e60e1c4a2f623629082a00092602be
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f263e349bacc2f303526dcfa61c4bc50132418b1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fae381a3d79bb94aa2eb752170d47458d778b797
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo