[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <656cec43-5810-3626-2251-7db2f8868f95@huawei.com>
Date: Wed, 2 Mar 2022 12:13:04 +0800
From: "weiyongjun (A)" <weiyongjun1@...wei.com>
To: "cgel.zte@...il.com" <cgel.zte@...il.com>,
"krzysztof.kozlowski@...onical.com"
<krzysztof.kozlowski@...onical.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Minghao Chi (CGEL ZTE)" <chi.minghao@....com.cn>,
Zeal Robot <zealci@....com.cn>
Subject: Re: [PATCH V2] net/nfc/nci: fix infoleak in struct
nci_set_config_param
> From: "Minghao Chi (CGEL ZTE)" <chi.minghao@....com.cn>
>
> On 64-bit systems, struct nci_set_config_param has
> an added padding of 7 bytes between struct members
> id and len. Even though all struct members are initialized,
> the 7-byte hole will contain data from the kernel stack.
> This patch zeroes out struct nci_set_config_param before
> usage, preventing infoleaks to userspace.
How this info leaks to userspace?
nci_set_config_req() convert to use packed 'struct nci_core_set_config_cmd'
to send data, which does not contain hole.
Powered by blists - more mailing lists