In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes:… (CVE-2026-74403)
A vulnerability in the Linux kernel's crypto CCP component involved improper checking of page allocation failure in TIO. Specifically, the function __snp_alloc_firmware_pages() could return NULL under memory pressure, but the code incorrectly passed this NULL pointer to page_address(), which on some architectures returns a non-NULL invalid address. This led to a potential dereference of an invalid pointer in sev_tsm_init_locked(). The issue has been resolved by correctly checking the page allocation for NULL before using the pointer.
AI Analysis
Technical Summary
The Linux kernel crypto CCP component had a flaw where the failure of page allocation was not correctly checked. The function __snp_alloc_firmware_pages() might return NULL when memory is low, but the code passed this NULL directly to page_address(). On architectures lacking HASHED_PAGE_VIRTUAL, page_address(NULL) returns a deterministic but invalid non-zero virtual address, causing subsequent conditional checks to incorrectly pass and leading to dereferencing an invalid pointer in sev_tsm_init_locked(). The fix involves verifying the page allocation pointer itself for NULL rather than the virtual address returned by page_address().
Potential Impact
This vulnerability could lead to dereferencing an invalid pointer, which may cause kernel crashes or undefined behavior. The impact is limited to the Linux kernel's crypto CCP component under specific memory pressure conditions and certain architectures without HASHED_PAGE_VIRTUAL. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by correcting the NULL pointer check. Users should apply the official kernel updates that include this fix. Since no patch links or vendor advisories are provided here, users should monitor official Linux kernel release notes and update accordingly. Patch status is not yet confirmed in this data — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes:… (CVE-2026-74403)
Description
A vulnerability in the Linux kernel's crypto CCP component involved improper checking of page allocation failure in TIO. Specifically, the function __snp_alloc_firmware_pages() could return NULL under memory pressure, but the code incorrectly passed this NULL pointer to page_address(), which on some architectures returns a non-NULL invalid address. This led to a potential dereference of an invalid pointer in sev_tsm_init_locked(). The issue has been resolved by correctly checking the page allocation for NULL before using the pointer.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel crypto CCP component had a flaw where the failure of page allocation was not correctly checked. The function __snp_alloc_firmware_pages() might return NULL when memory is low, but the code passed this NULL directly to page_address(). On architectures lacking HASHED_PAGE_VIRTUAL, page_address(NULL) returns a deterministic but invalid non-zero virtual address, causing subsequent conditional checks to incorrectly pass and leading to dereferencing an invalid pointer in sev_tsm_init_locked(). The fix involves verifying the page allocation pointer itself for NULL rather than the virtual address returned by page_address().
Potential Impact
This vulnerability could lead to dereferencing an invalid pointer, which may cause kernel crashes or undefined behavior. The impact is limited to the Linux kernel's crypto CCP component under specific memory pressure conditions and certain architectures without HASHED_PAGE_VIRTUAL. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by correcting the NULL pointer check. Users should apply the official kernel updates that include this fix. Since no patch links or vendor advisories are provided here, users should monitor official Linux kernel release notes and update accordingly. Patch status is not yet confirmed in this data — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6wq7-xhx5-p3vw
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74403"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b69bf8831d5394f5cd3
Added to database: 08/15/2026, 15:53:13 UTC
Last enriched: 08/15/2026, 16:02:04 UTC
Last updated: 08/15/2026, 16:02:04 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.