CVE-2021-47460
published 2024-05-22CVE-2021-47460: In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after conversion from inline format Commit 6dbf7bb55598 ("fs…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.4th percentile
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix data corruption after conversion from inline format
Commit 6dbf7bb55598 ("fs: Don't invalidate page buffers in
block_write_full_page()") uncovered a latent bug in ocfs2 conversion
from inline inode format to a normal inode format.
The code in ocfs2_convert_inline_data_to_extents() attempts to zero out
the whole cluster allocated for file data by grabbing, zeroing, and
dirtying all pages covering this cluster. However these pages are
beyond i_size, thus writeback code generally ignores these dirty pages
and no blocks were ever actually zeroed on the disk.
This oversight was fixed by commit 693c241a5f6a ("ocfs2: No need to zero
pages past i_size.") for standard ocfs2 write path, inline conversion
path was apparently forgotten; the commit log also has a reasoning why
the zeroing actually is not needed.
After commit 6dbf7bb55598, things became worse as writeback code stopped
invalidating buffers on pages beyond i_size and thus these pages end up
with clean PageDirty bit but with buffers attached to these pages being
still dirty. So when a file is converted from inline format, then
writeback triggers, and then the file is grown so that these pages
become valid, the invalid dirtiness state is preserved,
mark_buffer_dirty() does nothing on these pages (buffers are already
dirty) but page is never written back because it is clean. So data
written to these pages is lost once pages are reclaimed.
Simple reproducer for the problem is:
xfs_io -f -c "pwrite 0 2000" -c "pwrite 2000 2000" -c "fsync" \
-c "pwrite 4000 2000" ocfs2_file
After unmounting and mounting the fs again, you can observe that end of
'ocfs2_file' has lost its contents.
Fix the problem by not doing the pointless zeroing during conversion
from inline format similarly as in the standard write path.
[[email protected]: fix whitespace, per Joseph]
Affected
26 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.16-1 (bookworm) | linux 5.14.16-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 4.14.204 < 4.14.253 | 4.14.253 |
| linux | linux | >= 4.19.155 < 4.19.214 | 4.19.214 |
| linux | linux | >= 4.9.242 < 4.9.288 | 4.9.288 |
| linux | linux | >= 5.4.75 < 5.4.156 | 5.4.156 |
| linux | linux | >= 5.9.5 < 5.10 | 5.10 |
| linux | linux | >= 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b < f1b98569e81c37d7e0deada7172f8f60860c1360 | f1b98569e81c37d7e0deada7172f8f60860c1360 |
| linux | linux | >= 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b < fa9b6b6c953e3f6441ed6cf83b4c771dac2dae08 | fa9b6b6c953e3f6441ed6cf83b4c771dac2dae08 |
| linux | linux | >= 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b < 5314454ea3ff6fc746eaf71b9a7ceebed52888fa | 5314454ea3ff6fc746eaf71b9a7ceebed52888fa |
| linux | linux | >= 7ce2b16bad2cbfa3fa7bbc42c4448914f639ca47 < a3a089c241cd49b33a8cdd7fcb37cc87a086912a | a3a089c241cd49b33a8cdd7fcb37cc87a086912a |
| linux | linux | >= 7ed80e77c908cbaa686529a49f8ae0060c5caee7 < 8e6bfb4f70168ddfd32fb6dc028ad52faaf1f32e | 8e6bfb4f70168ddfd32fb6dc028ad52faaf1f32e |
| linux | linux | >= acef5107e2eacb08a16ad5db60320d65bd26a6c0 < 560edd14de2bf9dbc0129681eeb4d5ef87cc105f | 560edd14de2bf9dbc0129681eeb4d5ef87cc105f |
| linux | linux | >= f8a6a2ed4b7d1c3c8631eeb6d00572bc853094a8 < b05caf023b14cbed9223bb5b48ecc7bffe38f632 | b05caf023b14cbed9223bb5b48ecc7bffe38f632 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.84-1 | 5.10.84-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 0 < 5.14.16-1 | 5.14.16-1 |
| linux | linux_kernel | >= 4.14.204 < 4.14.253 | 4.14.253 |
| linux | linux_kernel | >= 4.19.155 < 4.19.214 | 4.19.214 |
| linux | linux_kernel | >= 4.9.242 < 4.9.288 | 4.9.288 |
| linux | linux_kernel | >= 5.11 < 5.14.15 | 5.14.15 |
| linux | linux_kernel | >= 5.4.75 < 5.4.156 | 5.4.156 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: ocfs2: fix data corruption after conversion from inline format
vendor_redhat·2024-05-22·CVSS 5.5
CVE-2021-47460 [MEDIUM] CWE-119 kernel: ocfs2: fix data corruption after conversion from inline format
kernel: ocfs2: fix data corruption after conversion from inline format
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix data corruption after conversion from inline format
Commit 6dbf7bb55598 ("fs: Don't invalidate page buffers in
block_write_full_page()") uncovered a latent bug in ocfs2 conversion
from inline inode format to a normal inode format.
The code in ocfs2_convert_inline_data_to_extents() attempts to zero out
the whole cluster allocated for file data by grabbing, zeroing, and
dirtying all pages covering this cluster. However these pages are
beyond i_size, thus writeback code generally ignores these dirty pages
and no blocks were ever actually zeroed on the disk.
This oversight was fixed by commit 693c241a5f6a ("ocfs2: No need to zero
pages past i_si
Debian
CVE-2021-47460: linux - In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix ...
vendor_debian·2021·CVSS 5.5
CVE-2021-47460 [MEDIUM] CVE-2021-47460: linux - In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix ...
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after conversion from inline format Commit 6dbf7bb55598 ("fs: Don't invalidate page buffers in block_write_full_page()") uncovered a latent bug in ocfs2 conversion from inline inode format to a normal inode format. The code in ocfs2_convert_inline_data_to_extents() attempts to zero out the whole cluster allocated for file data by grabbing, zeroing, and dirtying all pages covering this cluster. However these pages are beyond i_size, thus writeback code generally ignores these dirty pages and no blocks were ever actually zeroed on the disk. This oversight was fixed by commit 693c241a5f6a ("ocfs2: No need to zero pages past i_size.") for standard ocfs2 write path, inline conversion path was apparent
OSV
CVE-2021-47460: In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after conversion from inline format Commit 6dbf7bb55598
osv·2024-05-22·CVSS 5.5
CVE-2021-47460 [MEDIUM] CVE-2021-47460: In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after conversion from inline format Commit 6dbf7bb55598
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix data corruption after conversion from inline format Commit 6dbf7bb55598 ("fs: Don't invalidate page buffers in block_write_full_page()") uncovered a latent bug in ocfs2 conversion from inline inode format to a normal inode format. The code in ocfs2_convert_inline_data_to_extents() attempts to zero out the whole cluster allocated for file data by grabbing, zeroing, and dirtying all pages covering this cluster. However these pages are beyond i_size, thus writeback code generally ignores these dirty pages and no blocks were ever actually zeroed on the disk. This oversight was fixed by commit 693c241a5f6a ("ocfs2: No need to zero pages past i_size.") for standard ocfs2 write path, inline conversion path was apparent
GHSA
GHSA-f639-593q-rjgw: In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix data corruption after conversion from inline format
Commit 6dbf7bb555
ghsa_unreviewed·2024-05-22
CVE-2021-47460 [MEDIUM] GHSA-f639-593q-rjgw: In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix data corruption after conversion from inline format
Commit 6dbf7bb555
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix data corruption after conversion from inline format
Commit 6dbf7bb55598 ("fs: Don't invalidate page buffers in
block_write_full_page()") uncovered a latent bug in ocfs2 conversion
from inline inode format to a normal inode format.
The code in ocfs2_convert_inline_data_to_extents() attempts to zero out
the whole cluster allocated for file data by grabbing, zeroing, and
dirtying all pages covering this cluster. However these pages are
beyond i_size, thus writeback code generally ignores these dirty pages
and no blocks were ever actually zeroed on the disk.
This oversight was fixed by commit 693c241a5f6a ("ocfs2: No need to zero
pages past i_size.") for standard ocfs2 write path, inline conversion
path was appa
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/5314454ea3ff6fc746eaf71b9a7ceebed52888fahttps://git.kernel.org/stable/c/560edd14de2bf9dbc0129681eeb4d5ef87cc105fhttps://git.kernel.org/stable/c/8e6bfb4f70168ddfd32fb6dc028ad52faaf1f32ehttps://git.kernel.org/stable/c/a3a089c241cd49b33a8cdd7fcb37cc87a086912ahttps://git.kernel.org/stable/c/b05caf023b14cbed9223bb5b48ecc7bffe38f632https://git.kernel.org/stable/c/f1b98569e81c37d7e0deada7172f8f60860c1360https://git.kernel.org/stable/c/fa9b6b6c953e3f6441ed6cf83b4c771dac2dae08https://git.kernel.org/stable/c/5314454ea3ff6fc746eaf71b9a7ceebed52888fahttps://git.kernel.org/stable/c/560edd14de2bf9dbc0129681eeb4d5ef87cc105fhttps://git.kernel.org/stable/c/8e6bfb4f70168ddfd32fb6dc028ad52faaf1f32ehttps://git.kernel.org/stable/c/a3a089c241cd49b33a8cdd7fcb37cc87a086912ahttps://git.kernel.org/stable/c/b05caf023b14cbed9223bb5b48ecc7bffe38f632https://git.kernel.org/stable/c/f1b98569e81c37d7e0deada7172f8f60860c1360https://git.kernel.org/stable/c/fa9b6b6c953e3f6441ed6cf83b4c771dac2dae08
2024-05-22
Published