crypto: seqiv - Do not use req->iv after crypto_aead_encrypt
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0a270321dbf948963aeb0e8382fe17d2c2eb3771 · < 5476f7f8a311236604b78fcc5b2a63b3a61b0169| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: seqiv - Do not use req->iv after crypto_aead_encrypt
As soon as crypto_aead_encrypt is called, the underlying request may be freed by an asynchronous completion. Thus dereferencing req->iv after it returns is invalid.
Instead of checking req->iv against info, create a new variable unaligned_info and use it for that purpose instead.
From the CVE record · Linux
The Linux kernel’s crypto seqiv code can dereference a request after an asynchronous encryption completion frees it. The input does not specify how an attacker could trigger this issue, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the affected crypto seqiv code should check their kernel versions; affected versions are not specified.