- Vulnerability/
- CVE-2024-56565
CVE-2024-56565: f2fs: fix to drop all discards after creating snapshot on lvm device
First published: Fri Dec 27 2024(Updated: )
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().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.133-1 | 6.12.22-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/15136c3861a3341db261ebdbb6ae4ae1765635e2
- https://git.kernel.org/stable/c/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e
- https://git.kernel.org/stable/c/ed24ab98242f8d22b66fbe0452c97751b5ea4e22
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56565
- https://nvd.nist.gov/vuln/detail/CVE-2024-56565
- https://launchpad.net/bugs/cve/CVE-2024-56565
- https://security-tracker.debian.org/tracker/CVE-2024-56565
- https://ubuntu.com/security/CVE-2024-56565
- https://git.kernel.org/linus/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e
Frequently Asked Questions
What is the severity of CVE-2024-56565?
CVE-2024-56565 has been classified with a moderate severity level.
How do I fix CVE-2024-56565?
To fix CVE-2024-56565, you should update your Linux kernel to the latest stable version that addresses this vulnerability.
What systems are affected by CVE-2024-56565?
CVE-2024-56565 affects the Linux kernel, particularly systems using f2fs and LVM for snapshot management.
What are the potential impacts of CVE-2024-56565?
The potential impacts of CVE-2024-56565 include data loss or corruption during snapshot operations on devices using f2fs.
Who reported the CVE-2024-56565 vulnerability?
CVE-2024-56565 was reported by Piergiorgio, who documented the issue in Bugzilla.
- agent/severity
- agent/title
- agent/first-publish-date
- agent/type
- collector/nvd-api
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/source
- agent/tags
- agent/description
- agent/event
- agent/softwarecombine
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian