CVE-2026-64232

publishedCWE-667

In the Linux kernel, the following vulnerability has been resolved: block: recompute nr_integrity_segments in blk_insert_cloned_request blk_insert_cloned_request() already recomputes nr_phys_segments against the bottom queue, because "the queue settings related to segment counting may differ from the original queue." The exact same reasoning applies to integrity segments: a stacked driver's underlying queue can have tighter virt_boundary_mask, seg_boundary_mask, or max_segment_size than the top queue, in which case blk_rq_count_integrity_sg() against the bottom queue produces a different count than the cached rq->nr_integrity_segments inherited from the source request by blk_rq_prep_clone(). When the cached count is lower than the bottom queue's actual count, blk_rq_map_integrity_sg() trips BUG_ON(segments > rq->nr_integrity_segments); on dispatch. The same families of stacked setups that motivated the existing nr_phys_segments recompute -- dm-multipath fanning out to nvme-rdma in particular -- can produce this. Mirror the nr_phys_segments handling: when the request carries integrity, recompute nr_integrity_segments against the bottom queue and reject the request if it exceeds the bottom queue's max_integrity_segments. blk_rq_count_integrity_sg() and queue_max_integrity_segments() are both already available via <linux/blk-integrity.h>, which blk-mq.c includes. This closes a latent gap in the stacking contract and brings the integrity-segment accounting in line with the existing phys-segment accounting.

Technical severity9.8 criticalCVSS 3.1 · NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Published2026-07-24Source updated 2026-11-08

Collected2026-11-091 attributed source

Fixes and workarounds

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
linux_kernel linux	≥ 6.12; < 6.12.92 (affected, custom)	NVD
linux_kernel linux	≥ 6.13; < 6.18.34 (affected, custom)	NVD
linux_kernel linux	≥ 6.19; < 7.0.11 (affected, custom)	NVD
linux_kernel linux	7.1 (affected, custom)	NVD

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

NVD applicability configurations (1)

These expressions retain AND/OR operators, negation, and required environmental products. A listed product is not sufficient to establish exposure when additional conditions apply.

[
  {
    "negate": false,
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "6.12.92",
            "versionStartIncluding": "6.12",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "6.18.34",
            "versionStartIncluding": "6.13",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "7.0.11",
            "versionStartIncluding": "6.19",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ],
    "operator": "OR"
  }
]

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / score	Vector	Authority
3.1 / 9.8 critical	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`	NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

https://git.kernel.org/stable/c/0943f81e1b3176f27dbaf6db268fc69d8a94f0ba416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
https://git.kernel.org/stable/c/2c6e6a18a37b905cb584eb0dda3ae482162a81ca416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
https://git.kernel.org/stable/c/42929c98d044f126508baf54a65b0f87f932fa75416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch
https://git.kernel.org/stable/c/53a01bcc0242590eda4c452a5bd996f62457113b416baaa9-dc9f-4396-8d5f-8c081fb06d67 · Patch

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API key Use x402 Connect an agent

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide