CVE-2025-40182

published 12 Nov 2025 · updated 5 Aug 2026

crypto: skcipher - Fix reqsize handling

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 229c586b5e86979badb7cb0d38717b88a9e95ddd and Kernel f041339d6b9a5a46437f0c48fc7279c92af7a513.

In the Linux kernel, the following vulnerability has been resolved: crypto: skcipher - Fix reqsize handling Commit afddce13ce81d ("crypto: api - Add reqsize to crypto_alg") introduced cra_reqsize field in crypto_alg struct to replace type specific reqsize fields. It looks like this was introduced specifically for ahash and acomp from the commit description as subsequent commits add necessary changes in these alg frameworks. However, this is being recommended for use in all crypto algs [1] instead of setting reqsize using crypto_*_set_reqsize(). Using cra_reqsize in skcipher algorithms, hence, causes memory corruptions and crashes as the underlying functions in the algorithm framework have not been updated to set the reqsize properly from cra_reqsize. [2] Add proper set_reqsize calls in the skcipher init function to properly initialize reqsize for these algorithms in the framework. [1]: https://lore.kernel.org/linux-crypto/aCL8BxpHr5OpT04k@gondor.apana.org.au/ [2]: https://gist.github.com/Pratham-T/24247446f1faf4b7843e4014d5089f6b

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.16, >=afddce13ce81d52a13898fa0700917835c71acd6 <229c586b5e86979badb7cb0d38717b88a9e95ddd, >=afddce13ce81d52a13898fa0700917835c71acd6 <f041339d6b9a5a46437f0c48fc7279c92af7a513229c586b5e86979badb7cb0d38717b88a9e95ddd, f041339d6b9a5a46437f0c48fc7279c92af7a513

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-40182 severity on Zeptric[![CVE-2025-40182](https://zeptric.io/badge/cve/CVE-2025-40182.svg)](https://zeptric.io/cve/CVE-2025-40182)