Bug 2516858 (CVE-2026-74403) - CVE-2026-74403 kernel: crypto: ccp - Check for page allocation failure correctly in TIO
Summary: CVE-2026-74403 kernel: crypto: ccp - Check for page allocation failure correc...
Keywords:
Status: NEW
Alias: CVE-2026-74403
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-15 06:37 UTC by OSIDB Bzimport
Modified: 2026-08-19 12:44 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-15 06:37:10 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.