From: Arbab Haider <arbabhaider649@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Arbab Haider <arbabhaider649@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
John Garry <john.g.garry@oracle.com>,
linux-crypto@vger.kernel.org
Subject: [PATCH] crypto: hisilicon/sec - Fix element drop and UAF in sec_send_request()
Date: Fri, 31 Jul 2026 02:54:48 +0500 [thread overview]
Message-ID: <20260730215449.299311-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.
Fixes: 915e4e8413da ("crypto: hisilicon - SEC security accelerator driver")
Signed-off-by: Arbab Haider <arbabhaider649@gmail.com>
---
drivers/crypto/hisilicon/sec/sec_algs.c | 65 ++++++++++++++-----------
1 file changed, 37 insertions(+), 28 deletions(-)
diff --git a/drivers/crypto/hisilicon/sec/sec_algs.c b/drivers/crypto/hisilicon/sec/sec_algs.c
index 85eecbb40e7e..ce1dd95455ff 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) {
@@ -401,21 +400,17 @@ 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;
- }
+ if (WARN_ON_ONCE(sec_queue_send(queue, &el->req,
+ sec_req)))
+ /* Should not happen with proper capacity check */
+ ;
} else {
- kfifo_put(&queue->softqueue, el);
+ if (WARN_ON_ONCE(!kfifo_put(&queue->softqueue, el)))
+ /* Should not happen with proper capacity check */
+ ;
}
}
-err_unlock:
mutex_unlock(&sec_req->lock);
-
- return ret;
}
static void sec_skcipher_alg_callback(struct sec_bd_info *sec_resp,
@@ -790,28 +785,44 @@ 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 (!queue->havesoftqueue) {
+ if (!sec_queue_can_enqueue(queue, steps))
+ ret = -EBUSY;
+ } else if (!kfifo_is_empty(&queue->softqueue) ||
+ !sec_queue_empty(queue)) {
+ /* All entries must go to the softqueue */
+ if (kfifo_avail(&queue->softqueue) <= steps)
+ ret = -EBUSY;
+ } else {
+ /* First to hardware, rest to softqueue */
+ if (!sec_queue_can_enqueue(queue, 1) ||
+ kfifo_avail(&queue->softqueue) < steps - 1)
+ 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 +832,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
next reply other threads:[~2026-07-30 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 21:54 Arbab Haider [this message]
2026-07-31 20:39 ` [PATCH] crypto: hisilicon/sec - Fix element drop and UAF in sec_send_request() kernel test robot
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=20260730215449.299311-1-arbabhaider649@gmail.com \
--to=arbabhaider649@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.g.garry@oracle.com \
--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