diff options
| author | tim <tim.c.chen@linux.intel.com> | 2016-12-05 11:46:31 -0800 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2016-12-07 19:55:37 +0800 |
| commit | 48a992727d82cb7db076fa15d372178743b1f4cd (patch) | |
| tree | 2cc24a02c43a2d4d6382916f4614b118b82d27b4 /net/sched/sch_pie.c | |
| parent | 0c1e16cd1ec41987cc6671a2bff46ac958c41eb5 (diff) | |
crypto: mcryptd - Check mcryptd algorithm compatibility
Algorithms not compatible with mcryptd could be spawned by mcryptd
with a direct crypto_alloc_tfm invocation using a "mcryptd(alg)" name
construct. This causes mcryptd to crash the kernel if an arbitrary
"alg" is incompatible and not intended to be used with mcryptd. It is
an issue if AF_ALG tries to spawn mcryptd(alg) to expose it externally.
But such algorithms must be used internally and not be exposed.
We added a check to enforce that only internal algorithms are allowed
with mcryptd at the time mcryptd is spawning an algorithm.
Link: http://marc.info/?l=linux-crypto-vger&m=148063683310477&w=2
Cc: stable@vger.kernel.org
Reported-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'net/sched/sch_pie.c')
0 files changed, 0 insertions, 0 deletions