CVE-2024-27036
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2024
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
cifs: Fix writeback data corruption
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix writeback data corruption cifs writeback doesn't correctly handle the case where cifs_extend_writeback() hits a point where it is considering an additional folio, but this would overrun the wsize - at which point it drops out of the xarray scanning loop and calls xas_pause(). The problem is that xas_pause() advances the loop counter - thereby skipping that page. What needs to happen is for xas_reset() to be called any time we decide we don't want to process the page we're looking at, but rather send the request we are building and start a new one. Fix this by copying and adapting the netfslib writepages code as a temporary measure, with cifs writeback intending to be offloaded to netfslib in the near future. This also fixes the issue with the use of filemap_get_folios_tag() causing retry of a bunch of pages which the extender already dealt with. This can be tested by creating, say, a 64K file somewhere not on cifs (otherwise copy-offload may get underfoot), mounting a cifs share with a wsize of 64000, copying the file to it and then comparing the original file and the copy: dd if=/dev/urandom of=/tmp/64K bs=64k count=1 mount //192.168.6.1/test /mnt -o user=...,pass=...,wsize=64000 cp /tmp/64K /mnt/64K cmp /tmp/64K /mnt/64K Without the fix, the cmp fails at position 64000 (or shortly thereafter).
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| d08089f649a0cfb2099c8551ac47eef0cc23fdf2 | affected | git | e45deec35bf7f1f4f992a707b2d04a8c162f2240 | Unavailable | None listed |
| d08089f649a0cfb2099c8551ac47eef0cc23fdf2 | affected | git | 65f2ced695982ccd516196d0a9447d85dbe2eed5 | Unavailable | None listed |
| d08089f649a0cfb2099c8551ac47eef0cc23fdf2 | affected | git | 844b4e132f57f1333dc79feaa035075a096762e4 | Unavailable | None listed |
| d08089f649a0cfb2099c8551ac47eef0cc23fdf2 | affected | git | f3dc1bdb6b0b0693562c7c54a6c28bafa608ba3c | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 6.3 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 6.3 | Unavailable | None listed |
| 6.6.23 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.7.11 | unaffected | semver | Unavailable | 6.7.* | None listed |
| 6.8.2 | unaffected | semver | Unavailable | 6.8.* | None listed |
| 6.9 | unaffected | original_commit_for_fix | Unavailable | * | None listed |