Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2026-64232

A critical bug in the Linux kernel’s block layer can cause a kernel crash when handling certain storage requests. The flaw arises from incorrect counting of integrity segments in stacked queue setups, leading to a BUG_ON that aborts the request. The issue has been fixed in recent kernel releases.

publishedJul 24, 2026
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
38th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 26, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel, all versions prior to the patch that includes the fix. Typical users include system administrators, Linux users, servers, and embedded devices that rely on the kernel’s block I/O subsystem.

02

Real-world impact

An attacker could crash the system by sending specially crafted block requests, potentially causing a denial‑of‑service condition.

03

Why this severity

The CVSS score of 9.8 reflects a critical severity because the vulnerability is remotely exploitable without authentication or user interaction, and it can lead to a complete system crash or denial of service.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the fix for the integrity segment accounting bug.
  2. 02Reboot the system to load the updated kernel.

NVD description indicates the vulnerability has been resolved in the Linux kernel.

05

Timeline

  1. Jul 24, 2026 · 8d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 27, 2026 · 5d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  3. Jul 30, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →