CVE-2021-47114: ocfs2: fix data corruption by fallocate
First published: Fri Mar 15 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption by fallocate When fallocate punches holes out of inode size, if original isize is in the middle of last cluster, then the part from isize to the end of the cluster will be zeroed with buffer write, at that time isize is not yet updated to match the new size, if writeback is kicked in, it will invoke ocfs2_writepage()->block_write_full_page() where the pages out of inode size will be dropped. That will cause file corruption. Fix this by zero out eof blocks when extending the inode size. Running the following command with qemu-image 4.2.1 can get a corrupted coverted image file easily. qemu-img convert -p -t none -T none -f qcow2 $qcow_image \ -O qcow2 -o compat=1.1 $qcow_image.conv The usage of fallocate in qemu is like this, it first punches holes out of inode size, then extend the inode size. fallocate(11, FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE, 2276196352, 65536) = 0 fallocate(11, 0, 2276196352, 65536) = 0 v1: https://www.spinics.net/lists/linux-fsdevel/msg193999.html v2: https://lore.kernel.org/linux-fsdevel/20210525093034.GB4112@quack2.suse.cz/T/
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| QEMU |
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/624fa7baa3788dc9e57840ba5b94bc22b03cda57
- https://git.kernel.org/stable/c/33e03adafb29eedae1bae9cdb50c1385279fcf65
- https://git.kernel.org/stable/c/a1700479524bb9cb5e8ae720236a6fabd003acae
- https://git.kernel.org/stable/c/cec4e857ffaa8c447f51cd8ab4e72350077b6770
- https://git.kernel.org/stable/c/cc2edb99ea606a45182b5ea38cc8f4e583aa0774
- https://git.kernel.org/stable/c/c8d5faee46242c3f33b8a71a4d7d52214785bfcc
- https://git.kernel.org/stable/c/0a31dd6fd2f4e7db538fb6eb1f06973d81f8dd3b
- https://git.kernel.org/stable/c/6bba4471f0cc1296fe3c2089b9e52442d3074b2e
Frequently Asked Questions
What is the severity of CVE-2021-47114?
CVE-2021-47114 is classified with a moderate severity level due to the potential for data corruption.
How do I fix CVE-2021-47114?
To fix CVE-2021-47114, update the Linux kernel to the latest stable version that includes the patch for this vulnerability.
What systems are affected by CVE-2021-47114?
CVE-2021-47114 affects the Linux Kernel and QEMU's qemu-img utility.
What type of vulnerability is CVE-2021-47114?
CVE-2021-47114 is a data corruption vulnerability that occurs when using fallocate to manipulate file allocations.
Does CVE-2021-47114 require immediate action?
Yes, administrators should assess their systems and apply necessary updates to mitigate potential data corruption risks.
- agent/title
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- collector/nvd-api
- source/NVD
- agent/severity
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/linux
- canonical/linux kernel
- vendor/qemu
- canonical/qemu