diff options
| author |   Colin Ian King <colin.king@canonical.com> | 2015-07-27 15:23:43 +0100 |
|---|---|---|
| committer |   James Morris <james.l.morris@oracle.com> | 2015-07-28 13:08:23 +1000 |
| commit | ca4da5dd1f99fe9c59f1709fb43e818b18ad20e0 (patch) | |
| tree | 764a71fdad83745285b7db3a8143899a284c8bf5 /net | |
| parent | Linux 4.2-rc4 (diff) | |
| download | linux-dev-ca4da5dd1f99fe9c59f1709fb43e818b18ad20e0.tar.xz linux-dev-ca4da5dd1f99fe9c59f1709fb43e818b18ad20e0.zip | |
KEYS: ensure we free the assoc array edit if edit is valid
__key_link_end is not freeing the associated array edit structure
and this leads to a 512 byte memory leak each time an identical
existing key is added with add_key().
The reason the add_key() system call returns okay is that
key_create_or_update() calls __key_link_begin() before checking to see
whether it can update a key directly rather than adding/replacing - which
it turns out it can. Thus __key_link() is not called through
__key_instantiate_and_link() and __key_link_end() must cancel the edit.
CVE-2015-1333
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: James Morris <james.l.morris@oracle.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions