crypto: essiv - Handle EBUSY correctly
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 69c67d451fc19d88e54f7d97e8e7c093e08357e1, Kernel 796e02cca30a67322161f0745e5ce994bbe75605, Kernel 840a1d3b77c1b062bd62b4733969a5b1efc274ce and 3 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.4, >=be1eb7f78aa8fbe34779c56c266ccd0364604e71 <69c67d451fc19d88e54f7d97e8e7c093e08357e1, >=be1eb7f78aa8fbe34779c56c266ccd0364604e71 <796e02cca30a67322161f0745e5ce994bbe75605, >=be1eb7f78aa8fbe34779c56c266ccd0364604e71 <840a1d3b77c1b062bd62b4733969a5b1efc274ce, >=be1eb7f78aa8fbe34779c56c266ccd0364604e71 <a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385, >=be1eb7f78aa8fbe34779c56c266ccd0364604e71 <b5a772adf45a32c68bef28e60621f12617161556, >=be1eb7f78aa8fbe34779c56c266ccd0364604e71 <c61e7d182ee3f3f5ecf18a2964e303d49c539b52 | 69c67d451fc19d88e54f7d97e8e7c093e08357e1, 796e02cca30a67322161f0745e5ce994bbe75605, 840a1d3b77c1b062bd62b4733969a5b1efc274ce, a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385, b5a772adf45a32c68bef28e60621f12617161556, c61e7d182ee3f3f5ecf18a2964e303d49c539b52 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket