CVE-2023-52636 Affecting kernel-azure-devel package, versions <5.14.21-150500.33.48.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-KERNELAZUREDEVEL-6808316
  • published4 May 2024
  • disclosed3 May 2024

Introduced: 3 May 2024

CVE-2023-52636  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 kernel-azure-devel to version 5.14.21-150500.33.48.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-azure-devel package and not the kernel-azure-devel package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

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 ]

CVSS Scores

version 3.1