Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2023-53593

medium

In the Linux kernel, the following vulnerability has been resolved: cifs: Release folio lock on fscache read hit.

Vendor / product: Linux — linux kernel

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 [] folio_wait_bit_common+0x124/0x350 [] filemap_read_folio+0xad/0xf0 [] filemap_fault+0x8b1/0xab0 [] __do_fault+0x39/0x150 [] do_fault+0x25c/0x3e0 [] __handle_mm_fault+0x6ca/0xc70 [] handle_mm_fault+0xe9/0x350 [] do_user_addr_fault+0x225/0x6c0 [] exc_page_fault+0x84/0x1b0 [] 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.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-10-04 16:15
Modified: 2026-11-05 21:17
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-05 21:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.17.1 <6.1.47, ≥6.2 <6.4.12, 5.17, 6.5

Weakness classification (CWE)

NVD-CWE-noinfo

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/69513dd669e243928f7450893190915a88f84a2b
Patch / mitigation: https://git.kernel.org/stable/c/7a9fb689c1a1dc373887621a3bfa3810df0abde4
Patch / mitigation: https://git.kernel.org/stable/c/9e725386d4262ef23ae51993f04602bc535b5be2

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 21:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs