CVE-2023-53081
ocfs2: fix data corruption after failed write
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
ocfs2: fix data corruption after failed write
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.
Reserved 2025-05-02 | Published 2025-05-02 | Updated 2025-05-04 | Assigner Linuxgit.kernel.org/...c/1629f6f522b2d058019710466a84b240683bbee3
git.kernel.org/...c/c26f3ff4c0be590c1250f945ac2e4fc5fcdc5f45
git.kernel.org/...c/4c24eb49ab44351424ac8fe8567f91ea48a06089
git.kernel.org/...c/91d7a4bd5656552d6259e2d0f8859f9e8cc5ef68
git.kernel.org/...c/a9e53869cb43c96d6d851c491fd4e26430ab6ba6
git.kernel.org/...c/47eb055ad3588fc96d34e9e1dd87b210ce62906b
git.kernel.org/...c/205759c6c18f54659b0b5976b14a52d1b3eb9f57
git.kernel.org/...c/90410bcf873cf05f54a32183afff0161f44f9715
Support options
