* Re: [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
@ 2020-03-13 6:31 Zhao, XinfengX
0 siblings, 0 replies; 5+ messages in thread
From: Zhao, XinfengX @ 2020-03-13 6:31 UTC (permalink / raw)
To: dev; +Cc: Dybkowski, AdamX
Tested-by: Zhao, Xinfeng<xinfengx.zhao@intel.com<mailto:xinfengx.zhao@intel.com>>
> -----Original Message-----
> From: Dybkowski, AdamX <adamx.dybkowski at intel.com<https://mails.dpdk.org/listinfo/dev>>
> Sent: Thursday, February 20, 2020 3:04 PM
> To: dev at dpdk.org<https://mails.dpdk.org/listinfo/dev>; Trahe, Fiona <fiona.trahe at intel.com<https://mails.dpdk.org/listinfo/dev>>; akhil.goyal at nxp.com<https://mails.dpdk.org/listinfo/dev>
> Cc: Dybkowski, AdamX <adamx.dybkowski at intel.com<https://mails.dpdk.org/listinfo/dev>>; stable at dpdk.org<https://mails.dpdk.org/listinfo/dev>
> Subject: [PATCH] cryptodev: fix missing device id range checking
>
> This patch adds range-checking of the device id passed from
> the user app code. It prevents out-of-range array accesses
> which in some situations resulted in an
> application crash (segfault).
>
> Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id")
> Cc: stable at dpdk.org<https://mails.dpdk.org/listinfo/dev>
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski at intel.com<https://mails.dpdk.org/listinfo/dev>>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
2020-03-13 7:19 ` Akhil Goyal
@ 2020-03-25 19:11 ` Akhil Goyal
0 siblings, 0 replies; 5+ messages in thread
From: Akhil Goyal @ 2020-03-25 19:11 UTC (permalink / raw)
To: Akhil Goyal, Adam Dybkowski, dev, fiona.trahe; +Cc: stable
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Akhil Goyal
> Sent: Friday, March 13, 2020 12:50 PM
> To: Adam Dybkowski <adamx.dybkowski@intel.com>; dev@dpdk.org;
> fiona.trahe@intel.com
> Cc: stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
>
> > Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> > ---
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied to dpdk-next-crypto
Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
2020-02-20 15:04 Adam Dybkowski
2020-02-20 15:39 ` Trahe, Fiona
@ 2020-03-13 7:19 ` Akhil Goyal
2020-03-25 19:11 ` Akhil Goyal
1 sibling, 1 reply; 5+ messages in thread
From: Akhil Goyal @ 2020-03-13 7:19 UTC (permalink / raw)
To: Adam Dybkowski, dev, fiona.trahe; +Cc: stable
> Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id")
> Cc: stable@dpdk.org
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> ---
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
2020-02-20 15:04 Adam Dybkowski
@ 2020-02-20 15:39 ` Trahe, Fiona
2020-03-13 7:19 ` Akhil Goyal
1 sibling, 0 replies; 5+ messages in thread
From: Trahe, Fiona @ 2020-02-20 15:39 UTC (permalink / raw)
To: Dybkowski, AdamX, dev, akhil.goyal; +Cc: stable, julien.meunier, Trahe, Fiona
> -----Original Message-----
> From: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Sent: Thursday, February 20, 2020 3:04 PM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com
> Cc: Dybkowski, AdamX <adamx.dybkowski@intel.com>; stable@dpdk.org
> Subject: [PATCH] cryptodev: fix missing device id range checking
>
> This patch adds range-checking of the device id passed from
> the user app code. It prevents out-of-range array accesses
> which in some situations resulted in an
> application crash (segfault).
>
> Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id")
> Cc: stable@dpdk.org
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking
@ 2020-02-20 15:04 Adam Dybkowski
2020-02-20 15:39 ` Trahe, Fiona
2020-03-13 7:19 ` Akhil Goyal
0 siblings, 2 replies; 5+ messages in thread
From: Adam Dybkowski @ 2020-02-20 15:04 UTC (permalink / raw)
To: dev, fiona.trahe, akhil.goyal; +Cc: Adam Dybkowski, stable
This patch adds range-checking of the device id passed from
the user app code. It prevents out-of-range array accesses
which in some situations resulted in an
application crash (segfault).
Fixes: 3dd4435cf473 ("cryptodev: fix checks related to device id")
Cc: stable@dpdk.org
Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
---
lib/librte_cryptodev/rte_cryptodev.c | 41 +++++++++++++++++++++++++---
1 file changed, 37 insertions(+), 4 deletions(-)
diff --git a/lib/librte_cryptodev/rte_cryptodev.c b/lib/librte_cryptodev/rte_cryptodev.c
index 6d1d0e9d3..65d61a3ef 100644
--- a/lib/librte_cryptodev/rte_cryptodev.c
+++ b/lib/librte_cryptodev/rte_cryptodev.c
@@ -529,7 +529,8 @@ rte_cryptodev_pmd_get_named_dev(const char *name)
static inline uint8_t
rte_cryptodev_is_valid_device_data(uint8_t dev_id)
{
- if (rte_crypto_devices[dev_id].data == NULL)
+ if (dev_id >= RTE_CRYPTO_MAX_DEVS ||
+ rte_crypto_devices[dev_id].data == NULL)
return 0;
return 1;
@@ -621,8 +622,9 @@ rte_cryptodev_devices_get(const char *driver_name, uint8_t *devices,
void *
rte_cryptodev_get_sec_ctx(uint8_t dev_id)
{
- if (rte_crypto_devices[dev_id].feature_flags &
- RTE_CRYPTODEV_FF_SECURITY)
+ if (dev_id < RTE_CRYPTO_MAX_DEVS &&
+ (rte_crypto_devices[dev_id].feature_flags &
+ RTE_CRYPTODEV_FF_SECURITY))
return rte_crypto_devices[dev_id].security_ctx;
return NULL;
@@ -793,6 +795,11 @@ rte_cryptodev_queue_pair_count(uint8_t dev_id)
{
struct rte_cryptodev *dev;
+ if (!rte_cryptodev_is_valid_device_data(dev_id)) {
+ CDEV_LOG_ERR("Invalid dev_id=%" PRIu8, dev_id);
+ return 0;
+ }
+
dev = &rte_crypto_devices[dev_id];
return dev->data->nb_queue_pairs;
}
@@ -1258,6 +1265,11 @@ rte_cryptodev_sym_session_init(uint8_t dev_id,
uint8_t index;
int ret;
+ if (!rte_cryptodev_pmd_is_valid_dev(dev_id)) {
+ CDEV_LOG_ERR("Invalid dev_id=%" PRIu8, dev_id);
+ return -EINVAL;
+ }
+
dev = rte_cryptodev_pmd_get_dev(dev_id);
if (sess == NULL || xforms == NULL || dev == NULL)
@@ -1297,6 +1309,11 @@ rte_cryptodev_asym_session_init(uint8_t dev_id,
uint8_t index;
int ret;
+ if (!rte_cryptodev_pmd_is_valid_dev(dev_id)) {
+ CDEV_LOG_ERR("Invalid dev_id=%" PRIu8, dev_id);
+ return -EINVAL;
+ }
+
dev = rte_cryptodev_pmd_get_dev(dev_id);
if (sess == NULL || xforms == NULL || dev == NULL)
@@ -1432,6 +1449,11 @@ rte_cryptodev_sym_session_clear(uint8_t dev_id,
struct rte_cryptodev *dev;
uint8_t driver_id;
+ if (!rte_cryptodev_pmd_is_valid_dev(dev_id)) {
+ CDEV_LOG_ERR("Invalid dev_id=%" PRIu8, dev_id);
+ return -EINVAL;
+ }
+
dev = rte_cryptodev_pmd_get_dev(dev_id);
if (dev == NULL || sess == NULL)
@@ -1456,6 +1478,11 @@ rte_cryptodev_asym_session_clear(uint8_t dev_id,
{
struct rte_cryptodev *dev;
+ if (!rte_cryptodev_pmd_is_valid_dev(dev_id)) {
+ CDEV_LOG_ERR("Invalid dev_id=%" PRIu8, dev_id);
+ return -EINVAL;
+ }
+
dev = rte_cryptodev_pmd_get_dev(dev_id);
if (dev == NULL || sess == NULL)
@@ -1789,8 +1816,14 @@ rte_cryptodev_driver_id_get(const char *name)
const char *
rte_cryptodev_name_get(uint8_t dev_id)
{
- struct rte_cryptodev *dev = rte_cryptodev_pmd_get_dev(dev_id);
+ struct rte_cryptodev *dev;
+ if (!rte_cryptodev_is_valid_device_data(dev_id)) {
+ CDEV_LOG_ERR("Invalid dev_id=%" PRIu8, dev_id);
+ return NULL;
+ }
+
+ dev = rte_cryptodev_pmd_get_dev(dev_id);
if (dev == NULL)
return NULL;
--
2.17.1
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-03-25 19:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-13 6:31 [dpdk-dev] [PATCH] cryptodev: fix missing device id range checking Zhao, XinfengX
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 15:04 Adam Dybkowski
2020-02-20 15:39 ` Trahe, Fiona
2020-03-13 7:19 ` Akhil Goyal
2020-03-25 19:11 ` Akhil Goyal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).