linux-kernel - [PATCH] uio: reset file private

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <HK2PR06MB3554789EC96D408ADDDC82F8E3D19@HK2PR06MB3554.apcprd06.prod.outlook.com>
Date:   Wed, 18 May 2022 04:16:40 +0000
From:   王文虎 <wenhu.wang@...o.com>
To:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [PATCH] uio: reset file private_data pointer after kfree

From: Wang Wenhu mailto:wenhu.wang@...o.com

The pointer private_date should be reset to null after the memory
it pointed to, which was alloced for uio_listener instance, was freed.

Signed-off-by: Wang Wenhu <wenhu.wang@...o.com>
---
 drivers/uio/uio.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index 43afbb7c5ab9..1595a6eb352b 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -505,6 +505,7 @@ static int uio_open(struct inode *inode, struct file *filep)
        return 0;

 err_infoopen:
+       filep->private_data = NULL;
        kfree(listener);

 err_alloc_listener:
@@ -536,6 +537,7 @@ static int uio_release(struct inode *inode, struct file *filep)
                ret = idev->info->release(idev->info, inode);
        mutex_unlock(&idev->info_lock);

+       filep->private_data = NULL;
        module_put(idev->owner);
        kfree(listener);
        put_device(&idev->dev);
--
2.25.1

________________________________

本邮件及其附件内容可能含有机密和/或隐私信息，仅供指定个人或机构使用。若您非发件人指定收件人或其代理人，请勿使用、传播、复制或存储此邮件之任何内容或其附件。如您误收本邮件，请即以回复或电话方式通知发件人，并将原始邮件、附件及其所有复本删除。谢谢。
The contents of this message and any attachments may contain confidential and/or privileged information and are intended exclusively for the addressee(s). If you are not the intended recipient of this message or their agent, please note that any use, dissemination, copying, or storage of this message or its attachments is not allowed. If you receive this message in error, please notify the sender by reply the message or phone and delete this message, any attachments and any copies immediately.
Thank you