crypto: seqiv - Handle EBUSY correctly

jira LE-4559
cve CVE-2023-53373
Rebuild_History Non-Buildable kernel-4.18.0-553.80.1.el8_10
commit-author Herbert Xu <[email protected]>
commit 32e6202

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.

Fixes: 0a27032 ("[CRYPTO] seqiv: Add Sequence Number IV Generator")
	Signed-off-by: Herbert Xu <[email protected]>
(cherry picked from commit 32e6202)
	Signed-off-by: Jonathan Maple <[email protected]>

Author: PlaidCat

crypto/seqiv.c

@@ -30,7 +30,7 @@ static void seqiv_aead_encrypt_complete2(struct aead_request *req, int err)
 	struct aead_request *subreq = aead_request_ctx(req);
 	struct crypto_aead *geniv;
 
-	if (err == -EINPROGRESS)
+	if (err == -EINPROGRESS || err == -EBUSY)
 		return;
 
 	if (err)