BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64232High confidence

block: recompute nr_integrity_segments in blk_insert_cloned_request

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.46% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64232 · CSAF 2.0 · revision 7 · interimSUSE Product Security TeamCVE-2026-64232
19 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.0
Summary
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 , 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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-48640

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2527Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260729Security Bulletin 29 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Jul 2026, published on 29 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64190 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-64214 https://www.cve.org/CVERecord?id=CVE-2026-64214 Référence CVE CVE-2026-64217 https://www.cve.org/CVERecord?id=CVE-2026-64217 Référence CVE CVE-2026-64219 https://www.cve.org/CVERecord?id=CVE-2026-64219 Référence CVE CVE-2026-64222 https://www.cve.org/CVERecord?id=CVE-2026-64222 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=CVE-2026-64240 Référence CVE CVE-2026-64243 https://www.cve.org/CVERecord?id=CVE-2026-64243 Référence CVE CVE-2026-64244 https://www.cve.org/CVERecord?id=CVE-2026-64244 Référence CVE CVE-2026-64245 https://www.cve.org/CVERecord?id=CVE-2026-64245 Référence CVE CVE-2026-64246 https://www.cve.org/CVERecord?id=CVE-2026-64246 Référence CVE CVE-2026-64247 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64223 Référence CVE CVE-2026-64224 https://www.cve.org/CVERecord?id=CVE-2026-64224 Référence CVE CVE-2026-64225 https://www.cve.org/CVERecord?id=CVE-2026-64225 Référence CVE CVE-2026-64226 https://www.cve.org/CVERecord?id=CVE-2026-64226 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64228 https://www.cve.org/CVERecord?id=CVE-2026-64228 Référence CVE CVE-2026-64229 https://www.cve.org/CVERecord?id=CVE-2026-64229 Référence CVE CVE-2026-64230 https://www.cve.org/CVERecord?id=CVE-2026-64230 Référence CVE CVE-2026-64231 https://www.cve.org/CVERecord?id=CVE-2026-64231 Référence CVE CVE-2026-64232 https://www.cve.org/CVERecord?id=CVE-2026-64232 Référence CVE CVE-2026-64233 https://www.cve.org/CVERecord?id=CVE-2026-64233 Référence CVE CVE-2026-64234 https://www.cve.org/CVERecord?id=CVE-2026-64234 Référence CVE CVE-2026-64235 https://www.cve.org/CVERecord?id=CVE-2026-64235 Référence CVE CVE-2026-64236 https://www.cve.org/CVERecord?id=CVE-2026-64236 Référence CVE CVE-2026-64237 https://www.cve.org/CVERecord?id=CVE-2026-64237 Référence CVE CVE-2026-64238 https://www.cve.org/CVERecord?id=CVE-2026-64238 Référence CVE CVE-2026-64239 https://www.cve.org/CVERecord?id=CVE-2026-64239 Référence CVE CVE-2026-64240 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028058LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。block: blk_insert_cloned_request における nr_integrity_segments の再計算について説明します。blk_insert_cloned_request() はすでにボトムキューに対して nr_phys_segments を再計算しています。これは「セグメント数に関連するキュー設定が元のキューと異なる場合がある」ためです。この理由は、integrityセグメントにも同様に当てはまります。積み重ねられたドライバの基底キューは、トップキューに比べて virtu_boundary_mask、seg_boundary_mask、または max_segment_size が厳しく設定されていることがあり、その場合、ボトムキューに対する blk_rq_count_integrity_sg() は、blk_rq_prep_clone() によりソースリクエストから引き継がれたキャッシュ済み rq-＞nr_integrity_segments と異なるカウントを返します。キャッシュされたカウントがボトムキューの実際のカウントより少ない場合、blk_rq_map_integrity_sg() は dispatch 時に BUG_ON(segments ＞ rq-＞nr_integrity_segments); をトリガーします。既存の nr_phys_segments の再計算を必要としたスタック構成、特に dm-multipath が nvme-rdma へファンアウトする場合と同様の状況がこれによって発生します。nr_phys_segments の処理を踏襲し、リクエストに integrity 情報が含まれている場合は、ボトムキューに対して nr_integrity_segments を再計算し、その数がボトムキューの max_integrity_segments を超えていた場合にはリクエストを拒否するようにしました。blk_rq_count_integrity_sg() と queue_max_integrity_segments() は ＜linux/blk-integrity.h＞ で既に提供されており、blk-mq.c がこれをインクルードしています。これにより、スタック化時の潜在的なギャップが解消され、integrityセグメントのカウント処理が既存の物理セグメントのカウント処理と整合されます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.12, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 24 Jul 2026 · Last source change 5 Aug 2026, 12:40 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-48640
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-48640↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64232 · cve.blacktree.nl