linux-kernel - Re: [PATCH][xen-next] xen/pvcalls: fix null pointer reference on sock

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]

Date:   Tue, 18 Jul 2017 10:01:00 +0200
From:   Juergen Gross <jgross@...e.com>
To:     Colin King <colin.king@...onical.com>,
        Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        xen-devel@...ts.xenproject.org
Cc:     kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][xen-next] xen/pvcalls: fix null pointer reference on
 sock_release call

On 11/07/17 21:41, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
> 
> Currently a sock_release on map->sock will result in a null pointer
> deference on map when map is null. Instead, the sock_relase sould
> be on sock and not map->sock.
> 
> Detected by CoverityScan, CID#1450169 ("Dereference after null check")
> 
> Fixes: b535e2b9b78a ("xen/pvcalls: implement connect command")
> Signed-off-by: Colin Ian King <colin.king@...onical.com>

Committed to xen/tip for-linus-4.13


Thanks,

Juergen