[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOiHx=mWrizoJAOU=40NWk6A1+b99WCM1EkxVwLfiJ8Sv4pDKg@mail.gmail.com>
Date: Thu, 8 Jan 2026 13:25:51 +0100
From: Jonas Gorski <jonas.gorski@...il.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Johannes Berg <johannes@...solutions.net>, "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
Hi,
On Thu, Jan 8, 2026 at 12:28 PM Eric Dumazet <edumazet@...gle.com> wrote:
>
> 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
In case you do a V2: dislosing -> disclosing (I assume)
> > > to user space.
Best regards,
Jonas
Powered by blists - more mailing lists