CVE-2026-68131High· 7.5▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: rbd: Reset positive result codes to zero in object map update path In a reply message to an RBD request, a positive result code indicates a data payload, which is not …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.5%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
rbd: Reset positive result codes to zero in object map update path
In a reply message to an RBD request, a positive result code indicates a data payload, which is not allowed for writes. While rbd_osd_req_callback() already resets a positive result code for writes to zero, rbd_object_map_callback() does not. This allows a corrupted reply to an object map update to trigger the rbd_assert(*result < 0) in __rbd_obj_handle_request(). This happens, because rbd_object_map_callback() calls rbd_obj_handle_request() -> __rbd_obj_handle_request() and passes this positive result code. From __rbd_obj_handle_request(), rbd_obj_advance_write() is called, which leaves the positive result code unchanged and returns true. Therefore, the if(done && *result) branch is executed in __rbd_obj_handle_request() and the assertion triggers.
This patch fixes the issue by adjusting the logic in the rbd_object_map_callback() path. A positive result code for an object map update is now reset to zero (similar to rbd_osd_req_callback()), and the message is subsequently handled the same way as if the result code was zero from the beginning. Additionally, a WARN_ON_ONCE() is added for this case.
Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < cf1167292f606deaddac35ec384eba48f08a68d2Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < da926959bf791441ba06a80571708c3d0d3cc08fLinux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 6f33d9d539fb94e5a17589c2dfe271ff9bb64904Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 14995c4250f04b58bf6fc00e0e973a2e1b3cfb9bLinux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 2419aa74081007dc4d14ff5640659052dfdfd69aLinux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 34f2a2f32af570dfcc532ad70c080629ee1c32b0Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < b1a61366933224b3ad80975c4d01ac2cc6931ecfLinux >= 22e8bd51bb0469d1a524130a057f894ff632376a < a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4Linux 5.3Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets