CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE
In the Linux kernel, the following vulnerability has been resolved:
libceph: bound pg{temp,upmap,upmapitems} length to CEPHPGMAXSIZE
decodepgtemp() decodes an user-controlled length but only rejects values large enough to overflow the allocation; it does not bound it to CEPHPGMAXSIZE. The helper backs both pgtemp and pgupmap decoding, and applyupmap()/gettemposds() later copy the decoded list into the fixed-size on-stack array struct cephosds.osds[CEPHPGMAXSIZE]. A monitor that sends an OSDMap with a pgtemp/pgupmap entry longer than 32 thus causes a stack out-of-bounds write.
An OSD set for a single PG can never exceed CEPHPGMAXSIZE, so reject longer entries at decode time. The bound is well below the old overflow threshold, so it also covers the allocation-size overflow the previous check guarded against.
BUG: KASAN: stack-out-of-bounds in cephpgtoupactingosds Write of size 4 ... by task exploit kasanreport (mm/kasan/report.c:595) cephpgtoupactingosds (net/ceph/osdmap.c:2617 net/ceph/osdmap.c:2833) calctarget (net/ceph/osdclient.c:1638) submitrequest (net/ceph/osdclient.c:2394) cephosdcstartrequest (net/ceph/osdclient.c:2490) cephosdccall (net/ceph/osdclient.c:5164) rbddevimageprobe (drivers/block/rbd.c:6899) dorbdadd (drivers/block/rbd.c:7138) ... kernel BUG at net/ceph/osdmap.c:2670!
[ idryomov: do the same in decodepgupmapitems() ]
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68159?
CVE-2026-68159 has a risk rating of 57, indicating a moderate severity level.
What systems are affected by CVE-2026-68159?
CVE-2026-68159 affects the Linux kernel, specifically related to the libceph component.
How do I fix CVE-2026-68159?
To resolve CVE-2026-68159, you should update your Linux kernel to the latest version where the vulnerability has been patched.
What potential impacts does CVE-2026-68159 have on my system?
CVE-2026-68159 could lead to memory allocation issues due to the lack of proper length bounds, potentially allowing for malicious exploitation.
When was CVE-2026-68159 published?
CVE-2026-68159 was published on August 10, 2026.