Description
In the Linux kernel, the following vulnerability has been resolved: crypto: essiv - Handle EBUSY correctly As it is essiv 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 essiv 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.
References6
- git.kernel.org/stable/c/69c67d451fc19d88e54f7d97e8e7c093e08357e1
- git.kernel.org/stable/c/796e02cca30a67322161f0745e5ce994bbe75605
- git.kernel.org/stable/c/840a1d3b77c1b062bd62b4733969a5b1efc274ce
- git.kernel.org/stable/c/a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385
- git.kernel.org/stable/c/b5a772adf45a32c68bef28e60621f12617161556
- git.kernel.org/stable/c/c61e7d182ee3f3f5ecf18a2964e303d49c539b52
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 9 · as of 11 November 2026
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.