CVE-2022-50346: ext4: init quota for 'old.inode' in 'ext4_rename'
Noroxi assessment
Priority: Monitor (action score 22/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. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 13271fbbe85d73a7c47058f56a52f2a7f00d6e39, 135ba9146f4d38abed48a540ef8a8770ff0bd34f, 33fd7031d634f3b46e59f61adfbb0ea9fe514fef.
Low priority for now. Upgrade to Linux Linux 13271fbbe85d73a7c47058f56a52f2a7f00d6e39, 135ba9146f4d38abed48a540ef8a8770ff0bd34f, 33fd7031d634f3b46e59f61adfbb0ea9fe514fef 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: init quota for 'old.inode' in 'ext4_rename' Syzbot found the following issue: ext4_parse_param: s_want_extra_isize=128 ext4_inode_info_init: s_want_extra_isize=32 ext4_rename: old.inode=ffff88823869a2c8 old.dir=ffff888238699828 new.inode=ffff88823869d7e8 new.dir=ffff888238699828 __ext4_mark_inode_dirty: inode=ffff888238699828 ea_isize=32 want_ea_size=128 __ext4_mark_inode_dirty: inode=ffff88823869a2c8 ea_isize=32 want_ea_size=128 ext4_xattr_block_set: inode=ffff88823869a2c8 ------------[ cut here ]------------ WARNING: CPU: 13 PID: 2234 at fs/ext4/xattr.c:2070 ext4_xattr_block_set.cold+0x22/0x980 Modules linked in: RIP: 0010:ext4_xattr_block_set.cold+0x22/0x980 RSP: 0018:ffff888227d3f3b0 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffff88823007a000 RCX: 0000000000000000 RDX: 0000000000000a03 RSI: 0000000000000040 RDI: ffff888230078178 RBP: 0000000000000000 R08: 000000000000002c R09: ffffed1075c7df8e R10: ffff8883ae3efc6b R11: ffffed1075c7df8d R12: 0000000000000000 R13: ffff88823869a2c8 R14: ffff8881012e0460 R15: dffffc0000000000 FS: 00007f350ac1f740(0000) GS:ffff8883ae200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f350a6ed6a0 CR3: 0000000237456000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? ext4_xattr_set_entry+0x3b7/0x2320 ? ext4_xattr_block_set+0x0/0x2020 ? ext4_xattr_set_entry+0x0/0x2320 ? ext4_xattr_check_entries+0x77/0x310 ? ext4_xattr_ibody_set+0x23b/0x340 ext4_xattr_move_to_block+0x594/0x720 ext4_expand_extra_isize_ea+0x59a/0x10f0 __ext4_expand_extra_isize+0x278/0x3f0 __ext4_mark_inode_dirty.cold+0x347/0x410 ext4_rename+0xed3/0x174f vfs_rename+0x13a7/0x2510 do_renameat2+0x55d/0x920 __x64_sys_rename+0x7d/0xb0 do_syscall_64+0x3b/0xa0 entry_SYSCALL_64_after_hwframe+0x72/0xdc As 'ext4_rename' will modify 'old.inode' ctime and mark inode dirty, which may trigger expand 'extra_isize' and allocate block. If inode didn't init quota will lead to warning. To solve above issue, init 'old.inode' firstly in 'ext4_rename'.
- Published
- Sep 16, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-908
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.9.337
- linux linux kernel4.10 and later · before 4.14.303
- linux linux kernel4.15 and later · before 4.19.270
- linux linux kernel4.20 and later · before 5.4.229
- linux linux kernel5.5 and later · before 5.10.163
- linux linux kernel5.11 and later · before 5.15.87
- linux linux kernel5.16 and later · before 6.0.18
- linux linux kernel6.1 and later · before 6.1.4
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
- 2.6.23affected
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before 67f6d5a4043f3db0c6bb0e14a0d97a7be8bfb8b5affected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before 33fd7031d634f3b46e59f61adfbb0ea9fe514fefaffected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before 7dfb8259f66faafa68d23a261b284d2c2c67649baffected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before f263e349bacc2f303526dcfa61c4bc50132418b1affected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before 84a2f2ed49d6a4d92b354219077434c57d334620affected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before def7a39091e60e1c4a2f623629082a00092602beaffected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before 135ba9146f4d38abed48a540ef8a8770ff0bd34faffected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before 13271fbbe85d73a7c47058f56a52f2a7f00d6e39affected · git
- 6dd4ee7cab7e3a17c571aebd444f4344c8c4946e and later · before fae381a3d79bb94aa2eb752170d47458d778b797affected · git
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.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50343Sep 16, 2025 · rapidio: fix possible name leaks when rio_add_device() fails22Monitor
- ← EarlierCVE-2022-50344Sep 16, 2025 · ext4: fix null-ptr-deref in ext4_write_info22Monitor
- Later →CVE-2022-50347Sep 16, 2025 · mmc: rtsx_usb_sdmmc: fix return value check of mmc_add_host()22Monitor
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 | 13271fbbe85d73a7c47058f56a52f2a7f00d6e39 | Vendor (CNA) |
| Linux Linux | 135ba9146f4d38abed48a540ef8a8770ff0bd34f | Vendor (CNA) |
| Linux Linux | 33fd7031d634f3b46e59f61adfbb0ea9fe514fef | Vendor (CNA) |
| Linux Linux | 67f6d5a4043f3db0c6bb0e14a0d97a7be8bfb8b5 | Vendor (CNA) |
| Linux Linux | 7dfb8259f66faafa68d23a261b284d2c2c67649b | Vendor (CNA) |
| Linux Linux | 84a2f2ed49d6a4d92b354219077434c57d334620 | Vendor (CNA) |
| Linux Linux | def7a39091e60e1c4a2f623629082a00092602be | Vendor (CNA) |
| Linux Linux | f263e349bacc2f303526dcfa61c4bc50132418b1 | Vendor (CNA) |
| Linux Linux | fae381a3d79bb94aa2eb752170d47458d778b797 | Vendor (CNA) |
| debian:linux | 6.1.4-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.
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.
- CVE-2024-50302301 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2026-52989281 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers39Monitor
- CVE-2026-53225282 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()36Monitor
- CVE-2024-47685330 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2026-53170282 days apartaccel/ethosu: reject DMA commands with uninitialized length35Monitor
- CVE-2026-43139232 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()34Monitor
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.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-908 · Use of Uninitialized ResourceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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 (8 more)Show less
- git.kernel.org/stable/c/135ba9146f4d38abed48a540ef8a8770ff0bd34f
- git.kernel.org/stable/c/33fd7031d634f3b46e59f61adfbb0ea9fe514fef
- git.kernel.org/stable/c/67f6d5a4043f3db0c6bb0e14a0d97a7be8bfb8b5
- git.kernel.org/stable/c/7dfb8259f66faafa68d23a261b284d2c2c67649b
- git.kernel.org/stable/c/84a2f2ed49d6a4d92b354219077434c57d334620
- git.kernel.org/stable/c/def7a39091e60e1c4a2f623629082a00092602be
- git.kernel.org/stable/c/f263e349bacc2f303526dcfa61c4bc50132418b1
- git.kernel.org/stable/c/fae381a3d79bb94aa2eb752170d47458d778b797
Vendor advisories and official records. Exploit/PoC links are deliberately left out.