medium CVSS 5.5

CVE-2023-52732·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: ceph: blocklist the kclient when receiving corrupted snap trace When received corrupted snap trace we don't know what exactly has happened in MDS side. And we shouldn't continue IOs and metadatas access to MDS, which may corrupt or get incorrect contents. This patch will just block all the further IO/MDS requests immediately and then evict the kclient itself. The reason why we still need to evict the kclient just after blocking all the further IOs is that the MDS could revoke the caps faster.

Severity
medium
Software
Kernel
Fixed in
6.1.13
Published
2024-05-21

Affected versions

From: 2.6.35

Until: 6.1.13

Fixed in: 6.1.13

How to fix this CVE

Update your Linux kernel to version 6.1.13 or later to address this Ceph filesystem vulnerability that can cause data corruption when corrupted snap traces are received from the MDS server. This patch implements defensive blocklisting to prevent further I/O operations when trace corruption is detected, protecting your cluster from inconsistent state propagation. Apply the update through your distribution's package manager and reboot the system to activate the patched kernel.

sudo dnf check-update kernel && sudo dnf upgrade kernel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check current kernel version: uname -r | awk -F'.' '{print $1"."$2"."$3}'
  2. Verify if Ceph client is active: ps aux | grep -i ceph | grep -v grep
  3. Search system logs for snap trace errors: sudo grep -i 'snap trace\|corrupted trace' /var/log/kern.log /var/log/messages 2>/dev/null
  4. Confirm patch application by checking kernel build date: uname -v or dmesg | grep 'Linux version' and compare against release date of 6.1.13

FAQ

What is CVE-2023-52732?

This vulnerability exists in the Linux kernel's Ceph filesystem client when handling corrupted snapshot trace metadata from the MDS server. Without proper validation, the client would continue processing I/O operations with potentially inconsistent data, risking silent data corruption across the cluster.

Is CVE-2023-52732 being actively exploited?

No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. Exploitation requires either a compromised MDS server or a network-level man-in-the-middle attack to inject corrupted metadata.

What versions of Kernel are affected by CVE-2023-52732?

Linux kernel versions from 2.6.35 through 6.1.12 are affected. The vulnerability is patched in kernel 6.1.13 and all subsequent releases.

How do I check if my server is vulnerable to CVE-2023-52732?

Run 'uname -r' to display your kernel version. If the output shows version 6.1.12 or earlier, your system requires a kernel update. For versions between 2.6.35 and 6.1.12, the vulnerability is present.

Does Defensia detect CVE-2023-52732?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2023-52732 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2026-43501CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows ipv6_rpl_srh_rcv() decompresses an RFC 6554 Source Routing Header, swaps the next segment into ipv6_hdr->daddr, recompresses, then pulls the old header and pushes the new one plus the IPv6 header back. The recompressed header can be larger than the received one when the swap reduces the common-prefix length the segments share with daddr (CmprI=0, CmprE>0, seg[0][0] != daddr[0] gives the maximum +8 bytes). pskb_expand_head() was gated on segments_left == 0, so on earlier segments the push consumed unchecked headroom. Once skb_push() leaves fewer than skb->mac_len bytes in front of data, skb_mac_header_rebuild()'s call to: skb_set_mac_header(skb, -skb->mac_len); will store (data - head) - mac_len into the u16 mac_header field, which wraps to ~65530, and the following memmove() writes mac_len bytes ~64KiB past skb->head. A single AF_INET6/SOCK_RAW/IPV6_HDRINCL packet over lo with a two segment type-3 SRH (CmprI=0, CmprE=15) reaches headroom 8 after one pass; KASAN reports a 14-byte OOB write in ipv6_rthdr_rcv. Fix this by expanding the head whenever the remaining room is less than the push size plus mac_len, and request that much extra so the rebuilt MAC header fits afterwards.
CVE-2026-64385CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_ioctl() replay A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_ioctl_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.
CVE-2026-64391CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ksmbd: use opener credentials for ADS I/O Alternate data streams are stored as xattrs. Unlike regular file I/O, their read and write paths therefore call VFS xattr helpers which recheck inode permissions and LSM policy using the current task credentials. Run ADS I/O with the credentials captured when the SMB handle was opened.
CVE-2026-64383CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.
CVE-2026-53176CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN In drivers/infiniband/ulp/isert/ib_isert.c, isert_login_recv_done() computes the login request payload length as wc->byte_len minus ISER_HEADERS_LEN with no lower bound, and login_req_len is a signed int. A remote iSER initiator can post a login Send work request carrying fewer than ISER_HEADERS_LEN (76) bytes, so the subtraction underflows and login_req_len becomes negative. isert_rx_login_req() then reads that negative length back into a signed int, takes size = min(rx_buflen, MAX_KEY_VALUE_PAIRS), and because the min() is signed it keeps the negative value; the value is then passed as the memcpy() length and sign-extended to a multi-gigabyte size_t. The copy into the 8192-byte login->req_buf runs far out of bounds and faults, crashing the target node. The login phase precedes iSCSI authentication, so no credentials are required to reach this path. Reject any login PDU shorter than ISER_HEADERS_LEN before the subtraction, mirroring the existing early return on a failed work completion, so login_req_len can never go negative. The upper bound was already safe: a posted login buffer cannot deliver more than ISER_RX_PAYLOAD_SIZE, so the difference stays at or below MAX_KEY_VALUE_PAIRS and the existing min() clamps it; only the missing lower bound needs to be added.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2023-52732. Free for 1 server.

Get started free