linux-kernel - Re: [PATCH] tun: fix mismatch in mutex lock-unlock in tun_get

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:   Mon, 19 Feb 2018 11:15:00 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     khoroshilov@...ras.ru
Cc:     jasowang@...hat.com, edumazet@...gle.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, ldv-project@...uxtesting.org
Subject: Re: [PATCH] tun: fix mismatch in mutex lock-unlock in
 tun_get_user()

From: Alexey Khoroshilov <khoroshilov@...ras.ru>
Date: Sat, 17 Feb 2018 01:11:55 +0300

> There is a single error path where tfile->napi_mutex is left unlocked.
> It can lead to a deadlock.
> 
> Found by Linux Driver Verification project (linuxtesting.org).
> 
> Signed-off-by: Alexey Khoroshilov <khoroshilov@...ras.ru>

As Eric explained, tun_napi_frags_enabled() (and therefore 'frags')
will never be true for TUN devices, which is the type handled by this
code path.