CVE-2022-50546: ext4: fix uninititialized value in 'ext4_evict_inode'
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.22% (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 091f85db4c3fb1734a6d7fb4777a2b2831da6631, 3c31d8d3ad95aef8cc17a4fcf317e46217148439, 5.10.164.
Low priority for now. Upgrade to Linux Linux 091f85db4c3fb1734a6d7fb4777a2b2831da6631, 3c31d8d3ad95aef8cc17a4fcf317e46217148439, 5.10.164 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: fix uninititialized value in 'ext4_evict_inode' Syzbot found the following issue: ===================================================== BUG: KMSAN: uninit-value in ext4_evict_inode+0xdd/0x26b0 fs/ext4/inode.c:180 ext4_evict_inode+0xdd/0x26b0 fs/ext4/inode.c:180 evict+0x365/0x9a0 fs/inode.c:664 iput_final fs/inode.c:1747 [inline] iput+0x985/0xdd0 fs/inode.c:1773 __ext4_new_inode+0xe54/0x7ec0 fs/ext4/ialloc.c:1361 ext4_mknod+0x376/0x840 fs/ext4/namei.c:2844 vfs_mknod+0x79d/0x830 fs/namei.c:3914 do_mknodat+0x47d/0xaa0 __do_sys_mknodat fs/namei.c:3992 [inline] __se_sys_mknodat fs/namei.c:3989 [inline] __ia32_sys_mknodat+0xeb/0x150 fs/namei.c:3989 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline] __do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178 do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203 do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:246 entry_SYSENTER_compat_after_hwframe+0x70/0x82 Uninit was created at: __alloc_pages+0x9f1/0xe80 mm/page_alloc.c:5578 alloc_pages+0xaae/0xd80 mm/mempolicy.c:2285 alloc_slab_page mm/slub.c:1794 [inline] allocate_slab+0x1b5/0x1010 mm/slub.c:1939 new_slab mm/slub.c:1992 [inline] ___slab_alloc+0x10c3/0x2d60 mm/slub.c:3180 __slab_alloc mm/slub.c:3279 [inline] slab_alloc_node mm/slub.c:3364 [inline] slab_alloc mm/slub.c:3406 [inline] __kmem_cache_alloc_lru mm/slub.c:3413 [inline] kmem_cache_alloc_lru+0x6f3/0xb30 mm/slub.c:3429 alloc_inode_sb include/linux/fs.h:3117 [inline] ext4_alloc_inode+0x5f/0x860 fs/ext4/super.c:1321 alloc_inode+0x83/0x440 fs/inode.c:259 new_inode_pseudo fs/inode.c:1018 [inline] new_inode+0x3b/0x430 fs/inode.c:1046 __ext4_new_inode+0x2a7/0x7ec0 fs/ext4/ialloc.c:959 ext4_mkdir+0x4d5/0x1560 fs/ext4/namei.c:2992 vfs_mkdir+0x62a/0x870 fs/namei.c:4035 do_mkdirat+0x466/0x7b0 fs/namei.c:4060 __do_sys_mkdirat fs/namei.c:4075 [inline] __se_sys_mkdirat fs/namei.c:4073 [inline] __ia32_sys_mkdirat+0xc4/0x120 fs/namei.c:4073 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline] __do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178 do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203 do_SYSENTER_32+0x1b/0x20 arch/x86/entry/common.c:246 entry_SYSENTER_compat_after_hwframe+0x70/0x82 CPU: 1 PID: 4625 Comm: syz-executor.2 Not tainted 6.1.0-rc4-syzkaller-62821-gcb231e2f67ec #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 ===================================================== Now, 'ext4_alloc_inode()' didn't init 'ei->i_flags'. If new inode failed before set 'ei->i_flags' in '__ext4_new_inode()', then do 'iput()'. As after 6bc0d63dad7f commit will access 'ei->i_flags' in 'ext4_evict_inode()' which will lead to access uninit-value. To solve above issue just init 'ei->i_flags' in 'ext4_alloc_inode()'.
- Published
- Oct 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-908
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.2%
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 kernel5.15.61 and later · before 5.15.87
- linux linux kernel5.18.18 and later · before 5.19
- linux linux kernel5.19.2 and later · before 6.0.18
- linux linux kernel6.1 and later · before 6.1.4
- linux linux kernel5.10.163
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
- 819d16f7feaca0f2ed3409be14fe953127fc51b6, 458aee4a6e5be7ad862ee27dfaf07ce552d84f32, 6.0affected
- bb337d8dd1e1d6b7719872e45e36392f3ab14b4f and later · before f0bffdcc7cb14598af2aa706f1e0f2a9054154baaffected · git
- a5f9bd4beae8553480d02b569d4aabee1b49345d and later · before e431b4fb1fb8c2654b808086e9747a000adb9655affected · git
- 0e6fbc566fcc4c230bf80f76cf5df26b42142d8a and later · before 091f85db4c3fb1734a6d7fb4777a2b2831da6631affected · git
- 0b885394fd009aa0b46d81b496a816ab11309f8a and later · before 3c31d8d3ad95aef8cc17a4fcf317e46217148439affected · git
- 6bc0d63dad7f9f54d381925ee855b402f652fa39 and later · before 56491d60ddca9c697d885394cb0173675b9ab81faffected · git
- 6bc0d63dad7f9f54d381925ee855b402f652fa39 and later · before 9f966e021c20caae639dd0e404c8761e8281a2c4affected · git
- 6bc0d63dad7f9f54d381925ee855b402f652fa39 and later · before 7ea71af94eaaaf6d9aed24bc94a05b977a741cb9affected · git
- 5.10.163 and later · before 5.10.164affected · semver
- 5.15.61 and later · before 5.15.87affected · 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.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-50544Oct 7, 2025 · usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info()22Monitor
- ← EarlierCVE-2022-50545Oct 7, 2025 · r6040: Fix kmemleak in probe and remove22Monitor
- Later →CVE-2022-50547Oct 7, 2025 · media: solo6x10: fix possible memory leak in solo_sysfs_init()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 | 091f85db4c3fb1734a6d7fb4777a2b2831da6631 | Vendor (CNA) |
| Linux Linux | 3c31d8d3ad95aef8cc17a4fcf317e46217148439 | Vendor (CNA) |
| Linux Linux | 5.10.164 | Vendor (CNA) |
| Linux Linux | 5.15.87 | Vendor (CNA) |
| Linux Linux | 5.19 | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 56491d60ddca9c697d885394cb0173675b9ab81f | Vendor (CNA) |
| Linux Linux | 7ea71af94eaaaf6d9aed24bc94a05b977a741cb9 | Vendor (CNA) |
| Linux Linux | 9f966e021c20caae639dd0e404c8761e8281a2c4 | Vendor (CNA) |
| Linux Linux | e431b4fb1fb8c2654b808086e9747a000adb9655 | Vendor (CNA) |
| Linux Linux | f0bffdcc7cb14598af2aa706f1e0f2a9054154ba | 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-50302322 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2026-52989260 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers39Monitor
- CVE-2026-53225261 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()36Monitor
- CVE-2024-47685351 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2026-53170261 days apartaccel/ethosu: reject DMA commands with uninitialized length35Monitor
- CVE-2026-43139211 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
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- 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:H/I:H/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 (6 more)Show less
- git.kernel.org/stable/c/3c31d8d3ad95aef8cc17a4fcf317e46217148439
- git.kernel.org/stable/c/56491d60ddca9c697d885394cb0173675b9ab81f
- git.kernel.org/stable/c/7ea71af94eaaaf6d9aed24bc94a05b977a741cb9
- git.kernel.org/stable/c/9f966e021c20caae639dd0e404c8761e8281a2c4
- git.kernel.org/stable/c/e431b4fb1fb8c2654b808086e9747a000adb9655
- git.kernel.org/stable/c/f0bffdcc7cb14598af2aa706f1e0f2a9054154ba
Vendor advisories and official records. Exploit/PoC links are deliberately left out.