In the Linux kernel, the following vulnerability has been resolved: crypto: qat - validate RSA CRT component lengths The generic RSA key parser… (CVE-2026-64304)
A vulnerability in the Linux kernel's crypto qat driver related to RSA CRT component length validation has been resolved. The issue arises because the qat_rsa_setkey_crt() function allocates half-size DMA buffers but does not properly check if CRT components exceed this size, leading to potential out-of-bounds memory writes. The fix adds a length check to prevent writing beyond allocated buffers by falling back to a safer code path.
AI Analysis
Technical Summary
The Linux kernel's crypto qat driver had a vulnerability (CVE-2026-64304) where the RSA CRT components (p, q, dp, dq, qinv) could be larger than the half-size DMA buffers allocated by qat_rsa_setkey_crt(). The existing generic RSA key parser bounds each CRT component by the modulus size, but the qat driver copies these components into half-size buffers without verifying if the component length exceeds half the key size. This leads to an underflow in the memcpy offset calculation and causes memory corruption by writing out of bounds. The patch adds explicit length checks for each CRT component to ensure they do not exceed half the key size, causing the driver to revert to a non-CRT code path instead of corrupting memory.
Potential Impact
This vulnerability can cause memory corruption in the kernel crypto qat driver when processing RSA keys with CRT components larger than expected. Memory corruption in kernel space can lead to system instability, crashes, or potentially privilege escalation if exploited. However, no known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to add length checks for RSA CRT components in the crypto qat driver, preventing out-of-bounds writes. Users should update their Linux kernel to a version that includes this patch. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation. Patch status is not explicitly stated here; check the Linux kernel vendor advisory or source repository for the exact fixed version.
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - validate RSA CRT component lengths The generic RSA key parser… (CVE-2026-64304)
Description
A vulnerability in the Linux kernel's crypto qat driver related to RSA CRT component length validation has been resolved. The issue arises because the qat_rsa_setkey_crt() function allocates half-size DMA buffers but does not properly check if CRT components exceed this size, leading to potential out-of-bounds memory writes. The fix adds a length check to prevent writing beyond allocated buffers by falling back to a safer code path.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's crypto qat driver had a vulnerability (CVE-2026-64304) where the RSA CRT components (p, q, dp, dq, qinv) could be larger than the half-size DMA buffers allocated by qat_rsa_setkey_crt(). The existing generic RSA key parser bounds each CRT component by the modulus size, but the qat driver copies these components into half-size buffers without verifying if the component length exceeds half the key size. This leads to an underflow in the memcpy offset calculation and causes memory corruption by writing out of bounds. The patch adds explicit length checks for each CRT component to ensure they do not exceed half the key size, causing the driver to revert to a non-CRT code path instead of corrupting memory.
Potential Impact
This vulnerability can cause memory corruption in the kernel crypto qat driver when processing RSA keys with CRT components larger than expected. Memory corruption in kernel space can lead to system instability, crashes, or potentially privilege escalation if exploited. However, no known exploits are reported in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to add length checks for RSA CRT components in the crypto qat driver, preventing out-of-bounds writes. Users should update their Linux kernel to a version that includes this patch. Since this is a kernel-level vulnerability, applying the official kernel update is the recommended remediation. Patch status is not explicitly stated here; check the Linux kernel vendor advisory or source repository for the exact fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-63x3-xxqc-x6vr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64304"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f808603a
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:37:44 UTC
Last updated: 07/26/2026, 03:58:24 UTC
Views: 4
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.