CVE-2026-68433
libceph: bound get_version reply decode to front len
Description
In the Linux kernel, the following vulnerability has been resolved: libceph: bound get_version reply decode to front len handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually received. A truncated reply can therefore pass ceph_decode_need() and decode the second u64 from stale tail bytes left in the buffer by an earlier message, causing an uninitialized memory read. Use msg->front.iov_len as the receive-side decode boundary, matching other libceph reply handlers and limiting decoding to the bytes that were actually read from the wire.
INFO
Published Date :
Aug. 12, 2026, 12:17 a.m.
Last Modified :
Aug. 12, 2026, 12:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68433
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Limit decoding to actual received bytes.
- Use msg->front.iov_len as decode boundary.
- Apply the patch for libceph.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68433.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68433 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68433
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68433 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68433 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 12, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '513a8243d67f8e8d27f2883bd2f18bc87c7ca376', 'lessThan': '340e0386aa39da181015bee38f309018c335ce16', 'versionType': 'git'}, {'status': 'affected', 'version': '513a8243d67f8e8d27f2883bd2f18bc87c7ca376', 'lessThan': 'd60de8253c85a02d0e6194b0735e7a562981a04c', 'versionType': 'git'}, {'status': 'affected', 'version': '513a8243d67f8e8d27f2883bd2f18bc87c7ca376', 'lessThan': '4e7ebfaa0d14cf50e44041bfde38070d6dbc019f', 'versionType': 'git'}, {'status': 'affected', 'version': '513a8243d67f8e8d27f2883bd2f18bc87c7ca376', 'lessThan': '0d934c934ec746d53fc7e4f53239792647bbae63', 'versionType': 'git'}, {'status': 'affected', 'version': '513a8243d67f8e8d27f2883bd2f18bc87c7ca376', 'lessThan': 'd3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0', 'versionType': 'git'}], 'programFiles': ['net/ceph/mon_client.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.16'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.16', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc5', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/ceph/mon_client.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: libceph: bound get_version reply decode to front len handle_get_version_reply() uses msg->front_alloc_len as the decode boundary for MON_GET_VERSION_REPLY. That is the size of the reused reply buffer, not the number of bytes actually received. A truncated reply can therefore pass ceph_decode_need() and decode the second u64 from stale tail bytes left in the buffer by an earlier message, causing an uninitialized memory read. Use msg->front.iov_len as the receive-side decode boundary, matching other libceph reply handlers and limiting decoding to the bytes that were actually read from the wire. Added Reference https://git.kernel.org/stable/c/0d934c934ec746d53fc7e4f53239792647bbae63 Added Reference https://git.kernel.org/stable/c/340e0386aa39da181015bee38f309018c335ce16 Added Reference https://git.kernel.org/stable/c/4e7ebfaa0d14cf50e44041bfde38070d6dbc019f Added Reference https://git.kernel.org/stable/c/d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 Added Reference https://git.kernel.org/stable/c/d60de8253c85a02d0e6194b0735e7a562981a04c