summaryrefslogtreecommitdiffstats
path: root/mm/vmscan.c
diff options
context:
space:
mode:
authorDmitry Ivanov <dmitrijs.ivanovs@ubnt.com>2016-04-06 17:23:18 +0300
committerJohannes Berg <johannes.berg@intel.com>2016-04-12 15:39:06 +0200
commit8f815cdde3e550e10c2736990d791f60c2ce43eb (patch)
tree73a1773500eb7bb14d10b0c30001af5be98baf22 /mm/vmscan.c
parent30d237a6c2e9be1bb816fe8e787b88fd7aad833b (diff)
downloadop-kernel-dev-8f815cdde3e550e10c2736990d791f60c2ce43eb.zip
op-kernel-dev-8f815cdde3e550e10c2736990d791f60c2ce43eb.tar.gz
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>
Diffstat (limited to 'mm/vmscan.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud