linux-kernel - Re: [PATCH] fs: sysfs: Fix reference leak in sysfs_break_active

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-prev] [day] [month] [year] [list]

Message-ID: <436fb309-1f6f-4279-8c33-121fd76a7129@acm.org>
Date: Wed, 13 Mar 2024 15:10:16 -0700
From: Bart Van Assche <bvanassche@....org>
To: Alan Stern <stern@...land.harvard.edu>, Tejun Heo <tj@...nel.org>
Cc: Greg KH <gregkh@...uxfoundation.org>,
 Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fs: sysfs: Fix reference leak in
 sysfs_break_active_protection()

On 3/13/24 14:43, Alan Stern wrote:
> The sysfs_break_active_protection() routine has an obvious reference
> leak in its error path.  If the call to kernfs_find_and_get() fails then
> kn will be NULL, so the companion sysfs_unbreak_active_protection()
> routine won't get called (and would only cause an access violation by
> trying to dereference kn->parent if it was called).  As a result, the
> reference to kobj acquired at the start of the function will never be
> released.
> 
> Fix the leak by adding an explicit kobject_put() call when kn is NULL.

Reviewed-by: Bart Van Assche <bvanassche@....org>