crypto: mxs-dcp - Ensure payload is zero when using key slot
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel dd52b5eeb0f70893f762da7254e923fd23fd1379 and Kernel e1640fed0377bf7276efb70d03cb821a6931063d.
In the Linux kernel, the following vulnerability has been resolved: crypto: mxs-dcp - Ensure payload is zero when using key slot We could leak stack memory through the payload field when running AES with a key from one of the hardware's key slots. Fix this by ensuring the payload field is set to 0 in such cases. This does not affect the common use case when the key is supplied from main memory via the descriptor payload.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.10, >=3d16af0b4cfac4b2c3b238e2ec37b38c2f316978 <dd52b5eeb0f70893f762da7254e923fd23fd1379, >=3d16af0b4cfac4b2c3b238e2ec37b38c2f316978 <e1640fed0377bf7276efb70d03cb821a6931063d | dd52b5eeb0f70893f762da7254e923fd23fd1379, e1640fed0377bf7276efb70d03cb821a6931063d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket