diff options
| author | Colin Ian King <colin.king@canonical.com> | 2018-02-22 17:22:59 +0000 |
|---|---|---|
| committer | Juergen Gross <jgross@suse.com> | 2018-02-26 17:13:12 +0100 |
| commit | 68d2059be660944152ba667e43c3b4ec225974bc (patch) | |
| tree | 705c8b8a66719778986204fd92bda346fc5e98bc | |
| parent | d1a75e0896f5e9f5cb6a979caaea39f1f4b9feb1 (diff) | |
xen/pvcalls: fix null pointer dereference on map->sock
Currently if map is null then a potential null pointer deference
occurs when calling sock_release on map->sock. I believe the
actual intention was to call sock_release on sock instead. Fix
this.
Fixes: 5db4d286a8ef ("xen/pvcalls: implement connect command")
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Signed-off-by: Juergen Gross <jgross@suse.com>
| -rw-r--r-- | drivers/xen/pvcalls-back.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c index 156e5aea36db..b1092fbefa63 100644 --- a/drivers/xen/pvcalls-back.c +++ b/drivers/xen/pvcalls-back.c @@ -416,7 +416,7 @@ static int pvcalls_back_connect(struct xenbus_device *dev, sock); if (!map) { ret = -EFAULT; - sock_release(map->sock); + sock_release(sock); } out: |