CVE-2024-49859: f2fs: fix to check atomic_file in f2fs ioctl interfaces
f2fs: fix to check atomicfile in f2fs ioctl interfaces
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.56.1-5 - Compensating control
Update the Linux kernel to a version that includes the fix described as: "f2fs: fix to check atomic_file in f2fs ioctl interfaces" for f2fs ioctl functions f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() so they check atomic_write/atomic_file status to avoid race issues.
Event History
Frequently Asked Questions
What is the severity of CVE-2024-49859?
CVE-2024-49859 has a medium severity level that primarily affects file operations in the Linux kernel.
How do I fix CVE-2024-49859?
To fix CVE-2024-49859, update your Linux kernel to version 6.1.123-1 or newer.
Which Linux kernel versions are affected by CVE-2024-49859?
CVE-2024-49859 affects multiple versions of the Linux kernel, specifically those before version 6.1.113 and between versions 6.2 and 6.6.54.
What components in f2fs are impacted by CVE-2024-49859?
CVE-2024-49859 specifically impacts f2fs ioctl interfaces such as f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range().
Is CVE-2024-49859 related to file integrity?
Yes, CVE-2024-49859 is related to file integrity as it involves a failure to check atomic_write status in certain file operations.