Description
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.
Product status
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before cc4d0d4251748a8a68026938f4055d2ac47c5719
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before 1effbddaff60eeef8017c6dea1ee0ed970164d14
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before 63551e4b7cbcd9914258827699eb2cb6ed6e4a16
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before ae849d2f48019ff9c104e32bf588ccbfb200e971
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before 36ec108b7bd7e280edb22de028467bd09d644620
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before 4d497e8b200a175094e0ac252ed878add39b8771
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before 9477db935eb690f697d9bcc4f608927841bc8b36
0a270321dbf948963aeb0e8382fe17d2c2eb3771 (git) before 32e62025e5e52fbe4812ef044759de7010b15dbc
2.6.25
Any version before 2.6.25
4.14.308 (semver)
4.19.276 (semver)
5.4.235 (semver)
5.10.173 (semver)
5.15.99 (semver)
6.1.16 (semver)
6.2.3 (semver)
6.3 (original_commit_for_fix)
References
git.kernel.org/...c/cc4d0d4251748a8a68026938f4055d2ac47c5719
git.kernel.org/...c/1effbddaff60eeef8017c6dea1ee0ed970164d14
git.kernel.org/...c/63551e4b7cbcd9914258827699eb2cb6ed6e4a16
git.kernel.org/...c/ae849d2f48019ff9c104e32bf588ccbfb200e971
git.kernel.org/...c/36ec108b7bd7e280edb22de028467bd09d644620
git.kernel.org/...c/4d497e8b200a175094e0ac252ed878add39b8771
git.kernel.org/...c/9477db935eb690f697d9bcc4f608927841bc8b36
git.kernel.org/...c/32e62025e5e52fbe4812ef044759de7010b15dbc
