{"id":"CVE-2026-68131","title":"rbd: Reset positive result codes to zero in object map update path","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nrbd: Reset positive result codes to zero in object map update path\n\nIn a reply message to an RBD request, a positive result code indicates\na data payload, which is not …","severity":"high","cvss":7.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < cf1167292f606deaddac35ec384eba48f08a68d2","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < da926959bf791441ba06a80571708c3d0d3cc08f","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 6f33d9d539fb94e5a17589c2dfe271ff9bb64904","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 2419aa74081007dc4d14ff5640659052dfdfd69a","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 34f2a2f32af570dfcc532ad70c080629ee1c32b0","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < b1a61366933224b3ad80975c4d01ac2cc6931ecf","Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4","Linux 5.3"],"ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial","timestamp":"2026-10-16T15:44:26.632353Z"},"published":"2026-08-10","updated":"2026-10-16","sourceUpdated":"2026-10-16T15:52:58.739Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-68131","references":[{"url":"https://git.kernel.org/stable/c/cf1167292f606deaddac35ec384eba48f08a68d2"},{"url":"https://git.kernel.org/stable/c/da926959bf791441ba06a80571708c3d0d3cc08f"},{"url":"https://git.kernel.org/stable/c/6f33d9d539fb94e5a17589c2dfe271ff9bb64904"},{"url":"https://git.kernel.org/stable/c/14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b"},{"url":"https://git.kernel.org/stable/c/2419aa74081007dc4d14ff5640659052dfdfd69a"},{"url":"https://git.kernel.org/stable/c/34f2a2f32af570dfcc532ad70c080629ee1c32b0"},{"url":"https://git.kernel.org/stable/c/b1a61366933224b3ad80975c4d01ac2cc6931ecf"},{"url":"https://git.kernel.org/stable/c/a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4"}],"tags":["cve.org"],"epss":0.00523,"epssPercentile":0.43128,"ingestedAt":"2026-10-16T17:24:46.841Z","slug":"CVE-2026-68131","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrbd: Reset positive result codes to zero in object map update path\n\nIn a reply message to an RBD request, a positive result code indicates\na data payload, which is not allowed for writes. While\nrbd_osd_req_callback() already resets a positive result code for writes\nto zero, rbd_object_map_callback() does not. This allows a corrupted\nreply to an object map update to trigger the rbd_assert(*result < 0) in\n__rbd_obj_handle_request(). This happens, because\nrbd_object_map_callback() calls rbd_obj_handle_request() ->\n__rbd_obj_handle_request() and passes this positive result code. From\n__rbd_obj_handle_request(), rbd_obj_advance_write() is called, which\nleaves the positive result code unchanged and returns true. Therefore,\nthe if(done && *result) branch is executed in __rbd_obj_handle_request()\nand the assertion triggers.\n\nThis patch fixes the issue by adjusting the logic in the\nrbd_object_map_callback() path. A positive result code for an object map\nupdate is now reset to zero (similar to rbd_osd_req_callback()), and the\nmessage is subsequently handled the same way as if the result code was\nzero from the beginning. Additionally, a WARN_ON_ONCE() is added for\nthis case.\n\n## Affected\n\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < cf1167292f606deaddac35ec384eba48f08a68d2`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < da926959bf791441ba06a80571708c3d0d3cc08f`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 6f33d9d539fb94e5a17589c2dfe271ff9bb64904`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 2419aa74081007dc4d14ff5640659052dfdfd69a`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < 34f2a2f32af570dfcc532ad70c080629ee1c32b0`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < b1a61366933224b3ad80975c4d01ac2cc6931ecf`\n- `Linux >= 22e8bd51bb0469d1a524130a057f894ff632376a < a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4`\n- `Linux 5.3`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}