CVE-2026-68131

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

HIGH
7.5
CVSS Score
Published: August 10, 2026 at 11:58 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

22e8bd51bb0469d1a524130a057f894ff632376a5.3
Vendor states this is fixed in 14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b (fixed)
Vendor states this is fixed in 2419aa74081007dc4d14ff5640659052dfdfd69a (fixed)
Vendor states this is fixed in 34f2a2f32af570dfcc532ad70c080629ee1c32b0 (fixed)
Vendor states this is fixed in 6f33d9d539fb94e5a17589c2dfe271ff9bb64904 (fixed)
Vendor states this is fixed in a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4 (fixed)
Vendor states this is fixed in b1a61366933224b3ad80975c4d01ac2cc6931ecf (fixed)
Vendor states this is fixed in cf1167292f606deaddac35ec384eba48f08a68d2 (fixed)
Vendor states this is fixed in da926959bf791441ba06a80571708c3d0d3cc08f (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card