crypto: authencesn - reject short ahash digests during instance creation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f15f05b0a5de667c821a9727c33bce9d1d9b26dd · < b42821c15445f93daea3e76ada682b2b7181c476| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: authencesn - reject short ahash digests during instance creation
authencesn requires either a zero authsize or an authsize of at least 4 bytes because the ESN encrypt/decrypt paths always move 4 bytes of high-order sequence number data at the end of the authenticated data.
While crypto_authenc_esn_setauthsize() already rejects explicit non-zero authsizes in the range 1..3, crypto_authenc_esn_create() still copied auth->digestsize into inst->alg.maxauthsize without validating it. The AEAD core then initialized the tfm's default authsize from that value.
As a result, selecting an ahash with digest size 1..3, such as cbcmac(cipher_null), exposed authencesn instances whose default authsize was invalid even though setauthsize() would have rejected the same value. AF_ALG could then trigger the ESN tail handling with a too-short tag and hit an out-of-bounds access.
Reject authencesn instances whose ahash digest size is in the invalid non-zero range 1..3 so that no tfm can inherit an unsupported default authsize.
From the CVE record · Linux
The Linux kernel's authencesn component can create instances with an invalid default authentication size when an ahash digest is 1–3 bytes. A local attacker could use AF_ALG to trigger an out-of-bounds access with a too-short tag; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with authencesn should check their exposure; affected versions are not specified.