Menu

Star on GitHub · 3.2k

CVE-2026-64053

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: block: don't overwrite bip_vcnt in bio_integrity_copy_user() bio_integrity_add_page() already sets bip_vcnt to 1 for the bounce…

Published Jul 19, 2026EPSS 0.13%

Overview

CVE-2026-64053 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

block: don't overwrite bip_vcnt in bio_integrity_copy_user()

bio_integrity_add_page() already sets bip_vcnt to 1 for the bounce

segment. Overwriting it with nr_vecs breaks bip_vcnt <= bip_max_vcnt

on WRITE (bip_max_vcnt is 1), so the gap-merge checks in block/blk.h

read past the bip_vec[] flex array. On READ the read is in bounds

but lands on a saved user bvec instead of the bounce.

The line was added for split propagation, but bio_integrity_clone()

doesn't copy bip_vcnt and BIP_CLONE_FLAGS excludes BIP_COPY_USER.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64053?

CVE-2026-64053 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-64053?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64053?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64053?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64053 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all