Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2023-52732

A critical flaw in the Linux kernel's Ceph client (kclient) could allow an attacker to cause memory corruption or incorrect data access when the client receives a corrupted snapshot trace from the MDS. The vulnerability has been resolved by a patch that blocks further I/O and metadata requests and evicts the kclient to prevent potential exploitation. Applying the kernel patch eliminates the risk.

publishedMay 21, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
41th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users, particularly those using the Ceph filesystem client.

02

Real-world impact

An attacker who can send a corrupted snap trace could potentially cause denial of service, data corruption, or arbitrary code execution with high impact on confidentiality, integrity, and availability.

03

Why this severity

CVSS v3.1 base score 9.8 (Critical) due to network‑adjacent attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 01Obtain the Linux kernel patch that resolves CVE-2023-52732 as referenced in the NVD description.
  2. 02Apply the patch to the affected kernel version.
  3. 03Reboot the system to load the patched kernel.

NVD description indicating the vulnerability has been resolved in the Linux kernel.

05

Timeline

  1. May 21, 2024 · May 21, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →