<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net/wireless, branch v5.4</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v5.4</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v5.4'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2019-10-30T09:11:18Z</updated>
<entry>
<title>nl80211: fix validation of mesh path nexthop</title>
<updated>2019-10-30T09:11:18Z</updated>
<author>
<name>Markus Theil</name>
<email>markus.theil@tu-ilmenau.de</email>
</author>
<published>2019-10-29T09:30:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1fab1b89e2e8f01204a9c05a39fd0b6411a48593'/>
<id>urn:sha1:1fab1b89e2e8f01204a9c05a39fd0b6411a48593</id>
<content type='text'>
Mesh path nexthop should be a ethernet address, but current validation
checks against 4 byte integers.

Cc: stable@vger.kernel.org
Fixes: 2ec600d672e74 ("nl80211/cfg80211: support for mesh, sta dumping")
Signed-off-by: Markus Theil &lt;markus.theil@tu-ilmenau.de&gt;
Link: https://lore.kernel.org/r/20191029093003.10355-1-markus.theil@tu-ilmenau.de
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>nl80211: Disallow setting of HT for channel 14</title>
<updated>2019-10-30T09:07:22Z</updated>
<author>
<name>Masashi Honma</name>
<email>masashi.honma@gmail.com</email>
</author>
<published>2019-10-21T07:50:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ec649fed66bb242cca145ab364485c5a126efc53'/>
<id>urn:sha1:ec649fed66bb242cca145ab364485c5a126efc53</id>
<content type='text'>
This patch disables setting of HT20 and more for channel 14 because
the channel is only for IEEE 802.11b.

The patch for net/wireless/util.c was unit-tested.

The patch for net/wireless/chan.c was tested with iw command.

Before this patch.
$ sudo iw dev &lt;ifname&gt; set channel 14 HT20
$

After this patch.
$ sudo iw dev &lt;ifname&gt; set channel 14 HT20
kernel reports: invalid channel definition
command failed: Invalid argument (-22)
$

Signed-off-by: Masashi Honma &lt;masashi.honma@gmail.com&gt;
Link: https://lore.kernel.org/r/20191021075045.2719-1-masashi.honma@gmail.com
[clean up the code, use != instead of equivalent &gt;]
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>mac80211: fix scan when operating on DFS channels in ETSI domains</title>
<updated>2019-10-07T20:10:50Z</updated>
<author>
<name>Aaron Komisar</name>
<email>aaron.komisar@tandemg.com</email>
</author>
<published>2019-10-02T13:59:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=dc0c18ed229cdcca283dd78fefa38273ec37a42c'/>
<id>urn:sha1:dc0c18ed229cdcca283dd78fefa38273ec37a42c</id>
<content type='text'>
In non-ETSI regulatory domains scan is blocked when operating channel
is a DFS channel. For ETSI, however, once DFS channel is marked as
available after the CAC, this channel will remain available (for some
time) even after leaving this channel.

Therefore a scan can be done without any impact on the availability
of the DFS channel as no new CAC is required after the scan.

Enable scan in mac80211 in these cases.

Signed-off-by: Aaron Komisar &lt;aaron.komisar@tandemg.com&gt;
Link: https://lore.kernel.org/r/1570024728-17284-1-git-send-email-aaron.komisar@tandemg.com
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>cfg80211: fix a bunch of RCU issues in multi-bssid code</title>
<updated>2019-10-07T19:35:57Z</updated>
<author>
<name>Sara Sharon</name>
<email>sara.sharon@intel.com</email>
</author>
<published>2019-10-04T12:37:06Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=461c4c2b4c0731d7452bad4e77c0cdbdcea1804c'/>
<id>urn:sha1:461c4c2b4c0731d7452bad4e77c0cdbdcea1804c</id>
<content type='text'>
cfg80211_update_notlisted_nontrans() leaves the RCU critical session
too early, while still using nontrans_ssid which is RCU protected. In
addition, it performs a bunch of RCU pointer update operations such
as rcu_access_pointer and rcu_assign_pointer.

The caller, cfg80211_inform_bss_frame_data(), also accesses the RCU
pointer without holding the lock.

Just wrap all of this with bss_lock.

Signed-off-by: Sara Sharon &lt;sara.sharon@intel.com&gt;
Signed-off-by: Luca Coelho &lt;luciano.coelho@intel.com&gt;
Link: https://lore.kernel.org/r/20191004123706.15768-3-luca@coelho.fi
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>nl80211: fix memory leak in nl80211_get_ftm_responder_stats</title>
<updated>2019-10-07T19:34:52Z</updated>
<author>
<name>Navid Emamdoost</name>
<email>navid.emamdoost@gmail.com</email>
</author>
<published>2019-10-04T19:42:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1399c59fa92984836db90538cf92397fe7caaa57'/>
<id>urn:sha1:1399c59fa92984836db90538cf92397fe7caaa57</id>
<content type='text'>
In nl80211_get_ftm_responder_stats, a new skb is created via nlmsg_new
named msg. If nl80211hdr_put() fails, then msg should be released. The
return statement should be replace by goto to error handling code.

Fixes: 81e54d08d9d8 ("cfg80211: support FTM responder configuration/statistics")
Signed-off-by: Navid Emamdoost &lt;navid.emamdoost@gmail.com&gt;
Link: https://lore.kernel.org/r/20191004194220.19412-1-navid.emamdoost@gmail.com
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>cfg80211: wext: avoid copying malformed SSIDs</title>
<updated>2019-10-04T12:04:08Z</updated>
<author>
<name>Will Deacon</name>
<email>will@kernel.org</email>
</author>
<published>2019-10-04T09:51:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4ac2813cc867ae563a1ba5a9414bfb554e5796fa'/>
<id>urn:sha1:4ac2813cc867ae563a1ba5a9414bfb554e5796fa</id>
<content type='text'>
Ensure the SSID element is bounds-checked prior to invoking memcpy()
with its length field, when copying to userspace.

Cc: &lt;stable@vger.kernel.org&gt;
Cc: Kees Cook &lt;keescook@chromium.org&gt;
Reported-by: Nicolas Waisman &lt;nico@semmle.com&gt;
Signed-off-by: Will Deacon &lt;will@kernel.org&gt;
Link: https://lore.kernel.org/r/20191004095132.15777-2-will@kernel.org
[adjust commit log a bit]
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>nl80211: fix null pointer dereference</title>
<updated>2019-10-01T15:56:19Z</updated>
<author>
<name>Miaoqing Pan</name>
<email>miaoqing@codeaurora.org</email>
</author>
<published>2019-09-26T08:16:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=b501426cf86e70649c983c52f4c823b3c40d72a3'/>
<id>urn:sha1:b501426cf86e70649c983c52f4c823b3c40d72a3</id>
<content type='text'>
If the interface is not in MESH mode, the command 'iw wlanx mpath del'
will cause kernel panic.

The root cause is null pointer access in mpp_flush_by_proxy(), as the
pointer 'sdata-&gt;u.mesh.mpp_paths' is NULL for non MESH interface.

Unable to handle kernel NULL pointer dereference at virtual address 00000068
[...]
PC is at _raw_spin_lock_bh+0x20/0x5c
LR is at mesh_path_del+0x1c/0x17c [mac80211]
[...]
Process iw (pid: 4537, stack limit = 0xd83e0238)
[...]
[&lt;c021211c&gt;] (_raw_spin_lock_bh) from [&lt;bf8c7648&gt;] (mesh_path_del+0x1c/0x17c [mac80211])
[&lt;bf8c7648&gt;] (mesh_path_del [mac80211]) from [&lt;bf6cdb7c&gt;] (extack_doit+0x20/0x68 [compat])
[&lt;bf6cdb7c&gt;] (extack_doit [compat]) from [&lt;c05c309c&gt;] (genl_rcv_msg+0x274/0x30c)
[&lt;c05c309c&gt;] (genl_rcv_msg) from [&lt;c05c25d8&gt;] (netlink_rcv_skb+0x58/0xac)
[&lt;c05c25d8&gt;] (netlink_rcv_skb) from [&lt;c05c2e14&gt;] (genl_rcv+0x20/0x34)
[&lt;c05c2e14&gt;] (genl_rcv) from [&lt;c05c1f90&gt;] (netlink_unicast+0x11c/0x204)
[&lt;c05c1f90&gt;] (netlink_unicast) from [&lt;c05c2420&gt;] (netlink_sendmsg+0x30c/0x370)
[&lt;c05c2420&gt;] (netlink_sendmsg) from [&lt;c05886d0&gt;] (sock_sendmsg+0x70/0x84)
[&lt;c05886d0&gt;] (sock_sendmsg) from [&lt;c0589f4c&gt;] (___sys_sendmsg.part.3+0x188/0x228)
[&lt;c0589f4c&gt;] (___sys_sendmsg.part.3) from [&lt;c058add4&gt;] (__sys_sendmsg+0x4c/0x70)
[&lt;c058add4&gt;] (__sys_sendmsg) from [&lt;c0208c80&gt;] (ret_fast_syscall+0x0/0x44)
Code: e2822c02 e2822001 e5832004 f590f000 (e1902f9f)
---[ end trace bbd717600f8f884d ]---

Signed-off-by: Miaoqing Pan &lt;miaoqing@codeaurora.org&gt;
Link: https://lore.kernel.org/r/1569485810-761-1-git-send-email-miaoqing@codeaurora.org
[trim useless data from commit message]
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>cfg80211: initialize on-stack chandefs</title>
<updated>2019-10-01T15:56:18Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2019-09-23T11:51:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f43e5210c739fe76a4b0ed851559d6902f20ceb1'/>
<id>urn:sha1:f43e5210c739fe76a4b0ed851559d6902f20ceb1</id>
<content type='text'>
In a few places we don't properly initialize on-stack chandefs,
resulting in EDMG data to be non-zero, which broke things.

Additionally, in a few places we rely on the driver to init the
data completely, but perhaps we shouldn't as non-EDMG drivers
may not initialize the EDMG data, also initialize it there.

Cc: stable@vger.kernel.org
Fixes: 2a38075cd0be ("nl80211: Add support for EDMG channels")
Reported-by: Dmitry Osipenko &lt;digetx@gmail.com&gt;
Tested-by: Dmitry Osipenko &lt;digetx@gmail.com&gt;
Link: https://lore.kernel.org/r/1569239475-I2dcce394ecf873376c386a78f31c2ec8b538fa25@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>cfg80211: validate SSID/MBSSID element ordering assumption</title>
<updated>2019-10-01T15:56:18Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2019-09-20T19:54:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=242b0931c1918c56cd1dc5563fd250a3c39b996d'/>
<id>urn:sha1:242b0931c1918c56cd1dc5563fd250a3c39b996d</id>
<content type='text'>
The code copying the data assumes that the SSID element is
before the MBSSID element, but since the data is untrusted
from the AP, this cannot be guaranteed.

Validate that this is indeed the case and ignore the MBSSID
otherwise, to avoid having to deal with both cases for the
copy of data that should be between them.

Cc: stable@vger.kernel.org
Fixes: 0b8fb8235be8 ("cfg80211: Parsing of Multiple BSSID information in scanning")
Link: https://lore.kernel.org/r/1569009255-I1673911f5eae02964e21bdc11b2bf58e5e207e59@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>nl80211: validate beacon head</title>
<updated>2019-10-01T15:56:18Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2019-09-20T19:54:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f88eb7c0d002a67ef31aeb7850b42ff69abc46dc'/>
<id>urn:sha1:f88eb7c0d002a67ef31aeb7850b42ff69abc46dc</id>
<content type='text'>
We currently don't validate the beacon head, i.e. the header,
fixed part and elements that are to go in front of the TIM
element. This means that the variable elements there can be
malformed, e.g. have a length exceeding the buffer size, but
most downstream code from this assumes that this has already
been checked.

Add the necessary checks to the netlink policy.

Cc: stable@vger.kernel.org
Fixes: ed1b6cc7f80f ("cfg80211/nl80211: add beacon settings")
Link: https://lore.kernel.org/r/1569009255-I7ac7fbe9436e9d8733439eab8acbbd35e55c74ef@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
</feed>
