ocfs2: fix data corruption after failed write
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6dbf7bb555981fb5faf7b691e8f6169fc2b2e63b · < 47eb055ad3588fc96d34e9e1dd87b210ce62906b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: fix data corruption after failed write
When buffered write fails to copy data into underlying page cache page, ocfs2_write_end_nolock() just zeroes out and dirties the page. This can leave dirty page beyond EOF and if page writeback tries to write this page before write succeeds and expands i_size, page gets into inconsistent state where page dirty bit is clear but buffer dirty bits stay set resulting in page data never getting written and so data copied to the page is lost. Fix the problem by invalidating page beyond EOF after failed write.
From the CVE record · Linux
The Linux kernel’s ocfs2 filesystem can lose data after a buffered write fails to copy data into a page beyond end-of-file. If writeback runs before a later write expands the file, the page can enter an inconsistent state and data subsequently copied to it may never be written. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with ocfs2 should check their versions against the vendor advisory; affected versions are not specified.