CVE-2026-64053
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.
Affected versions
Linux kernel versions
6.11
and later are affected. Fixed in
6.12.92,
6.18.34,
7.0.11,
7.1
and their respective stable series.
References
4 totalFrequently asked questions
-
What is CVE-2026-64053?
CVE-2026-64053 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.11 onward and has been patched in 6.12.92, 6.18.34, 7.0.11 and others. CVE-2026-64053 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64053?
Yes — CVE-2026-64053 has been patched. Fixed versions include 6.12.92, 6.18.34, 7.0.11 and others. If you are running Linux kernel 6.11 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64053 actively exploited?
No — CVE-2026-64053 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.