ocfs2: fix data corruption after failed write
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.14.312, 4.19.280, 5.4.240, 4.10, 5.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4.14.204 · fixed in 4.14.312; From 4.19.155 · fixed in 4.19.280; From 5.4.75 · fixed in 5.4.240; From 4.9.242 · fixed in 4.10; From 5.9.5 · fixed in 5.10
- Linux Linux
5.10
References 8
git.kernel.org
- stable/c/1629f6f522b2d058019710466a84b240683bbee3
- stable/c/c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45
- stable/c/4c24eb49ab44351424ac8fe8567f91ea48a06089
- stable/c/91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68
- stable/c/a9e53869cb43c96d6d851c491fd4e26430ab6ba6
- stable/c/47eb055ad3588fc96d34e9e1dd87b210ce62906b
- stable/c/205759c6c18f54659b0b5976b14a52d1b3eb9f57
- stable/c/90410bcf873cf05f54a32183afff0161f44f9715