[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iLxDc9viP0Pmj3uC01s46eUR2xu4XAUEo=he-M84aCf9A@mail.gmail.com>
Date: Thu, 8 Jan 2026 11:32:04 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
eric.dumazet@...il.com, syzbot+bfc7323743ca6dbcc3d3@...kaller.appspotmail.com,
stable@...r.kernel.org
Subject: Re: [PATCH net] wifi: avoid kernel-infoleak from struct iw_point
On Thu, Jan 8, 2026 at 11:29 AM Johannes Berg <johannes@...solutions.net> wrote:
>
> On Thu, 2026-01-08 at 10:19 +0000, Eric Dumazet wrote:
> > struct iw_point has a 32bit hole on 64bit arches.
> >
> > struct iw_point {
> > void __user *pointer; /* Pointer to the data (in user space) */
> > __u16 length; /* number of fields or size in bytes */
> > __u16 flags; /* Optional params */
> > };
> >
> > Make sure to zero the structure to avoid dislosing 32bits of kernel data
> > to user space.
>
> Heh, wow. Talk about old code.
>
> > Reported-by: syzbot+bfc7323743ca6dbcc3d3@...kaller.appspotmail.com
> > https://lore.kernel.org/netdev/695f83f3.050a0220.1c677c.0392.GAE@google.com/T/#u
>
> Was that intentionally without Link: or some other tag?
Somehow the Closes: prefix has been lost when I cooked the patch.
Closes: https://lore.kernel.org/netdev/695f83f3.050a0220.1c677c.0392.GAE@google.com/T/#u
Let me know if you want a V2, thanks.
>
> johannes
Powered by blists - more mailing lists