CVE-2023-53593

published 4 Oct 2025 · updated 7 Nov 2026

cifs: Release folio lock on fscache read hit.

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9e725386d4262ef23ae51993f04602bc535b5be2, Kernel 6.4.12, Kernel 7a9fb689c1a1dc373887621a3bfa3810df0abde4 and 2 more.

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: > The filesystem should unlock the folio once the read has completed, > 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 [<0>] folio_wait_bit_common+0x124/0x350 [<0>] filemap_read_folio+0xad/0xf0 [<0>] filemap_fault+0x8b1/0xab0 [<0>] __do_fault+0x39/0x150 [<0>] do_fault+0x25c/0x3e0 [<0>] __handle_mm_fault+0x6ca/0xc70 [<0>] handle_mm_fault+0xe9/0x350 [<0>] do_user_addr_fault+0x225/0x6c0 [<0>] exc_page_fault+0x84/0x1b0 [<0>] 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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=0174ee9947bd0f24fee2794b35258960d108b7aa <9e725386d4262ef23ae51993f04602bc535b5be2, >=6.2 <6.4.12, =5.17, =6.5, >=0174ee9947bd0f24fee2794b35258960d108b7aa <7a9fb689c1a1dc373887621a3bfa3810df0abde4, >=5.17.1 <6.1.47, >=0174ee9947bd0f24fee2794b35258960d108b7aa <69513dd669e243928f7450893190915a88f84a2b9e725386d4262ef23ae51993f04602bc535b5be2, 6.4.12, 7a9fb689c1a1dc373887621a3bfa3810df0abde4, 6.1.47, 69513dd669e243928f7450893190915a88f84a2b
linux-kernel: Kernel>=5.17.0 <6.1.47, >=6.2.0 <6.4.126.1.47, 6.4.12

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-53593 severity on Zeptric[![CVE-2023-53593](https://zeptric.io/badge/cve/CVE-2023-53593.svg)](https://zeptric.io/cve/CVE-2023-53593)