summaryrefslogtreecommitdiff
path: root/crypto/algif_aead.c
diff options
context:
space:
mode:
authortim <tim.c.chen@linux.intel.com>2016-12-05 11:46:31 -0800
committerHerbert Xu <herbert@gondor.apana.org.au>2016-12-07 19:55:37 +0800
commitd4d21b6e0520cdfa428e805d452776a62f1b3a37 (patch)
treee81940616f0c02ddb710475e0851df7e03b6026d /crypto/algif_aead.c
parente5c8b106ce5fd2ad7b8e735dff452844c03a5f49 (diff)
downloadlinux-crypto-d4d21b6e0520cdfa428e805d452776a62f1b3a37.tar.gz
linux-crypto-d4d21b6e0520cdfa428e805d452776a62f1b3a37.zip
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 'crypto/algif_aead.c')
0 files changed, 0 insertions, 0 deletions