linux-kernel - Re: [PATCH 020/190] Revert "PCI: Fix pci_create

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

Date:   Mon, 26 Apr 2021 19:05:45 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     linux-kernel@...r.kernel.org, Qiushi Wu <wu000273@....edu>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Jiri Kosina <jikos@...nel.org>,
        Jubin Zhong <zhongjubin@...wei.com>
Subject: Re: [PATCH 020/190] Revert "PCI: Fix pci_create_slot() reference
 count leak"

On Wed, Apr 21, 2021 at 11:43:31PM -0500, Bjorn Helgaas wrote:
> [+cc Jiri, Jubin (author of 4684709bf81a)]
> 
> On Wed, Apr 21, 2021 at 02:58:15PM +0200, Greg Kroah-Hartman wrote:
> > This reverts commit 8a94644b440eef5a7b9c104ac8aa7a7f413e35e5.
> > 
> > Commits from @umn.edu addresses have been found to be submitted in "bad
> > faith" to try to test the kernel community's ability to review "known
> > malicious" changes.  The result of these submissions can be found in a
> > paper published at the 42nd IEEE Symposium on Security and Privacy
> > entitled, "Open Source Insecurity: Stealthily Introducing
> > Vulnerabilities via Hypocrite Commits" written by Qiushi Wu (University
> > of Minnesota) and Kangjie Lu (University of Minnesota).
> > 
> > Because of this, all submissions from this group must be reverted from
> > the kernel tree and will need to be re-reviewed again to determine if
> > they actually are a valid fix.  Until that work is complete, remove this
> > change to ensure that no problems are being introduced into the
> > codebase.
> > 
> > Cc: https
> > Cc: Qiushi Wu <wu000273@....edu>
> > Cc: Bjorn Helgaas <bhelgaas@...gle.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> 
> Please do not apply this revert.
> 
> Prior to 8a94644b440e ("PCI: Fix pci_create_slot() reference count
> leak"), we essentially had this:
> 
>   err = kobject_init_and_add(&slot->kobj, &pci_slot_ktype, ...);
>   if (err)
>     kfree(slot);
>     return ERR_PTR(err);
> 
>   INIT_LIST_HEAD(&slot->list);
>   list_add(&slot->list, &parent->slots);
> 
> That was incorrect because if kobject_init_and_add() fails,
> kobject_put() must be called to clean up the object (per the function
> comment).  For pci_slot_ktype, the release function is
> pci_slot_release():
> 
>   pci_slot_release
>     list_del(&slot->list);
>     kfree(slot);
> 
> After 8a94644b440e, we had:
> 
>   err = kobject_init_and_add(&slot->kobj, &pci_slot_ktype, ...);
>   if (err)
>     kobject_put(&slot->kobj);
>     return ERR_PTR(err);
> 
>   INIT_LIST_HEAD(&slot->list);
>   list_add(&slot->list, &parent->slots);
> 
> This fixed one bug but exposed another: we correctly clean up the
> object by calling kobject_put() which calls pci_slot_release(), but 
> that dereferences slot->list, which hasn't been initialized yet.
> 
> But 4684709bf81a ("PCI: Fix pci_slot_release() NULL pointer
> dereference") fixed that problem by making it this:
> 
>   INIT_LIST_HEAD(&slot->list);
>   list_add(&slot->list, &parent->slots);
>   err = kobject_init_and_add(&slot->kobj, &pci_slot_ktype, ...);
>   if (err)
>     kobject_put(&slot->kobj);
>     return ERR_PTR(err);
> 
> This correctly initializes slot->list and cleans up if
> kobject_init_and_add() fails.
> 
> But if we apply this revert, we'll have this:
> 
>   INIT_LIST_HEAD(&slot->list);
>   list_add(&slot->list, &parent->slots);
>   err = kobject_init_and_add(&slot->kobj, &pci_slot_ktype, ...);
>   if (err)
>     kfree(slot);
>     return ERR_PTR(err);
> 
> Now we kfree(slot), but we don't call kobject_put(), so we don't
> remove it from the list, so the list is now corrupted because one of
> its entries has been deallocated.

Thanks for the review, I have now dropped this revert.

greg k-h