CVE-2023-52636
Last modified
CVE-2023-52636 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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(). EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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 ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.6.17 | — |
| Linux | Linux Kernel | >= 6.7, < 6.7.5 | — |
| Linux | Linux Kernel | 6.8 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2023-52636?
How severe is CVE-2023-52636?
How do I fix CVE-2023-52636?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-52630Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-52631In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52632In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52633In the Linux kernel, the following vulnerability has been re…5
- CVE-2023-52634In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52635In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52637In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-52638In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52639In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-5264A vulnerability classified as critical was found in huakecms…7.2
- CVE-2023-52640In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2023-52641In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-52636?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
