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

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

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-74403, GHSA-6wq7-xhx5-p3vw, UBUNTU-CVE-2026-74403

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74403 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-74403 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74403/ (Markdown: https://insights.sbomify.com/CVE-2026-74403/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74403
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74403
- OSV: https://osv.dev/vulnerability/CVE-2026-74403

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74403/
Summaries are generated and may contain mistakes; the official description above is the record.