CVE-2024-56565f2fs: fix to drop all discards after creating snapshot on lvm device
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
Published
- 22 months later
· 22 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 35ec7d5748849762008e8ae9f8ad2766229d5794 – < 0f3b00763dae90e94eed94a39d32d252d8750e9d
- affected 35ec7d5748849762008e8ae9f8ad2766229d5794 – < ed24ab98242f8d22b66fbe0452c97751b5ea4e22
- affected 35ec7d5748849762008e8ae9f8ad2766229d5794 – < 15136c3861a3341db261ebdbb6ae4ae1765635e2
- affected 35ec7d5748849762008e8ae9f8ad2766229d5794 – < bc8aeb04fd80cb8cfae3058445c84410fd0beb5e
- affected 4.19
- unaffected < 4.19
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.66 – ≤ 6.6.*
- unaffected 6.12.4 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References4
- https://git.kernel.org/stable/c/0f3b00763dae90e94eed94a39d32d252d8750e9d (opens in a new tab)
- https://git.kernel.org/stable/c/ed24ab98242f8d22b66fbe0452c97751b5ea4e22 (opens in a new tab)
- https://git.kernel.org/stable/c/15136c3861a3341db261ebdbb6ae4ae1765635e2 (opens in a new tab)
- https://git.kernel.org/stable/c/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-53213 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-56565)Record last updated .