crypto: xts - Handle EBUSY correctly
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.1%
exploitation probability
0.1%top 95% of all CVEs
observed exploitation
nono source reports it
In the Linux kernel, the following vulnerability has been resolved:
crypto: xts - Handle EBUSY correctly
As it is xts only handles the special return value of EINPROGRESS,
which means that in all other cases it will free data related to the
request.
However, as the caller of xts 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.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/51c082514c2dedf2711c99d93c196cc4eedceb40https://git.kernel.org/stable/c/57c3e1d63b63dc0841d41df729297cd7c1c35808https://git.kernel.org/stable/c/912eb10b65646ffd222256c78a1c566a3dac177dhttps://git.kernel.org/stable/c/92a07ba4f0af2cccdc2aa5ee32679c9c9714db90https://git.kernel.org/stable/c/d5870848879291700fe6c5257dcb48aadd10425c