- Vulnerability/
- CVE-2024-27036
CVE-2024-27036: cifs: Fix writeback data corruption
First published: Wed May 01 2024(Updated: )
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).
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/65f2ced695982ccd516196d0a9447d85dbe2eed5
- https://git.kernel.org/stable/c/844b4e132f57f1333dc79feaa035075a096762e4
- https://git.kernel.org/stable/c/e45deec35bf7f1f4f992a707b2d04a8c162f2240
- https://git.kernel.org/stable/c/f3dc1bdb6b0b0693562c7c54a6c28bafa608ba3c
- https://launchpad.net/bugs/cve/CVE-2024-27036
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-27036
- https://nvd.nist.gov/vuln/detail/CVE-2024-27036
- https://security-tracker.debian.org/tracker/CVE-2024-27036
- https://ubuntu.com/security/CVE-2024-27036
- https://git.kernel.org/linus/f3dc1bdb6b0b0693562c7c54a6c28bafa608ba3c
Frequently Asked Questions
What is the severity of CVE-2024-27036?
CVE-2024-27036 has a severity rating of medium due to its impact on writeback data integrity in the Linux kernel.
How do I fix CVE-2024-27036?
To fix CVE-2024-27036, update your Linux kernel to one of the patched versions: 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.
What kind of systems are affected by CVE-2024-27036?
CVE-2024-27036 affects systems running specific versions of the Linux kernel with cifs functionality.
Is CVE-2024-27036 a remote code execution vulnerability?
No, CVE-2024-27036 does not directly lead to remote code execution but impacts the integrity of data written back through cifs.
When was CVE-2024-27036 disclosed?
CVE-2024-27036 was disclosed following the identification of a bug in the Linux kernel's handling of writeback data.
- agent/severity
- agent/title
- agent/type
- collector/nvd-api
- source/NVD
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/last-modified-date
- agent/references
- agent/event
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- package-manager/debian