{"id":"DEBIAN-CVE-2023-53593","details":"In the Linux kernel, the following vulnerability has been resolved:  cifs: Release folio lock on fscache read hit.  Under the current code, when cifs_readpage_worker is called, the call contract is that the callee should unlock the page. This is documented in the read_folio section of Documentation/filesystems/vfs.rst as:  \u003e The filesystem should unlock the folio once the read has completed, \u003e whether it was successful or not.  Without this change, when fscache is in use and cache hit occurs during a read, the page lock is leaked, producing the following stack on subsequent reads (via mmap) to the page:  $ cat /proc/3890/task/12864/stack [\u003c0\u003e] folio_wait_bit_common+0x124/0x350 [\u003c0\u003e] filemap_read_folio+0xad/0xf0 [\u003c0\u003e] filemap_fault+0x8b1/0xab0 [\u003c0\u003e] __do_fault+0x39/0x150 [\u003c0\u003e] do_fault+0x25c/0x3e0 [\u003c0\u003e] __handle_mm_fault+0x6ca/0xc70 [\u003c0\u003e] handle_mm_fault+0xe9/0x350 [\u003c0\u003e] do_user_addr_fault+0x225/0x6c0 [\u003c0\u003e] exc_page_fault+0x84/0x1b0 [\u003c0\u003e] asm_exc_page_fault+0x27/0x30  This requires a reboot to resolve; it is a deadlock.  Note however that the call to cifs_readpage_from_fscache does mark the page clean, but does not free the folio lock. This happens in __cifs_readpage_from_fscache on success. Releasing the lock at that point however is not appropriate as cifs_readahead also calls cifs_readpage_from_fscache and *does* unconditionally release the lock after its return. This change therefore effectively makes cifs_readpage_worker work like cifs_readahead.","modified":"2026-09-15T09:02:55.354477959Z","published":"2025-10-04T16:15:55.790Z","upstream":["CVE-2023-53593"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2023-53593"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:12","purl":"pkg:deb/debian/linux?arch=source&distro=bookworm"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.52-1"}]}],"versions":["6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1"],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53593.json"}},{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.13-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53593.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.13-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53593.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}