CVE-2023-53373
crypto: seqiv - 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
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: seqiv - Handle EBUSY correctly As it is seqiv 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 seqiv 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
Version range not reported
- Linux Linux
2.6.25
References 8
git.kernel.org
- stable/c/cc4d0d4251748a8a68026938f4055d2ac47c5719
- stable/c/1effbddaff60eeef8017c6dea1ee0ed970164d14
- stable/c/63551e4b7cbcd9914258827699eb2cb6ed6e4a16
- stable/c/ae849d2f48019ff9c104e32bf588ccbfb200e971
- stable/c/36ec108b7bd7e280edb22de028467bd09d644620
- stable/c/4d497e8b200a175094e0ac252ed878add39b8771
- stable/c/9477db935eb690f697d9bcc4f608927841bc8b36
- stable/c/32e62025e5e52fbe4812ef044759de7010b15dbc