crypto: ccp - Check for page allocation failure correctly in TIO
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 17e1aae19a06d9f6da4b46d54fa2aeab77ec0c69 and Kernel a8d5370eef00eca132a292b1901c9914c817e385.
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes: > if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it > safe to pass it directly to page_address()? > > On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might > compute a deterministic but invalid, non-zero virtual address. The > subsequent if (tio_status) check would then evaluate to true, and > sev_tsm_init_locked() would dereference the invalid pointer. Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by checking the page allocation itself for NULL, not the resulting virtual address.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.19, >=4be423572da1f4c11f45168e3fafda870ddac9f8 <17e1aae19a06d9f6da4b46d54fa2aeab77ec0c69, >=4be423572da1f4c11f45168e3fafda870ddac9f8 <a8d5370eef00eca132a292b1901c9914c817e385 | 17e1aae19a06d9f6da4b46d54fa2aeab77ec0c69, a8d5370eef00eca132a292b1901c9914c817e385 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket