CVE-2023-52636Network attack vector

Kernel crash and data corruption via footer misparse

Published Apr 2, 2024 · Updated Aug 5, 2026

Improper message handling in affected Linux releases allows remote attackers controlling a Ceph OSD peer to corrupt read data or crash the kernel. After a short socket read ends at the sparse payload, read_partial_sparse_msg_data re-enters the OSD sparse-read state machine and treats footer bytes as a new sparse-read header. Exploitation requires a malicious or compromised OSD speaking msgr1 to a CephFS client using sparse reads; effects are limited to buffer-bounded read-data corruption, Ceph I/O failure, or a kernel crash.

CVSS severity8.2
High
EPSS probability0.51%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper message handling in affected Linux releases allows remote attackers controlling a Ceph OSD peer to corrupt read data or crash the kernel. After a short socket read ends at the sparse payload, read_partial_sparse_msg_data re-enters the OSD sparse-read state machine and treats footer bytes as a new sparse-read header. Exploitation requires a malicious or compromised OSD speaking msgr1 to a CephFS client using sparse reads; effects are limited to buffer-bounded read-data corruption, Ceph I/O failure, or a kernel crash.

The record

CVE
CVE-2023-52636
Published
Apr 2, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 2, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.6
  2. Affected versionversion=d396f89db39a2f259e2125ca43b4c31bb65afcad <8e46a2d068c92a905d01cbb018b00d66991585ab
  3. Affected versionversion=d396f89db39a2f259e2125ca43b4c31bb65afcad <bd9442e553ab8bf74b8be3b3c0a43bf4af4dc9b8
  4. Affected versionversion=d396f89db39a2f259e2125ca43b4c31bb65afcad <da9c33a70f095d5d55c36d0bfeba969e31de08ae

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.6; version=d396f89db39a2f259e2125ca43b4c31bb65afcad <8e46a2d068c92a905d01cbb018b00d66991585ab; version=d396f89db39a2f259e2125ca43b4c31bb65afcad <bd9442e553ab8bf74b8be3b3c0a43bf4af4dc9b8; version=d396f89db39a2f259e2125ca43b4c31bb65afcad <da9c33a70f095d5d55c36d0bfeba969e31de08ae

Published CVSS scores

8.2Linux Kernel CVE TeamCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
5.5NISTCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo