integrity: Fix memory leakage in keyring allocation error path
authorGUO Zihua <guozihua@huawei.com>
Fri, 11 Nov 2022 10:13:17 +0000 (18:13 +0800)
committerMimi Zohar <zohar@linux.ibm.com>
Wed, 16 Nov 2022 16:47:47 +0000 (11:47 -0500)
Key restriction is allocated in integrity_init_keyring(). However, if
keyring allocation failed, it is not freed, causing memory leaks.

Fixes: 2b6aa412ff23 ("KEYS: Use structure to capture key restriction function and data")
Signed-off-by: GUO Zihua <guozihua@huawei.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
security/integrity/digsig.c

index 8a82a6c7f48a44def6d1aa127b66ea8afa3d7e34..f2193c531f4a461c3fd51f6df13ae7b8d30a6337 100644 (file)
@@ -126,6 +126,7 @@ int __init integrity_init_keyring(const unsigned int id)
 {
        struct key_restriction *restriction;
        key_perm_t perm;
+       int ret;
 
        perm = (KEY_POS_ALL & ~KEY_POS_SETATTR) | KEY_USR_VIEW
                | KEY_USR_READ | KEY_USR_SEARCH;
@@ -154,7 +155,10 @@ int __init integrity_init_keyring(const unsigned int id)
                perm |= KEY_USR_WRITE;
 
 out:
-       return __integrity_init_keyring(id, perm, restriction);
+       ret = __integrity_init_keyring(id, perm, restriction);
+       if (ret)
+               kfree(restriction);
+       return ret;
 }
 
 static int __init integrity_add_key(const unsigned int id, const void *data,