crypto: seqiv - Handle EBUSY correctly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0a270321dbf948963aeb0e8382fe17d2c2eb3771 · < 4d497e8b200a175094e0ac252ed878add39b8771| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: seqiv - Handle EBUSY correctly
As it is seqiv only handles the special return value of EINPROGERSS, which means that in all other cases it will free data related to the request.
However, as the caller of seqiv may specify MAY_BACKLOG, we also need to expect EBUSY and treat it in the same way. Otherwise backlogged requests will trigger a use-after-free.
From the CVE record · Linux
The Linux kernel's crypto seqiv code can free request data when it receives EBUSY instead of handling it like EINPROGRESS. A caller that specifies MAY_BACKLOG can trigger a use-after-free on backlogged requests. The input does not specify network or local access, authentication requirements, or user interaction.
Engineers running the Linux kernel should check whether their version is affected; affected versions are not specified.