CVE-2026-74403

Source
https://cve.org/CVERecord?id=CVE-2026-74403
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74403.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-74403
Downstream
Published
2026-08-15T05:59:13Z
Modified
2026-08-18T03:56:57Z
Severity
  • 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
crypto: ccp - Check for page allocation failure correctly in TIO
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74403.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
4be423572da1f4c11f45168e3fafda870ddac9f8
Fixed
17e1aae19a06d9f6da4b46d54fa2aeab77ec0c69
Fixed
a8d5370eef00eca132a292b1901c9914c817e385

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74403.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.1.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74403.json"