linux-kernel - Re: [PATCH -next] vfio: platform: reset: add missing iounmap() on error in vfio_platform_amdxgbe

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: <20210518154647.6541bac2.alex.williamson@redhat.com>
Date:   Tue, 18 May 2021 15:46:47 -0600
From:   Alex Williamson <alex.williamson@...hat.com>
To:     Yang Yingliang <yangyingliang@...wei.com>
Cc:     <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>,
        <eric.auger@...hat.com>
Subject: Re: [PATCH -next] vfio: platform: reset: add missing iounmap() on
 error in vfio_platform_amdxgbe_reset()

On Thu, 13 May 2021 13:09:24 +0800
Yang Yingliang <yangyingliang@...wei.com> wrote:

> Add the missing iounmap() before return from vfio_platform_amdxgbe_reset()
> in the error handling case.
> 
> Fixes: 0990822c9866 ("VFIO: platform: reset: AMD xgbe reset module")
> Reported-by: Hulk Robot <hulkci@...wei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@...wei.com>
> ---
>  drivers/vfio/platform/reset/vfio_platform_amdxgbe.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/vfio/platform/reset/vfio_platform_amdxgbe.c b/drivers/vfio/platform/reset/vfio_platform_amdxgbe.c
> index abdca900802d..c6d823a27bd6 100644
> --- a/drivers/vfio/platform/reset/vfio_platform_amdxgbe.c
> +++ b/drivers/vfio/platform/reset/vfio_platform_amdxgbe.c
> @@ -61,8 +61,10 @@ static int vfio_platform_amdxgbe_reset(struct vfio_platform_device *vdev)
>  	if (!xpcs_regs->ioaddr) {
>  		xpcs_regs->ioaddr =
>  			ioremap(xpcs_regs->addr, xpcs_regs->size);
> -		if (!xpcs_regs->ioaddr)
> +		if (!xpcs_regs->ioaddr) {
> +			iounmap(xgmac_regs->ioaddr);
>  			return -ENOMEM;
> +		}
>  	}
>  
>  	/* reset the PHY through MDIO*/

This actually introduces multiple bugs.  vfio-platform has common code
for calling iounmap when the device is released and the struct
vfio_platform_region ioaddr member is re-used throughout the code.
Performing an iounmap() without setting the value to NULL essentially
introduces use-after-free and double free bugs.  There's no bug in the
original afaict, the iounmap occurs lazily on release.  Thanks,

Alex