block: don't overwrite bip_vcnt in bio_integrity_copy_user()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d18160c9525c63c203656fefd847e94b538cd4a4, Kernel 066be1439593a381b1a29663becfcfe0c92363e7, Kernel 0d48654af4d1390c888389206cc13b51b82c30e6 and 4 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3991657ae7074c3c497bf095093178bed37ea1b4 <d18160c9525c63c203656fefd847e94b538cd4a4, >=3991657ae7074c3c497bf095093178bed37ea1b4 <066be1439593a381b1a29663becfcfe0c92363e7, >=3991657ae7074c3c497bf095093178bed37ea1b4 <0d48654af4d1390c888389206cc13b51b82c30e6, >=3991657ae7074c3c497bf095093178bed37ea1b4 <637ad3a56a3b889527d1dacea6fea2a8bd648140, =6.11 | d18160c9525c63c203656fefd847e94b538cd4a4, 066be1439593a381b1a29663becfcfe0c92363e7, 0d48654af4d1390c888389206cc13b51b82c30e6, 637ad3a56a3b889527d1dacea6fea2a8bd648140 |
| linux-kernel: Kernel | >=6.13.0 <6.18.34, >=6.19.0 <7.0.11, >=6.11.0 <6.12.92 | 6.18.34, 7.0.11, 6.12.92 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket