mac80211: reject zero MAC address in add station
PATCH 1/1 mac80211: reject zero MAC address in add station
Don't allow using a zero MAC address as the station MAC address. so validated the MAC address using is_valid_ether_addr.
--- net/mac80211/cfg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/mac80211/cfg.c +1 -1
@@ -1539,7 +1539,7 @@ static int ieee80211_add_station(struct wiphy *wiphy, struct net_device *dev,if (ether_addr_equal (mac, sdata->vif.addr))return -EINVAL ; -if (is_multicast_ether_addr (mac)) +if (!is_valid_ether_addr (mac))return -EINVAL ; sta =sta_info_alloc (sdata, mac,GFP_KERNEL );
Signature · 1 line
1.9.1
Johannes Berg
maintainerQuoted 3 lines · Karthikeyan Periyasamy
Don't allow using a zero MAC address as the station MAC address. so validated the MAC address using
is_valid_ether_addr.
Theoretically, all zeroes might have been a valid address at some point. I see no reason not to reject it, but I'd like to know why you ended up with this now??
johannes
Quoted 8 lines
Quoted 3 lines
Don't allow using a zero MAC address as the station MAC address. so validated the MAC address using
is_valid_ether_addr.Theoretically, all zeroes might have been a valid address at some point. I see no reason not to reject it, but I'd like to know why you ended up with this now??
Its a Wireless fuzz testing tool (codenomicon) which sends out different types of frames to the AP. It actually tampers legitimate wireless frames (Probe, Auth, Assoc, Data etc..) and will send to the AP. I thought allowing a zero MAC address station is not a valid. so validated the given MAC address. Just for curious, which case all zero address is a valid MAC.
Thanks,
Karthikeyan
Johannes Berg
maintainerQuoted 10 lines · Karthikeyan Periyasamy
Quoted 9 lines
Quoted 3 lines
Don't allow using a zero MAC address as the station MAC address. so validated the MAC address using
is_valid_ether_addr.Theoretically, all zeroes might have been a valid address at some point.
I see no reason not to reject it, but I'd like to know why you ended up with this now??
Quoted 6 lines
Its a Wireless fuzz testing tool (codenomicon) which sends out different types of frames to the AP. It actually tampers legitimate wireless frames (Probe, Auth, Assoc, Data etc..) and will send to the AP. I thought allowing a zero MAC address station is not a valid. so validated the given MAC address. Just for curious, which case all zero address is a valid MAC.
Well, it isn't really, but the OUI 00:00:00 *is* in fact assigned (or was), and theoretically the vendor could assign it to a device.
We do assume basically everywhere that it's invalid though.
Was just wondering how you came across this really, I guess I'll add a bit of text to the commit log and merge it.
johannes
Quoted 18 lines · Johannes Berg
Quoted 10 lines · Karthikeyan Periyasamy
Quoted 9 lines
Quoted 3 lines
Don't allow using a zero MAC address as the station MAC address. so validated the MAC address using
is_valid_ether_addr.Theoretically, all zeroes might have been a valid address at some point.
I see no reason not to reject it, but I'd like to know why you ended up with this now??Quoted 6 lines
Its a Wireless fuzz testing tool (codenomicon) which sends out different types of frames to the AP. It actually tampers legitimate wireless frames (Probe, Auth, Assoc, Data etc..) and will send to the AP. I thought allowing a zero MAC address station is not a valid. so validated the given MAC address. Just for curious, which case all zero address is a valid MAC.
Quoted 2 lines
Well, it isn't really, but the OUI 00:00:00 *is* in fact assigned (or was), and theoretically the vendor could assign it to a device.
Heh, now that we allow routing the 0.0.0.0/8 subnet, this means that the following could be a perfectly sensible thing to do:
'ip neigh add 0.0.0.1/8 lladdr 00:00:00:00:00:01 dev wlan0'
One bit per address per network layer ought to be enough for everyone, right? ;)
-Toke