SUSE CVE-2026-64053

In the Linux kernel, the following vulnerability has been resolved: block: don't overwrite bipvcnt in biointegritycopyuser biointegrityaddpage already sets bipvcnt to 1 for the bounce segment. Overwriting it with nrvecs breaks bipvcnt = bipmaxvcnt on WRITE bipmaxvcnt is 1, so the gap-merge checks...

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

In the Linux kernel, the following vulnerability has been resolved: block: don't overwrite bipvcnt in biointegritycopyuser biointegrityaddpage already sets bipvcnt to 1 for the bounce segment. Overwriting it with nrvecs breaks bipvcnt = bipmaxvcnt on WRITE bipmaxvcnt is 1, so the gap-merge checks...

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

In the Linux kernel, the following vulnerability has been resolved: block: don't overwrite bipvcnt in biointegritycopyuser biointegrityaddpage already sets bipvcnt to 1 for the bounce segment. Overwriting it with nrvecs breaks bipvcnt = bipmaxvcnt on WRITE bipmaxvcnt is 1, so the gap-merge checks...

CVE-2026-64053

The CVE-2026-64053 issue lies in the Linux kernel block layer: bio_integrity_copy_user() overwrites bip_vcnt, and bio_integrity_add_page() already sets bip_vcnt to 1 for the bounce segment. Writing with nr_vecs can violate bip_vcnt

PT-2026-61370

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the bio integrity copy user function where the bip vcnt variable is incorrectly overwritten. Because bio integrity add page already sets bip vcnt to 1 for the bounce...