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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <495b042e-62f3-4eb5-9190-f39d082b1291@nop.hu>
Date: Tue, 21 Oct 2025 17:28:23 +0200
From: mc36 <csmate@....hu>
To: Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
 Jason Xing <kerneljasonxing@...il.com>
Cc: alekcejk@...glemail.com, Jonathan Lemon <jonathan.lemon@...il.com>,
 Stanislav Fomichev <sdf@...ichev.me>,
 Magnus Karlsson <magnus.karlsson@...el.com>, Björn Töpel
 <bjorn@...nel.org>, 1118437@...s.debian.org, netdev@...r.kernel.org,
 bpf@...r.kernel.org
Subject: Re: null pointer dereference in interrupt after receiving an ip
 packet on veth from xsk from user space

hi,

On 10/21/25 16:47, Maciej Fijalkowski wrote:

> However, I do not understand why setting mac addr on one veth interface
> triggers this path.
> 

just my 10 cents but imho i saw a check for promisc while walking through the call

stack's small epsilon surroundings, maybe there is a for-us check somewhere earlier?

recall that we're setting the interface hw-address to the packet's destination mac...

br,

cs


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