Hello Marcel, could you apply this to bluetooth-next? regards Stefan Schmidt On 23/07/16 14:21, Alexander Aring wrote:
Hi, On 07/20/2016 10:43 AM, Vegard Nossum wrote:I've observed a NULL pointer dereference in ieee802154_del_iface() during netlink fuzzing. It's the ->wpan_phy dereference here: phy = dev->ieee802154_ptr->wpan_phy; My bet is that we're not checking that this is an IEEE802154 interface, so let's do what ieee802154_nl_get_dev() is doing. (Maybe we should even be calling this directly?) Cc: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx> Cc: Alexander Aring <alex.aring@xxxxxxxxx> Cc: Marcel Holtmann <marcel@xxxxxxxxxxxx> Cc: Dmitry Eremin-Solenikov <dbaryshkov@xxxxxxxxx> Cc: Sergey Lapin <slapin@xxxxxxxxxxx> Signed-off-by: Vegard Nossum <vegard.nossum@xxxxxxxxxx>Acked-by: Alexander Aring <aar@xxxxxxxxxxxxxx> thanks for letting us known that this bug exists. Unfortunate I don't care much about this code. This code is part of the old UAPI for 802.15.4 subsystems and there are many bugs known. Nevertheless I added my ack here and would like that Marcel apply this patch into his bluetooth tree repository. The new netlink api exists since 3.19 and highly recommended to don't use the old stuff. The ieee802154 never got out the experimental state, there was a patch [0] which globally remove the experimental Kconfig entry, but no maintainer ever said that this branch isn't in experimental state anymore. I will prepare a RFC series to remove all deprecated handling which we have replacements for it, these are: - old netlink api - af_802154 raw sockets, will replaced by AF_PACKET RAW - Alex [0] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/net/ieee802154/Kconfig?id=f4671a90c418b5aae14b61a9fc9d79c629403ca0 -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
-- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
