CVE-2022-49352— ext4: fix warning in ext4_handle_inode_extension
Affected Version Matrix 12
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | b1b4705d54abedfd69dcdf42779c521aa1e0fbd3< adf490083ca52ebfb0b2fe64ff1ead00c0452dd7 | affected |
b1b4705d54abedfd69dcdf42779c521aa1e0fbd3< b81d2ff6885e38fc745eeaf9565775055778fc0b | affected | ||
b1b4705d54abedfd69dcdf42779c521aa1e0fbd3< e383c2aa5f02ab571530dc5c5696479672478c25 | affected | ||
b1b4705d54abedfd69dcdf42779c521aa1e0fbd3< 1bcce88da60eccc946c0f4ed942b0f08cd565778 | affected | ||
b1b4705d54abedfd69dcdf42779c521aa1e0fbd3< f4534c9fc94d22383f187b9409abb3f9df2e3db3 | affected | ||
5.5 | affected | ||
< 5.5 | unaffected | ||
5.10.121≤ 5.10.* | unaffected | ||
| … +4 more rows | |||
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2022-49352
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
ext4: fix warning in ext4_handle_inode_extension
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix warning in ext4_handle_inode_extension We got issue as follows: EXT4-fs error (device loop0) in ext4_reserve_inode_write:5741: Out of memory EXT4-fs error (device loop0): ext4_setattr:5462: inode #13: comm syz-executor.0: mark_inode_dirty error EXT4-fs error (device loop0) in ext4_setattr:5519: Out of memory EXT4-fs error (device loop0): ext4_ind_map_blocks:595: inode #13: comm syz-executor.0: Can't allocate blocks for non-extent mapped inodes with bigalloc ------------[ cut here ]------------ WARNING: CPU: 1 PID: 4361 at fs/ext4/file.c:301 ext4_file_write_iter+0x11c9/0x1220 Modules linked in: CPU: 1 PID: 4361 Comm: syz-executor.0 Not tainted 5.10.0+ #1 RIP: 0010:ext4_file_write_iter+0x11c9/0x1220 RSP: 0018:ffff924d80b27c00 EFLAGS: 00010282 RAX: ffffffff815a3379 RBX: 0000000000000000 RCX: 000000003b000000 RDX: ffff924d81601000 RSI: 00000000000009cc RDI: 00000000000009cd RBP: 000000000000000d R08: ffffffffbc5a2c6b R09: 0000902e0e52a96f R10: ffff902e2b7c1b40 R11: ffff902e2b7c1b40 R12: 000000000000000a R13: 0000000000000001 R14: ffff902e0e52aa10 R15: ffffffffffffff8b FS: 00007f81a7f65700(0000) GS:ffff902e3bc80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffff600400 CR3: 000000012db88001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: do_iter_readv_writev+0x2e5/0x360 do_iter_write+0x112/0x4c0 do_pwritev+0x1e5/0x390 __x64_sys_pwritev2+0x7e/0xa0 do_syscall_64+0x37/0x50 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Above issue may happen as follows: Assume inode.i_size=4096 EXT4_I(inode)->i_disksize=4096 step 1: set inode->i_isize = 8192 ext4_setattr if (attr->ia_size != inode->i_size) EXT4_I(inode)->i_disksize = attr->ia_size; rc = ext4_mark_inode_dirty ext4_reserve_inode_write ext4_get_inode_loc __ext4_get_inode_loc sb_getblk --> return -ENOMEM ... if (!error) ->will not update i_size i_size_write(inode, attr->ia_size); Now: inode.i_size=4096 EXT4_I(inode)->i_disksize=8192 step 2: Direct write 4096 bytes ext4_file_write_iter ext4_dio_write_iter iomap_dio_rw ->return error if (extend) ext4_handle_inode_extension WARN_ON_ONCE(i_size_read(inode) < EXT4_I(inode)->i_disksize); ->Then trigger warning. To solve above issue, if mark inode dirty failed in ext4_setattr just set 'EXT4_I(inode)->i_disksize' with old value.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于ext4_handle_inode_extension未正确处理内存不足，可能导致内核警告。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2022-49352
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2022-49352
请登录查看更多情报信息。
Patches & Fixes for CVE-2022-49352 (6)
Same Patch Batch · Linux · 2025-02-26 · 706 CVEs total
| CVE-2022-49498 | ALSA: pcm: Check for null pointer of pointer substream before dereferencing it | |
| CVE-2022-49486 | ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe | |
| CVE-2022-49488 | drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected | |
| CVE-2022-49489 | drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm run | |
| CVE-2022-49490 | drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected | |
| CVE-2022-49491 | drm/rockchip: vop: fix possible null-ptr-deref in vop_bind() | |
| CVE-2022-49492 | nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags | |
| CVE-2022-49493 | ASoC: rt5645: Fix errorenous cleanup order | |
| CVE-2022-49494 | mtd: rawnand: cadence: fix possible null-ptr-deref in cadence_nand_dt_probe() | |
| CVE-2022-49495 | drm/msm/hdmi: check return value after calling platform_get_resource_byname() | |
| CVE-2022-49497 | net: remove two BUG() from skb_checksum_help() | |
| CVE-2022-49496 | media: mediatek: vcodec: prevent kernel crash when rmmod mtk-vcodec-dec.ko | |
| CVE-2022-49502 | media: rga: fix possible memory leak in rga_probe | |
| CVE-2022-49507 | regulator: da9121: Fix uninit-value in da9121_assign_chip_model() | |
| CVE-2022-49508 | HID: elan: Fix potential double free in elan_input_configured | |
| CVE-2022-49506 | drm/mediatek: Add vblank register/unregister callback functions | |
| CVE-2022-49504 | scsi: lpfc: Inhibit aborts if external loopback plug is inserted | |
| CVE-2022-49505 | NFC: NULL out the dev->rfkill to prevent UAF | |
| CVE-2022-49501 | usbnet: Run unregister_netdev() before unbind() again | |
| CVE-2022-49500 | wl1251: dynamically allocate memory used for DMA |
Showing top 20 of 706 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-45836
Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndti - CVE-2026-45835
Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_conne - CVE-2026-45834
Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_cha - CVE-2026-46300
net: skbuff: preserve shared-frag marker during coalescing - CVE-2026-43503
net: skbuff: propagate shared-frag marker through frag-trans
Same vendor: Linux
- CVE-2026-45836
Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_get_sndti - CVE-2026-45835
Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_new_conne - CVE-2026-45834
Bluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_cha - CVE-2026-46300
net: skbuff: preserve shared-frag marker during coalescing - CVE-2026-43503
net: skbuff: propagate shared-frag marker through frag-trans
V. Comments for CVE-2022-49352
No comments yet