linux-kernel - Re: [PATCH v3] selftests/capabilities: Fix possible file leak in copy_fromat

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: <a194b5d3-d3f8-48a4-a010-d98381107b80@web.de>
Date: Mon, 1 Jul 2024 10:01:13 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Ma Ke <make24@...as.ac.cn>, linux-kselftest@...r.kernel.org,
 Amer Al Shanawany <amer.shanawany@...il.com>,
 Andrew Morton <akpm@...ux-foundation.org>, Andy Lutomirski
 <luto@...nel.org>, Kees Cook <kees@...nel.org>,
 Muhammad Usama Anjum <usama.anjum@...labora.com>,
 Shuah Khan <shuah@...nel.org>,
 Swarup Laxman Kotiaklapudi <swarupkotikalapudi@...il.com>
Cc: kernel-janitors@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
 Julia Lawall <julia.lawall@...ia.fr>
Subject: Re: [PATCH v3] selftests/capabilities: Fix possible file leak in
 copy_fromat_to

>                                        … openat() and open() initialize
> 'from' and 'to', and only 'from' validated with 'if' statement.

Why do you find such information helpful?

>                                                                 If the
> initialization of variable 'to' fails,

The variable assignment will usually succeed.
A stored return value would eventually indicate a failed function call.

>                                        we should better check the value
> of 'to' and close 'from' to avoid possible file leak. Improve the checking
> of 'from' additionally.

Please split desired changes into separate update steps.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n168

How do you think about to use a summary phrase like “Complete error handling
in copy_fromat_to()”?

Under which circumstances would you become interested to take remaining
patch review concerns better into account?

…
> ---
> Changes in v3:
> - Thank you for your interest in our vulnerability detection method. We
> extract vulnerability characteristics from a known vulnerability and match
> the same characteristics in the project code. As our work is still in
> progress, we are not able to disclose it at this time. …

* In which time range do you plan to publish an official announcement?

* Will similar software research approaches be discussed further?

> - found by customized static analysis tool.
> ---

Would you like to replace a duplicate marker line by a blank line?

Regards,
Markus