Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64053: block: don't overwrite bip_vcnt in bio_integrity_copy_user()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 066be1439593a381b1a29663becfcfe0c92363e7, 0d48654af4d1390c888389206cc13b51b82c30e6, 637ad3a56a3b889527d1dacea6fea2a8bd648140.

Low priority for now. Upgrade to Linux Linux 066be1439593a381b1a29663becfcfe0c92363e7, 0d48654af4d1390c888389206cc13b51b82c30e6, 637ad3a56a3b889527d1dacea6fea2a8bd648140 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64053

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.11 and later · before 6.12.92
  • linux linux kernel6.13 and later · before 6.18.34
  • linux linux kernel6.19 and later · before 7.0.11
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.11affected
    • 3991657ae7074c3c497bf095093178bed37ea1b4 and later · before d18160c9525c63c203656fefd847e94b538cd4a4affected · git
    • 3991657ae7074c3c497bf095093178bed37ea1b4 and later · before 0d48654af4d1390c888389206cc13b51b82c30e6affected · git
    • 3991657ae7074c3c497bf095093178bed37ea1b4 and later · before 066be1439593a381b1a29663becfcfe0c92363e7affected · git
    • 3991657ae7074c3c497bf095093178bed37ea1b4 and later · before 637ad3a56a3b889527d1dacea6fea2a8bd648140affected · git
    • before 6.11not affected · semver
    • 6.12.92 and later · up to and including 6.12.*not affected · semver
    • 6.18.34 and later · up to and including 6.18.*not affected · semver
    • 7.0.11 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-docbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-headersbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-zfcpdump-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-zfcpdump-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10perfbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10python3-perfbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:9kernelbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64047Jul 19, 2026 · net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring
    39Monitor
  • ← EarlierCVE-2026-64048Jul 19, 2026 · net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot
    30Monitor
  • Later →CVE-2026-64057Jul 19, 2026 · afs: Fix the locking used by afs_get_link()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux066be1439593a381b1a29663becfcfe0c92363e7Vendor (CNA)
Linux Linux0d48654af4d1390c888389206cc13b51b82c30e6Vendor (CNA)
Linux Linux637ad3a56a3b889527d1dacea6fea2a8bd648140Vendor (CNA)
Linux Linuxd18160c9525c63c203656fefd847e94b538cd4a4Vendor (CNA)
almalinux:kernel5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-extra5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-687.51.1.el9_8 · Rocky Linux:9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records