Description (CNA)
In the Linux kernel, the following vulnerability has been resolved: smb/client: flush dirty data before punching a hole Punching a hole after a large buffered write may leave the range reported as data. Reproduce it with: xfs_io -f \ -c "pwrite -b 3m -S 0x61 0 3m" \ -c "fpunch 1m 1m" \ -c "seek -h 0" \ -c "seek -d 1m" \ /mnt/test/repro Punching 1 MiB at offset 1 MiB should produce: 0 1 MiB 2 MiB 3 MiB | DATA | HOLE | DATA | EOF Instead, the entire file is reported as data. SEEK_HOLE(0) returns EOF, and SEEK_DATA(1M) returns 1M. This happens because a dirty folio spanning the punched range can be written back after the punch and refill the hole. Fix this by flushing and waiting for dirty data in the punched range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA. The xfstests generic/539 pass against Samba/ksmbd with this change.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 before 216e469586057c29409e4ef8311d282388c6e251; affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 before 6c265aca08155e519a8f6f6071c59dff4f535f70; affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 before 39562a56cdb515f6635c3e7bfe6629439b18a169; affected 31742c5a331766bc7df6b0d525df00c6cd20d5a6 before d7d2adcd022baade5cab65ca492ce63421ce3a6e |
| Linux / Linux | affected 3.17; unaffected 0 before 3.17; unaffected 6.6.158 through 6.6.*; unaffected 6.12.111 through 6.12.*; unaffected 6.18.53 through 6.18.*; unaffected 7.2 through * |
CWE
No CWE identifiers supplied.