BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-53593High confidence

cifs: Release folio lock on fscache read hit.

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

13 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 9 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.52-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-53593 · CSAF 2.0 · revision 51 · interimSUSE Product Security TeamCVE-2023-53593
217 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-32276

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory ↗
BSI · German · WID-SEC-2025-2194Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251008Security Bulletin 08 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 Oct 2025, published on 8 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1073Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53581 Référence CVE CVE-2023-53582 https://www.cve.org/CVERecord?id=CVE-2023-53582 Référence CVE CVE-2023-53583 https://www.cve.org/CVERecord?id=CVE-2023-53583 Référence CVE CVE-2023-53585 https://www.cve.org/CVERecord?id=CVE-2023-53585 Référence CVE CVE-2023-53587 https://www.cve.org/CVERecord?id=CVE-2023-53587 Référence CVE CVE-2023-53588 https://www.cve.org/CVERecord?id=CVE-2023-53588 Référence CVE CVE-2023-53589 https://www.cve.org/CVERecord?id=CVE-2023-53589 Référence CVE CVE-2023-53591 https://www.cve.org/CVERecord?id=CVE-2023-53591 Référence CVE CVE-2023-53592 https://www.cve.org/CVERecord?id=CVE-2023-53592 Référence CVE CVE-2023-53593 https://www.cve.org/CVERecord?id=CVE-2023-53593 Référence CVE CVE-2023-53594 https://www.cve.org/CVERecord?id=CVE-2023-53594 Référence CVE CVE-2023-53596 https://www.cve.org/CVERecord?id=CVE-2023-53596 Référence CVE CVE-2023-53597 https://www.cve.org/CVERecord?id=CVE-2023-53597 Référence CVE CVE-2023-53598 https://www.cve.org/CVERecord?id=CVE-2023-53598 Référence CVE CVE-2023-53599 https://www.cve.org/CVERecord?id=CVE-2023-53599 Référence CVE CVE-2023-53600 https://www.cve.org/CVERecord?id=CVE-2023-53600 Référence CVE CVE-2023-53601 https://www.cve.org/CVERecord?id=CVE-2023-53601 Référence CVE CVE-2023-53602 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1047Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53579 Référence CVE CVE-2023-53580 https://www.cve.org/CVERecord?id=CVE-2023-53580 Référence CVE CVE-2023-53581 https://www.cve.org/CVERecord?id=CVE-2023-53581 Référence CVE CVE-2023-53582 https://www.cve.org/CVERecord?id=CVE-2023-53582 Référence CVE CVE-2023-53583 https://www.cve.org/CVERecord?id=CVE-2023-53583 Référence CVE CVE-2023-53585 https://www.cve.org/CVERecord?id=CVE-2023-53585 Référence CVE CVE-2023-53587 https://www.cve.org/CVERecord?id=CVE-2023-53587 Référence CVE CVE-2023-53588 https://www.cve.org/CVERecord?id=CVE-2023-53588 Référence CVE CVE-2023-53589 https://www.cve.org/CVERecord?id=CVE-2023-53589 Référence CVE CVE-2023-53593 https://www.cve.org/CVERecord?id=CVE-2023-53593 Référence CVE CVE-2023-53594 https://www.cve.org/CVERecord?id=CVE-2023-53594 Référence CVE CVE-2023-53596 https://www.cve.org/CVERecord?id=CVE-2023-53596 Référence CVE CVE-2023-53597 https://www.cve.org/CVERecord?id=CVE-2023-53597 Référence CVE CVE-2023-53599 https://www.cve.org/CVERecord?id=CVE-2023-53599 Référence CVE CVE-2023-53600 https://www.cve.org/CVERecord?id=CVE-2023-53600 Référence CVE CVE-2023-53601 https://www.cve.org/CVERecord?id=CVE-2023-53601 Référence CVE CVE-2023-53602 https://www.cve.org/CVERecord?id=CVE-2023-53602 Référence CVE CVE-2023-53603 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53581 Référence CVE CVE-2023-53582 https://www.cve.org/CVERecord?id=CVE-2023-53582 Référence CVE CVE-2023-53583 https://www.cve.org/CVERecord?id=CVE-2023-53583 Référence CVE CVE-2023-53585 https://www.cve.org/CVERecord?id=CVE-2023-53585 Référence CVE CVE-2023-53587 https://www.cve.org/CVERecord?id=CVE-2023-53587 Référence CVE CVE-2023-53588 https://www.cve.org/CVERecord?id=CVE-2023-53588 Référence CVE CVE-2023-53589 https://www.cve.org/CVERecord?id=CVE-2023-53589 Référence CVE CVE-2023-53591 https://www.cve.org/CVERecord?id=CVE-2023-53591 Référence CVE CVE-2023-53592 https://www.cve.org/CVERecord?id=CVE-2023-53592 Référence CVE CVE-2023-53593 https://www.cve.org/CVERecord?id=CVE-2023-53593 Référence CVE CVE-2023-53594 https://www.cve.org/CVERecord?id=CVE-2023-53594 Référence CVE CVE-2023-53596 https://www.cve.org/CVERecord?id=CVE-2023-53596 Référence CVE CVE-2023-53597 https://www.cve.org/CVERecord?id=CVE-2023-53597 Référence CVE CVE-2023-53598 https://www.cve.org/CVERecord?id=CVE-2023-53598 Référence CVE CVE-2023-53599 https://www.cve.org/CVERecord?id=CVE-2023-53599 Référence CVE CVE-2023-53600 https://www.cve.org/CVERecord?id=CVE-2023-53600 Référence CVE CVE-2023-53601 https://www.cve.org/CVERecord?id=CVE-2023-53601 Référence CVE CVE-2023-53602 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53574 Référence CVE CVE-2023-53575 https://www.cve.org/CVERecord?id=CVE-2023-53575 Référence CVE CVE-2023-53577 https://www.cve.org/CVERecord?id=CVE-2023-53577 Référence CVE CVE-2023-53579 https://www.cve.org/CVERecord?id=CVE-2023-53579 Référence CVE CVE-2023-53580 https://www.cve.org/CVERecord?id=CVE-2023-53580 Référence CVE CVE-2023-53581 https://www.cve.org/CVERecord?id=CVE-2023-53581 Référence CVE CVE-2023-53583 https://www.cve.org/CVERecord?id=CVE-2023-53583 Référence CVE CVE-2023-53585 https://www.cve.org/CVERecord?id=CVE-2023-53585 Référence CVE CVE-2023-53588 https://www.cve.org/CVERecord?id=CVE-2023-53588 Référence CVE CVE-2023-53593 https://www.cve.org/CVERecord?id=CVE-2023-53593 Référence CVE CVE-2023-53596 https://www.cve.org/CVERecord?id=CVE-2023-53596 Référence CVE CVE-2023-53597 https://www.cve.org/CVERecord?id=CVE-2023-53597 Référence CVE CVE-2023-53599 https://www.cve.org/CVERecord?id=CVE-2023-53599 Référence CVE CVE-2023-53600 https://www.cve.org/CVERecord?id=CVE-2023-53600 Référence CVE CVE-2023-53601 https://www.cve.org/CVERecord?id=CVE-2023-53601 Référence CVE CVE-2023-53602 https://www.cve.org/CVERecord?id=CVE-2023-53602 Référence CVE CVE-2023-53603 https://www.cve.org/CVERecord?id=CVE-2023-53603 Référence CVE CVE-2023-53611 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-025979LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルのcifsファイルシステムにおいて、fscacheの読み取りヒット時に適切にfolioのロックを解放しなかった問題が修正されました。この問題は、cifs_readpage_worker関数が呼び出された際にページのロックがリークし、mmap経由でページを読み取る際にデッドロックを引き起こす可能性がありました。本修正により、ページロックの扱いが正しくなり、システムの安定性が向上しました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.17, 6.1.47 ≤ 6.1.*, 6.4.12 ≤ 6.4.*, 6.5 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 4 Oct 2025 · Last source change 11 May 2026, 19:48 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-32276
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-32276↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-53593 · cve.blacktree.nl