netdev - [PATCH] net/netlink: how to deal with the problem of exceeding the maximum reach of nlattr's nla

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-next>] [day] [month] [year] [list]

Message-ID: <20240321141400.38639-1-renmingshuai@huawei.com>
Date: Thu, 21 Mar 2024 22:14:00 +0800
From: renmingshuai <renmingshuai@...wei.com>
To: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
	<pabeni@...hat.com>, <idosch@...dia.com>, <netdev@...r.kernel.org>
CC: <renmingshuai@...wei.com>, <yanan@...wei.com>, <chenzhen126@...wei.com>,
	<liaichun@...wei.com>
Subject: [PATCH] net/netlink: how to deal with the problem of exceeding the maximum reach of nlattr's nla_len

RTM_GETLINK for greater than about 220 VFs truncates IFLA_VFINFO_LIST
due to the maximum reach of nlattr's nla_len being exceeded. As a result,
the value of nla_len overflows in nla_nest_end(). According to [1],
changing the type of nla_len is not possible, but how can we deal with this
overflow problem? The nla_len is constantly set to the
maximum value when it overflows? Or some better ways?

[1] https://lore.kernel.org/netdev/20210123045321.2797360-1-edwin.peer@broadcom.com/