---
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:

  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 …
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'
---

## Overview

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

- `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`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
