Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-68131

rbd: Reset positive result codes to zero in object map update path

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in cf1167292f606deaddac35ec384eba48f08a68d2; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in da926959bf791441ba06a80571708c3d0d3cc08f; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in 6f33d9d539fb94e5a17589c2dfe271ff9bb64904; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in 14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in 2419aa74081007dc4d14ff5640659052dfdfd69a; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in 34f2a2f32af570dfcc532ad70c080629ee1c32b0; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in b1a61366933224b3ad80975c4d01ac2cc6931ecf; From 22e8bd51bb0469d1a524130a057f894ff632376a · fixed in a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4

  • Linux Linux

    5.3

  • KernelLinux

    From 5.3.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.148; From 6.7.0 · fixed in 6.12.101; From 6.13.0 · fixed in 6.18.42; From 6.19.0 · fixed in 7.1.6

References 8

git.kernel.org