CVE-2023-52732: ceph: blocklist the kclient when receiving corrupted snap trace

Published May 21, 2024
·
Updated

ceph: blocklist the kclient when receiving corrupted snap trace

Affected Software

16 affected components
Linux Kernel
Linux Linux kernel>=2.6.35<6.1.13
Linux Linux kernel=2.6.34
Linux Linux kernel=2.6.34-rc2
Linux Linux kernel=2.6.34-rc3
Linux Linux kernel=2.6.34-rc4
Linux Linux kernel=2.6.34-rc5
Linux Linux kernel=2.6.34-rc6
Linux Linux kernel=2.6.34-rc7
Linux Linux kernel=6.2-rc1
Linux Linux kernel=6.2-rc2
Linux Linux kernel=6.2-rc3
Linux Linux kernel=6.2-rc4
Linux Linux kernel=6.2-rc5
Linux Linux kernel=6.2-rc6
Microsoft cbl2 kernel 5.15.186.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    In the Linux kernel’s Ceph handling, blocklist the kclient when receiving corrupted snap trace to stop all further IO/MDS requests (and then evict the kclient immediately).

Event History

May 21, 2024
CVE Published
via MITRE·03:22 PM
Data Sourced
via MITRE·03:22 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityAffected Software
Sep 27, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·01:01 AM
Affected Software
Updated
via Microsoft·01:01 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2023-52732?

CVE-2023-52732 has been classified with a medium severity level due to potential disruption of IO operations and metadata access in the Linux kernel.

2

How do I fix CVE-2023-52732?

To fix CVE-2023-52732, ensure you have updated to the latest stable release of the Linux kernel that addresses this vulnerability.

3

What versions of the Linux kernel are affected by CVE-2023-52732?

CVE-2023-52732 affects various versions of the Linux kernel where the Ceph file system is utilized.

4

What impact does CVE-2023-52732 have on system security?

CVE-2023-52732 may lead to compromised system integrity by allowing continued IO and metadata access despite receiving corrupted snap traces.

5

Is there a workaround for CVE-2023-52732 if I cannot apply the fix immediately?

Currently, there are no known workarounds for CVE-2023-52732, so applying the kernel update is essential for protection.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203