crypto: af_alg - zero initialize memory allocated via sock_kmalloc
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fe869cdb89c95d060c77eea20204d6c91f233b53 · < 51a5ab36084f3251ef87eda3e6a6236f6488925e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: af_alg - zero initialize memory allocated via sock_kmalloc
Several crypto user API contexts and requests allocated with sock_kmalloc() were left uninitialized, relying on callers to set fields explicitly. This resulted in the use of uninitialized data in certain error paths or when new fields are added in the future.
The ACVP patches also contain two user-space interface files: algif_kpp.c and algif_akcipher.c. These too rely on proper initialization of their context structures.
A particular issue has been observed with the newly added 'inflight' variable introduced in af_alg_ctx by commit:
67b164a871af ("crypto: af_alg - Disallow multiple in-flight AIO requests")
Because the context is not memset to zero after allocation, the inflight variable has contained garbage values. As a result, af_alg_alloc_areq() has incorrectly returned -EBUSY randomly when the garbage value was interpreted as true:
https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209
From the CVE record · Linux
Crypto user API contexts allocated by sock_kmalloc() may contain uninitialized data. A local user making crypto API requests can encounter unexpected -EBUSY failures when an uninitialized inflight value is treated as true; the input does not establish an authentication requirement.
Engineers running Linux kernels with the affected crypto af_alg code should check their deployments; affected versions were not specified.