CVE-2024-56565— f2fs: fix to drop all discards after creating snapshot on lvm device
Affected Version Matrix 8
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 35ec7d5748849762008e8ae9f8ad2766229d5794< ed24ab98242f8d22b66fbe0452c97751b5ea4e22 | affected |
35ec7d5748849762008e8ae9f8ad2766229d5794< 15136c3861a3341db261ebdbb6ae4ae1765635e2 | affected | ||
35ec7d5748849762008e8ae9f8ad2766229d5794< bc8aeb04fd80cb8cfae3058445c84410fd0beb5e | affected | ||
4.19 | affected | ||
< 4.19 | unaffected | ||
6.6.66≤ 6.6.* | unaffected | ||
6.12.4≤ 6.12.* | unaffected | ||
6.13≤ * | unaffected |
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2024-56565
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 drop all discards after creating snapshot on lvm device
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to drop all discards after creating snapshot on lvm device Piergiorgio reported a bug in bugzilla as below: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 969 at fs/f2fs/segment.c:1330 RIP: 0010:__submit_discard_cmd+0x27d/0x400 [f2fs] Call Trace: __issue_discard_cmd+0x1ca/0x350 [f2fs] issue_discard_thread+0x191/0x480 [f2fs] kthread+0xcf/0x100 ret_from_fork+0x31/0x50 ret_from_fork_asm+0x1a/0x30 w/ below testcase, it can reproduce this bug quickly: - pvcreate /dev/vdb - vgcreate myvg1 /dev/vdb - lvcreate -L 1024m -n mylv1 myvg1 - mount /dev/myvg1/mylv1 /mnt/f2fs - dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=20 - sync - rm /mnt/f2fs/file - sync - lvcreate -L 1024m -s -n mylv1-snapshot /dev/myvg1/mylv1 - umount /mnt/f2fs The root cause is: it will update discard_max_bytes of mounted lvm device to zero after creating snapshot on this lvm device, then, __submit_discard_cmd() will pass parameter @nr_sects w/ zero value to __blkdev_issue_discard(), it returns a NULL bio pointer, result in panic. This patch changes as below for fixing: 1. Let's drop all remained discards in f2fs_unfreeze() if snapshot of lvm device is created. 2. Checking discard_max_bytes before submitting discard during __submit_discard_cmd().
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模块中在LVM设备上创建快照后丢弃操作的处理。
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-2024-56565
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2024-56565
请登录查看更多情报信息。
Same Patch Batch · Linux · 2024-12-27 · 221 CVEs total
| CVE-2024-56607 | wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() | |
| CVE-2024-56594 | drm/amdgpu: set the right AMDGPU sg segment limitation | |
| CVE-2024-56595 | jfs: add a check to prevent array-index-out-of-bounds in dbAdjTree | |
| CVE-2024-56596 | jfs: fix array-index-out-of-bounds in jfs_readdir | |
| CVE-2024-56597 | jfs: fix shift-out-of-bounds in dbSplit | |
| CVE-2024-56598 | jfs: array-index-out-of-bounds fix in dtReadFirst | |
| CVE-2024-56599 | wifi: ath10k: avoid NULL pointer error during sdio remove | |
| CVE-2024-56601 | net: inet: do not leave a dangling sk pointer in inet_create() | |
| CVE-2024-56600 | net: inet6: do not leave a dangling sk pointer in inet6_create() | |
| CVE-2024-56602 | net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() | |
| CVE-2024-56603 | net: af_can: do not leave a dangling sk pointer in can_create() | |
| CVE-2024-56604 | Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() | |
| CVE-2024-56605 | Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() | |
| CVE-2024-56606 | af_packet: avoid erroring out after sock_init_data() in packet_create() | |
| CVE-2024-56618 | pmdomain: imx: gpcv2: Adjust delay after power up handshake | |
| CVE-2024-56615 | bpf: fix OOB devmap writes when deleting elements | |
| CVE-2024-56616 | drm/dp_mst: Fix MST sideband message body length check | |
| CVE-2024-56617 | cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU | |
| CVE-2024-56614 | xsk: fix OOB map writes when deleting elements | |
| CVE-2024-56619 | nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() |
Showing top 20 of 221 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-46333
ptrace: slightly saner 'get_dumpable()' logic - CVE-2026-43490
ksmbd: validate inherited ACE SID length - CVE-2026-43489
liveupdate: luo_file: remember retrieve() status - CVE-2026-43487
ata: libata-core: Disable LPM on ST1000DM010-2EP102 - CVE-2026-43488
usb: xhci: Prevent interrupt storm on host controller error
Same vendor: Linux
- CVE-2026-46333
ptrace: slightly saner 'get_dumpable()' logic - CVE-2026-43490
ksmbd: validate inherited ACE SID length - CVE-2026-43489
liveupdate: luo_file: remember retrieve() status - CVE-2026-43487
ata: libata-core: Disable LPM on ST1000DM010-2EP102 - CVE-2026-43488
usb: xhci: Prevent interrupt storm on host controller error
V. Comments for CVE-2024-56565
No comments yet