linux-kernel - Re: [PATCH 2/2] i2c: Fix a potential use after free

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]

Message-ID: <81b35c80-74c2-e14e-4947-f23ec6197b73@web.de>
Date:   Sat, 28 Dec 2019 13:50:22 +0100
From:   Markus Elfring <Markus.Elfring@....de>
To:     Xu Wang <vulab@...as.ac.cn>, linux-i2c@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, Wolfram Sang <wsa@...-dreams.de>
Subject: Re: [PATCH 2/2] i2c: Fix a potential use after free

> Free the adap structure only after we are done using it.

This information can be reasonable.

> This patch just moves the put_device() down a bit to avoid the
> use after free.

I suggest to reconsider such a change because a device reference count
should eventually be decremented before decrementing the reference count
for the module which is managed by this programming interface.
Would you like to clarify the dependencies for such an use case any more?

Regards,
Markus