All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>, stable@dpdk.org
Subject: [PATCH 5/5] crypto/cnxk: use timing-safe digest comparison
Date: Thu, 25 Jun 2026 08:56:38 -0700	[thread overview]
Message-ID: <20260625160200.24170-6-stephen@networkplumber.org> (raw)
In-Reply-To: <20260625160200.24170-1-stephen@networkplumber.org>

compl_auth_verify() compared the generated and received MAC with
memcmp(), which returns early on the first differing byte and leaks
the number of matching leading bytes through timing.

Use rte_memeq_timingsafe() for the verify comparison.

Bugzilla ID: 1773
Fixes: 786963fdcf3e ("crypto/cnxk: add digest support")
Cc: stable@dpdk.org

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 drivers/crypto/cnxk/cnxk_se.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/cnxk/cnxk_se.h b/drivers/crypto/cnxk/cnxk_se.h
index 8dbf3e73c7..d2306a9daf 100644
--- a/drivers/crypto/cnxk/cnxk_se.h
+++ b/drivers/crypto/cnxk/cnxk_se.h
@@ -3282,7 +3282,7 @@ compl_auth_verify(struct rte_crypto_op *op, uint8_t *gen_mac, uint64_t mac_len)
 		return;
 	}
 
-	if (memcmp(mac, gen_mac, mac_len))
+	if (!rte_memeq_timingsafe(mac, gen_mac, mac_len))
 		op->status = RTE_CRYPTO_OP_STATUS_AUTH_FAILED;
 	else
 		op->status = RTE_CRYPTO_OP_STATUS_SUCCESS;
-- 
2.53.0


  parent reply	other threads:[~2026-06-25 16:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 15:56 [PATCH 0/5] crypto: use timing-safe digest comparison Stephen Hemminger
2026-06-25 15:56 ` [PATCH 1/5] eal: take experimental flag off of rte_memeq_timingsafe Stephen Hemminger
2026-06-25 15:56 ` [PATCH 2/5] crypto/uadk: use timing-safe digest comparison Stephen Hemminger
2026-06-25 15:56 ` [PATCH 3/5] crypto/ccp: " Stephen Hemminger
2026-06-25 15:56 ` [PATCH 4/5] crypto/armv8: " Stephen Hemminger
2026-06-26 17:11   ` Jack Bond-Preston
2026-06-25 15:56 ` Stephen Hemminger [this message]
2026-06-29  6:42   ` [EXTERNAL] [PATCH 5/5] crypto/cnxk: " Tejasree Kondoj
2026-06-29  7:38 ` [EXTERNAL] [PATCH 0/5] crypto: " Akhil Goyal
2026-06-29 18:59 ` [PATCH v2 0/6] " Stephen Hemminger
2026-06-29 18:59   ` [PATCH v2 1/6] eal: take experimental flag off of rte_memeq_timingsafe Stephen Hemminger
2026-06-29 18:59   ` [PATCH v2 2/6] crypto/uadk: use timing-safe digest comparison Stephen Hemminger
2026-06-29 18:59   ` [PATCH v2 3/6] crypto/ccp: " Stephen Hemminger
2026-06-29 18:59   ` [PATCH v2 4/6] crypto/armv8: " Stephen Hemminger
2026-06-29 18:59   ` [PATCH v2 5/6] crypto/cnxk: " Stephen Hemminger
2026-06-29 18:59   ` [PATCH v2 6/6] crypto/octeontx: use timing-safe RSA signature verification Stephen Hemminger
2026-06-30  9:50     ` [EXTERNAL] " Tejasree Kondoj
2026-06-30 17:22   ` [PATCH v2 0/6] crypto: use timing-safe digest comparison Morten Brørup

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=20260625160200.24170-6-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.