CVE-2023-52636

libceph: just wait for more data to be available on the socket

MEDIUM
5.5
CVSS Score
Published: April 2, 2024 at 07:01 AM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: just wait for more data to be available on the socket A short read may occur while reading the message footer from the socket. Later, when the socket is ready for another read, the messenger invokes all read_partial_*() handlers, including read_partial_sparse_msg_data(). The expectation is that read_partial_sparse_msg_data() would bail, allowing the messenger to invoke read_partial() for the footer and pick up where it left off. However read_partial_sparse_msg_data() violates that and ends up calling into the state machine in the OSD client. The sparse-read state machine assumes that it's a new op and interprets some piece of the footer as the sparse-read header and returns bogus extents/data length, etc. To determine whether read_partial_sparse_msg_data() should bail, let's reuse cursor->total_resid. Because once it reaches to zero that means all the extents and data have been successfully received in last read, else it could break out when partially reading any of the extents and data. And then osd_sparse_read() could continue where it left off. [ idryomov: changelog ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.6 ≤ v < 6.6.176.6 ≤ v < 6.7.56.6 ≤ v < 6.86.7 ≤ v < 6.7.56.8 rc16.8 rc26.8 rc3d396f89db39a2f259e2125ca43b4c31bb65afcad
Vendor states this is fixed in 8e46a2d068c92a905d01cbb018b00d66991585ab (fixed)
Vendor states this is fixed in bd9442e553ab8bf74b8be3b3c0a43bf4af4dc9b8 (fixed)
Vendor states this is fixed in da9c33a70f095d5d55c36d0bfeba969e31de08ae (fixed)
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.17 (unaffected)
Vendor states this is fixed in 6.7.5 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8e46a2d068c92a905d01cbb018b00d66991585ab
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bd9442e553ab8bf74b8be3b3c0a43bf4af4dc9b8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/da9c33a70f095d5d55c36d0bfeba969e31de08ae

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card