nl80211: check netlink protocol in socket release notification
authorDmitry Ivanov <dmitrijs.ivanovs@ubnt.com>
Wed, 6 Apr 2016 14:23:18 +0000 (17:23 +0300)
committerJohannes Berg <johannes.berg@intel.com>
Tue, 12 Apr 2016 13:39:06 +0000 (15:39 +0200)
commit8f815cdde3e550e10c2736990d791f60c2ce43eb
tree73a1773500eb7bb14d10b0c30001af5be98baf22
parent30d237a6c2e9be1bb816fe8e787b88fd7aad833b
nl80211: check netlink protocol in socket release notification

A non-privileged user can create a netlink socket with the same port_id as
used by an existing open nl80211 netlink socket (e.g. as used by a hostapd
process) with a different protocol number.

Closing this socket will then lead to the notification going to nl80211's
socket release notification handler, and possibly cause an action such as
removing a virtual interface.

Fix this issue by checking that the netlink protocol is NETLINK_GENERIC.
Since generic netlink has no notifier chain of its own, we can't fix the
problem more generically.

Fixes: 026331c4d9b5 ("cfg80211/mac80211: allow registering for and sending action frames")
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Ivanov <dima@ubnt.com>
[rewrite commit message]
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
net/wireless/nl80211.c
This page took 0.02465 seconds and 5 git commands to generate.