CVE-2026-74403 crypto: ccp - Check for page allocation failure correctly in TIO

High 7.8 Published Updated

A missing null check in the Linux kernel's CCP driver can lead to a kernel crash when memory allocation fails during TIO initialization.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-74403?

CVE-2026-74403 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Which versions are affected by CVE-2026-74403?

How do I fix CVE-2026-74403?

Apply the vendor's patch.

Is CVE-2026-74403 being exploited?

There is no known exploitation of CVE-2026-74403 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2026-74403, GHSA-6wq7-xhx5-p3vw, UBUNTU-CVE-2026-74403.

Is CVE-2026-74403 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free