lkml.org 
[lkml]   [2020]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 4.4 005/113] ecryptfs: fix a memory leak bug in ecryptfs_init_messaging()
    Date
    From: Wenwen Wang <wenwen@cs.uga.edu>

    commit b4a81b87a4cfe2bb26a4a943b748d96a43ef20e8 upstream.

    In ecryptfs_init_messaging(), if the allocation for 'ecryptfs_msg_ctx_arr'
    fails, the previously allocated 'ecryptfs_daemon_hash' is not deallocated,
    leading to a memory leak bug. To fix this issue, free
    'ecryptfs_daemon_hash' before returning the error.

    Cc: stable@vger.kernel.org
    Fixes: 88b4a07e6610 ("[PATCH] eCryptfs: Public key transport mechanism")
    Signed-off-by: Wenwen Wang <wenwen@cs.uga.edu>
    Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    fs/ecryptfs/messaging.c | 1 +
    1 file changed, 1 insertion(+)

    --- a/fs/ecryptfs/messaging.c
    +++ b/fs/ecryptfs/messaging.c
    @@ -397,6 +397,7 @@ int __init ecryptfs_init_messaging(void)
    * ecryptfs_message_buf_len),
    GFP_KERNEL);
    if (!ecryptfs_msg_ctx_arr) {
    + kfree(ecryptfs_daemon_hash);
    rc = -ENOMEM;
    printk(KERN_ERR "%s: Failed to allocate memory\n", __func__);
    goto out;

    \
     
     \ /
      Last update: 2020-02-27 14:40    [W:3.201 / U:0.056 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site