Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2022-49170— f2fs: fix to do sanity check on curseg->alloc_type

EPSS 0.11% · P30

Affected Version Matrix 12

VendorProductVersion RangeStatus
LinuxLinux98e4da8ca301e062d79ae168c67e56f3c3de3ce4< 498b7088db71f9707359448cd6800bbb1882f4c3affected
98e4da8ca301e062d79ae168c67e56f3c3de3ce4< f68caedf264a95c0b02dfd0d9f92ac2637d5848aaffected
98e4da8ca301e062d79ae168c67e56f3c3de3ce4< 0748a0f7dcb9d9dddc80302d73ebcecef6782ef0affected
98e4da8ca301e062d79ae168c67e56f3c3de3ce4< c12765e3f129b144421c80d3383df885f85ee290affected
98e4da8ca301e062d79ae168c67e56f3c3de3ce4< f41ee8b91c00770d718be2ff4852a80017ae9ab3affected
3.8affected
< 3.8unaffected
5.10.110≤ 5.10.*unaffected
… +4 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2022-49170

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
f2fs: fix to do sanity check on curseg->alloc_type
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on curseg->alloc_type As Wenqing Liu reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215657 - Overview UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2 when mount and operate a corrupted image - Reproduce tested on kernel 5.17-rc4, 5.17-rc6 1. mkdir test_crash 2. cd test_crash 3. unzip tmp2.zip 4. mkdir mnt 5. ./single_test.sh f2fs 2 - Kernel dump [ 46.434454] loop0: detected capacity change from 0 to 131072 [ 46.529839] F2FS-fs (loop0): Mounted with checkpoint version = 7548c2d9 [ 46.738319] ================================================================================ [ 46.738412] UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2 [ 46.738475] index 231 is out of range for type 'unsigned int [2]' [ 46.738539] CPU: 2 PID: 939 Comm: umount Not tainted 5.17.0-rc6 #1 [ 46.738547] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 46.738551] Call Trace: [ 46.738556] <TASK> [ 46.738563] dump_stack_lvl+0x47/0x5c [ 46.738581] ubsan_epilogue+0x5/0x50 [ 46.738592] __ubsan_handle_out_of_bounds+0x68/0x80 [ 46.738604] f2fs_allocate_data_block+0xdff/0xe60 [f2fs] [ 46.738819] do_write_page+0xef/0x210 [f2fs] [ 46.738934] f2fs_do_write_node_page+0x3f/0x80 [f2fs] [ 46.739038] __write_node_page+0x2b7/0x920 [f2fs] [ 46.739162] f2fs_sync_node_pages+0x943/0xb00 [f2fs] [ 46.739293] f2fs_write_checkpoint+0x7bb/0x1030 [f2fs] [ 46.739405] kill_f2fs_super+0x125/0x150 [f2fs] [ 46.739507] deactivate_locked_super+0x60/0xc0 [ 46.739517] deactivate_super+0x70/0xb0 [ 46.739524] cleanup_mnt+0x11a/0x200 [ 46.739532] __cleanup_mnt+0x16/0x20 [ 46.739538] task_work_run+0x67/0xa0 [ 46.739547] exit_to_user_mode_prepare+0x18c/0x1a0 [ 46.739559] syscall_exit_to_user_mode+0x26/0x40 [ 46.739568] do_syscall_64+0x46/0xb0 [ 46.739584] entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is we missed to do sanity check on curseg->alloc_type, result in out-of-bound accessing on sbi->block_count[] array, fix it.
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存在安全漏洞,该漏洞源于f2fs驱动在curseg->alloc_type上未进行完整性检查,可能导致数组越界。
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

VendorProductAffected VersionsCPESubscribe
LinuxLinux 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 ~ 498b7088db71f9707359448cd6800bbb1882f4c3 -
LinuxLinux 3.8 -

II. Public POCs for CVE-2022-49170

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-49170

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-02-26 · 706 CVEs total

CVE-2022-49498ALSA: pcm: Check for null pointer of pointer substream before dereferencing it
CVE-2022-49486ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe
CVE-2022-49488drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected
CVE-2022-49489drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm run
CVE-2022-49490drm/msm/mdp5: Return error code in mdp5_pipe_release when deadlock is detected
CVE-2022-49491drm/rockchip: vop: fix possible null-ptr-deref in vop_bind()
CVE-2022-49492nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags
CVE-2022-49493ASoC: rt5645: Fix errorenous cleanup order
CVE-2022-49494mtd: rawnand: cadence: fix possible null-ptr-deref in cadence_nand_dt_probe()
CVE-2022-49495drm/msm/hdmi: check return value after calling platform_get_resource_byname()
CVE-2022-49497net: remove two BUG() from skb_checksum_help()
CVE-2022-49496media: mediatek: vcodec: prevent kernel crash when rmmod mtk-vcodec-dec.ko
CVE-2022-49502media: rga: fix possible memory leak in rga_probe
CVE-2022-49507regulator: da9121: Fix uninit-value in da9121_assign_chip_model()
CVE-2022-49508HID: elan: Fix potential double free in elan_input_configured
CVE-2022-49506drm/mediatek: Add vblank register/unregister callback functions
CVE-2022-49504scsi: lpfc: Inhibit aborts if external loopback plug is inserted
CVE-2022-49505NFC: NULL out the dev->rfkill to prevent UAF
CVE-2022-49501usbnet: Run unregister_netdev() before unbind() again
CVE-2022-49500wl1251: dynamically allocate memory used for DMA

Showing top 20 of 706 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2022-49170

No comments yet


Leave a comment