Answer in brief
CVE-2026-68433 records a Unknown severity vulnerability in libceph: bound get_version reply decode to front len. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <340e0386aa39da181015bee38f309018c335ce16 || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <d60de8253c85a02d0e6194b0735e7a562981a04c || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <4e7ebfaa0d14cf50e44041bfde38070d6dbc019f || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <0d934c934ec746d53fc7e4f53239792647bbae63 || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 | 340e0386aa39da181015bee38f309018c335ce16, d60de8253c85a02d0e6194b0735e7a562981a04c, 4e7ebfaa0d14cf50e44041bfde38070d6dbc019f, 0d934c934ec746d53fc7e4f53239792647bbae63, d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 |
| Linux/Linuxgeneric | 3.16 | Not reported |
Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68433 records a Unknown severity vulnerability in libceph: bound get_version reply decode to front len. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <340e0386aa39da181015bee38f309018c335ce16 || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <d60de8253c85a02d0e6194b0735e7a562981a04c || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <4e7ebfaa0d14cf50e44041bfde38070d6dbc019f || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <0d934c934ec746d53fc7e4f53239792647bbae63 || >=513a8243d67f8e8d27f2883bd2f18bc87c7ca376 <d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 | 340e0386aa39da181015bee38f309018c335ce16, d60de8253c85a02d0e6194b0735e7a562981a04c, 4e7ebfaa0d14cf50e44041bfde38070d6dbc019f, 0d934c934ec746d53fc7e4f53239792647bbae63, d3c32939fa0e3ee9b883b9a0fd1972c5c444e3d0 |
| Linux/Linuxgeneric | 3.16 | Not reported |
Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.