Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Arbab Haider <arbabhaider649@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, Arbab Haider <arbabhaider649@gmail.com>
Subject: [PATCH v3] crypto: hisilicon/sec - Fix element drop and UAF in sec_send_request()
Date: Sun,  2 Aug 2026 12:45:34 +0500	[thread overview]
Message-ID: <20260802074534.353727-1-arbabhaider649@gmail.com> (raw)

The capacity check in sec_alg_skcipher_crypto() only verified that the
hardware queue could accept all steps or that the softqueue had
capacity, but failed to account for the case where softqueue already
has pending entries. When softqueue is non-empty, all new entries must
go to softqueue (to preserve cipher chaining ordering), even if the
hardware queue has available capacity.

This means the check could pass via hardware capacity, yet the first
element goes to hardware and subsequent elements go to softqueue -
which might be full. kfifo_put() silently returns 0 on a full fifo,
so those elements are dropped and the request never completes.

Fix by:

- Replacing the capacity check with correct logic that accounts
  for all three queueing scenarios.

- Making sec_send_request() void and checking both sec_queue_send()
  and kfifo_put() with WARN_ON_ONCE. A return value is not returned
  to the caller because a mid-loop error after partial queuing would
  cause the caller's err_free_elements path to free elements still
  referenced by the hardware shadow array or softqueue (UAF). The
  corrected capacity check guarantees these paths are unreachable.

- Factoring the corrected capacity check into sec_can_send_request()
  and applying it to the backlog re-queue path in
  sec_alg_skcipher_alg_callback() as well, which previously used the
  same flawed check. If the hardware queue could accept the whole
  request but the softqueue could not hold the remaining elements,
  the re-queue would queue the first element to hardware and then
  drop the tail elements on a full softqueue, hanging the request.

Fixes: 915e4e8413da ("crypto: hisilicon - SEC security accelerator driver")
Signed-off-by: Arbab Haider <arbabhaider649@gmail.com>
---
 drivers/crypto/hisilicon/sec/sec_algs.c | 84 ++++++++++++++-----------
 1 file changed, 48 insertions(+), 36 deletions(-)

diff --git a/drivers/crypto/hisilicon/sec/sec_algs.c b/drivers/crypto/hisilicon/sec/sec_algs.c
index 85eecbb40e7e..e12206989f63 100644
--- a/drivers/crypto/hisilicon/sec/sec_algs.c
+++ b/drivers/crypto/hisilicon/sec/sec_algs.c
@@ -381,10 +381,9 @@ static void sec_alg_free_el(struct sec_request_el *el,
 }
 
 /* queuelock must be held */
-static int sec_send_request(struct sec_request *sec_req, struct sec_queue *queue)
+static void sec_send_request(struct sec_request *sec_req, struct sec_queue *queue)
 {
 	struct sec_request_el *el, *temp;
-	int ret = 0;
 
 	mutex_lock(&sec_req->lock);
 	list_for_each_entry_safe(el, temp, &sec_req->elements, head) {
@@ -400,22 +399,36 @@ static int sec_send_request(struct sec_request *sec_req, struct sec_queue *queue
 		 */
 		if (!queue->havesoftqueue ||
 		    (kfifo_is_empty(&queue->softqueue) &&
-		     sec_queue_empty(queue))) {
-			ret = sec_queue_send(queue, &el->req, sec_req);
-			if (ret == -EAGAIN) {
-				/* Wait unti we can send then try again */
-				/* DEAD if here - should not happen */
-				ret = -EBUSY;
-				goto err_unlock;
-			}
-		} else {
-			kfifo_put(&queue->softqueue, el);
-		}
+		     sec_queue_empty(queue)))
+			WARN_ON_ONCE(sec_queue_send(queue, &el->req,
+						    sec_req));
+		else
+			WARN_ON_ONCE(!kfifo_put(&queue->softqueue, el));
 	}
-err_unlock:
 	mutex_unlock(&sec_req->lock);
+}
 
