crypto: essiv - Handle EBUSY correctly
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From be1eb7f78aa8fbe34779c56c266ccd0364604e71 · fixed in c61e7d182ee3f3f5ecf18a2964e303d49c539b52; From be1eb7f78aa8fbe34779c56c266ccd0364604e71 · fixed in 796e02cca30a67322161f0745e5ce994bbe75605; From be1eb7f78aa8fbe34779c56c266ccd0364604e71 · fixed in 840a1d3b77c1b062bd62b4733969a5b1efc274ce; From be1eb7f78aa8fbe34779c56c266ccd0364604e71 · fixed in a006aa3eedb8bfd6fe317c3cfe9c86ffe76b2385; From be1eb7f78aa8fbe34779c56c266ccd0364604e71 · fixed in 69c67d451fc19d88e54f7d97e8e7c093e08357e1; From be1eb7f78aa8fbe34779c56c266ccd0364604e71 · fixed in b5a772adf45a32c68bef28e60621f12617161556
- Linux Linux
5.4
- KernelLinux
From 5.4.0 · fixed in 5.4.235; From 5.5.0 · fixed in 5.10.173; From 5.11.0 · fixed in 5.15.99; From 5.16.0 · fixed in 6.1.16; From 6.2.0 · fixed in 6.2.3