crypto: qat - validate RSA CRT component lengths
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - validate RSA CRT component lengths The generic RSA key parser (rsa_helper.c) bounds each CRT component (p, q, dp, dq, qinv) by the modulus size n_sz, but qat_rsa_setkey_crt() allocates half-size DMA buffers (key_sz / 2) and right-aligns each component with: memcpy(dst + half_key_sz - len, src, len) When a CRT component is larger than half_key_sz the subtraction underflows and memcpy writes past the DMA buffer, causing memory corruption. Add a len > half_key_sz check next to the existing !len check for each of the five CRT components so the driver falls back to the non-CRT path instead of writing out of bounds.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in 6d99c5fadd2df488103f64d6475b63ba6852202b; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in c34369473bfe92a0b46ec78d6358e30341c7f481; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in 1002719d13072a5e4be1e993aa61dffb4a604e82; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in 500319830d76911c120dc0b9605f8c16d7702844; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in 3d61a214fdcda41f1ebfabbb483404032a7b4d91; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in 6fb62b767f3e27661e8f8d2f7b85f4e098fcdb1a; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in ce42224487c504aee4b7ff3a7342e7b4d7e28cc9; From 879f77e9071f029e1c9bd5a75814ecf51370f846 · fixed in b3ac78756588059729b9195fcc9f4b37d54057a5
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4
References 8
git.kernel.org
- stable/c/6d99c5fadd2df488103f64d6475b63ba6852202b
- stable/c/c34369473bfe92a0b46ec78d6358e30341c7f481
- stable/c/1002719d13072a5e4be1e993aa61dffb4a604e82
- stable/c/500319830d76911c120dc0b9605f8c16d7702844
- stable/c/3d61a214fdcda41f1ebfabbb483404032a7b4d91
- stable/c/6fb62b767f3e27661e8f8d2f7b85f4e098fcdb1a
- stable/c/ce42224487c504aee4b7ff3a7342e7b4d7e28cc9
- stable/c/b3ac78756588059729b9195fcc9f4b37d54057a5