-	return ret;
+/*
+ * Check whether a request of @steps elements can be queued without
+ * exceeding the capacity of the hardware and software queues.
+ *
+ * When the softqueue has pending entries, all new entries must go to
+ * the softqueue to preserve ordering.  When both queues are empty the
+ * first entry goes to hardware and the rest to the softqueue (if
+ * enabled).
+ *
+ * queuelock must be held.
+ */
+static bool sec_can_send_request(struct sec_queue *queue, unsigned int steps)
+{
+	if (!queue->havesoftqueue)
+		return sec_queue_can_enqueue(queue, steps);
+
+	if (!kfifo_is_empty(&queue->softqueue) || !sec_queue_empty(queue))
+		return kfifo_avail(&queue->softqueue) > steps;
+
+	return sec_queue_can_enqueue(queue, 1) &&
+	       kfifo_avail(&queue->softqueue) >= steps - 1;
 }
 
 static void sec_skcipher_alg_callback(struct sec_bd_info *sec_resp,
@@ -498,11 +511,8 @@ static void sec_skcipher_alg_callback(struct sec_bd_info *sec_resp,
 		backlog_req = list_first_entry(&ctx->backlog,
 					       typeof(*backlog_req),
 					       backlog_head);
-		if (sec_queue_can_enqueue(ctx->queue,
-		    backlog_req->num_elements) ||
-		    (ctx->queue->havesoftqueue &&
-		     kfifo_avail(&ctx->queue->softqueue) >
-		     backlog_req->num_elements)) {
+		if (sec_can_send_request(ctx->queue,
+					 backlog_req->num_elements)) {
 			sec_send_request(backlog_req, ctx->queue);
 			crypto_request_complete(backlog_req->req_base,
 						-EINPROGRESS);
@@ -713,7 +723,7 @@ static int sec_alg_skcipher_crypto(struct skcipher_request *skreq,
 	struct sec_queue *queue = ctx->queue;
 	struct sec_request *sec_req = skcipher_request_ctx(skreq);
 	struct sec_dev_info *info = queue->dev_info;
-	int i, ret, steps;
+	int i, ret = 0, steps;
 	size_t *split_sizes;
 	struct scatterlist **splits_in;
 	struct scatterlist **splits_out = NULL;
@@ -790,28 +800,32 @@ static int sec_alg_skcipher_crypto(struct skcipher_request *skreq,
 
 	/*
 	 * Only attempt to queue if the whole lot can fit in the queue -
-	 * we can't successfully cleanup after a partial queing so this
+	 * we can't successfully cleanup after a partial queuing so this
 	 * must succeed or fail atomically.
 	 *
-	 * Big hammer test of both software and hardware queues - could be
-	 * more refined but this is unlikely to happen so no need.
+	 * When the softqueue has pending entries, all new entries must
+	 * go to the softqueue to preserve ordering.  When both queues
+	 * are empty the first entry goes to hardware and the rest to
+	 * the softqueue (if enabled).
 	 */
 
 	/* Grab a big lock for a long time to avoid concurrency issues */
 	spin_lock_bh(&queue->queuelock);
 
 	/*
-	 * Can go on to queue if we have space in either:
-	 * 1) The hardware queue and no software queue
-	 * 2) The software queue
-	 * AND there is nothing in the backlog.  If there is backlog we
-	 * have to only queue to the backlog queue and return busy.
+	 * Can go on to queue if we have space for everything upfront.
+	 * If there is backlog we must queue to the backlog and return busy.
 	 */
-	if ((!sec_queue_can_enqueue(queue, steps) &&
-	     (!queue->havesoftqueue ||
-	      kfifo_avail(&queue->softqueue) > steps)) ||
-	    !list_empty(&ctx->backlog)) {
+	if (!list_empty(&ctx->backlog)) {
+		ret = -EBUSY;
+		goto backlog;
+	}
+
+	if (!sec_can_send_request(queue, steps))
 		ret = -EBUSY;
+
+	if (ret) {
+backlog:
 		if ((skreq->base.flags & CRYPTO_TFM_REQ_MAY_BACKLOG)) {
 			list_add_tail(&sec_req->backlog_head, &ctx->backlog);
 			spin_unlock_bh(&queue->queuelock);
@@ -821,10 +835,8 @@ static int sec_alg_skcipher_crypto(struct skcipher_request *skreq,
 		spin_unlock_bh(&queue->queuelock);
 		goto err_free_elements;
 	}
-	ret = sec_send_request(sec_req, queue);
+	sec_send_request(sec_req, queue);
 	spin_unlock_bh(&queue->queuelock);
-	if (ret)
-		goto err_free_elements;
 
 	ret = -EINPROGRESS;
 out:
-- 
2.53.0


                 reply	other threads:[~2026-08-02  7:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260802074534.353727-1-arbabhaider649@gmail.com \
    --to=arbabhaider649@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox