Description
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: linux kernel
References5
- git.kernel.org/stable/c/51c082514c2dedf2711c99d93c196cc4eedceb40 Patch
- git.kernel.org/stable/c/57c3e1d63b63dc0841d41df729297cd7c1c35808 Patch
- git.kernel.org/stable/c/912eb10b65646ffd222256c78a1c566a3dac177d Patch
- git.kernel.org/stable/c/92a07ba4f0af2cccdc2aa5ee32679c9c9714db90 Patch
- git.kernel.org/stable/c/d5870848879291700fe6c5257dcb48aadd10425c Patch
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 6 · as of 9 November 2026
- CWE
- CWE-416
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.