b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: b.a.t.m.a.n@lists.open-mesh.org, gregkh@linuxfoundation.org,
	linus.luessing@c0d3.blue, me@irrelefant.net, sven@narfation.org,
	sw@simonwunderlich.de
Cc: stable-commits@vger.kernel.org
Subject: Patch "batman-adv: Fix multicast TT issues with bogus ROAM flags" has been added to the 4.4-stable tree
Date: Tue, 23 Nov 2021 13:42:43 +0100	[thread overview]
Message-ID: <163767136325592@kroah.com> (raw)
In-Reply-To: <20211120123939.260723-3-sven@narfation.org>


This is a note to let you know that I've just added the patch titled

    batman-adv: Fix multicast TT issues with bogus ROAM flags

to the 4.4-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     batman-adv-fix-multicast-tt-issues-with-bogus-roam-flags.patch
and it can be found in the queue-4.4 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


From foo@baz Tue Nov 23 01:39:02 PM CET 2021
From: Sven Eckelmann <sven@narfation.org>
Date: Sat, 20 Nov 2021 13:39:30 +0100
Subject: batman-adv: Fix multicast TT issues with bogus ROAM flags
To: stable@vger.kernel.org
Cc: b.a.t.m.a.n@lists.open-mesh.org, "Linus Lüssing" <linus.luessing@c0d3.blue>, "Leonardo Mörlein" <me@irrelefant.net>, "Simon Wunderlich" <sw@simonwunderlich.de>, "Sven Eckelmann" <sven@narfation.org>
Message-ID: <20211120123939.260723-3-sven@narfation.org>

From: Linus Lüssing <linus.luessing@c0d3.blue>

commit a44ebeff6bbd6ef50db41b4195fca87b21aefd20 upstream.

When a (broken) node wrongly sends multicast TT entries with a ROAM
flag then this causes any receiving node to drop all entries for the
same multicast MAC address announced by other nodes, leading to
packet loss.

Fix this DoS vector by only storing TT sync flags. For multicast TT
non-sync'ing flag bits like ROAM are unused so far anyway.

Fixes: 1d8ab8d3c176 ("batman-adv: Modified forwarding behaviour for multicast packets")
Reported-by: Leonardo Mörlein <me@irrelefant.net>
Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>
[ bp: 4.4 backported: adjust context, use old style to access flags ]
Signed-off-by: Sven Eckelmann <sven@narfation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 net/batman-adv/translation-table.c |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

--- a/net/batman-adv/translation-table.c
+++ b/net/batman-adv/translation-table.c
@@ -1426,7 +1426,8 @@ static bool batadv_tt_global_add(struct
 		ether_addr_copy(common->addr, tt_addr);
 		common->vid = vid;
 
-		common->flags = flags & (~BATADV_TT_SYNC_MASK);
+		if (!is_multicast_ether_addr(common->addr))
+			common->flags = flags & (~BATADV_TT_SYNC_MASK);
 
 		tt_global_entry->roam_at = 0;
 		/* node must store current time in case of roaming. This is
@@ -1489,7 +1490,8 @@ static bool batadv_tt_global_add(struct
 		 * TT_CLIENT_WIFI, therefore they have to be copied in the
 		 * client entry
 		 */
-		tt_global_entry->common.flags |= flags & (~BATADV_TT_SYNC_MASK);
+		if (!is_multicast_ether_addr(common->addr))
+			tt_global_entry->common.flags |= flags & (~BATADV_TT_SYNC_MASK);
 
 		/* If there is the BATADV_TT_CLIENT_ROAM flag set, there is only
 		 * one originator left in the list and we previously received a


Patches currently in stable-queue which might be from sven@narfation.org are

queue-4.4/batman-adv-consider-fragmentation-for-needed_headroom.patch
queue-4.4/ath9k-fix-potential-interrupt-storm-on-queue-reset.patch
queue-4.4/batman-adv-set-.owner-to-this_module.patch
queue-4.4/batman-adv-mcast-fix-duplicate-mcast-packets-from-bla-backbone-to-mesh.patch
queue-4.4/batman-adv-fix-multicast-tt-issues-with-bogus-roam-flags.patch
queue-4.4/batman-adv-mcast-fix-duplicate-mcast-packets-in-bla-backbone-from-lan.patch
queue-4.4/batman-adv-reserve-needed_-room-for-fragments.patch
queue-4.4/net-batman-adv-fix-error-handling.patch
queue-4.4/batman-adv-keep-fragments-equally-sized.patch
queue-4.4/batman-adv-avoid-warn_on-timing-related-checks.patch
queue-4.4/batman-adv-prevent-duplicated-softif_vlan-entry.patch
queue-4.4/batman-adv-don-t-always-reallocate-the-fragmentation-skb-head.patch
queue-4.4/batman-adv-mcast-fix-duplicate-mcast-packets-in-bla-backbone-from-mesh.patch

  reply	other threads:[~2021-11-23 12:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20 12:39 [PATCH 4.4 00/11] batman-adv: Fixes for stable/linux-4.4.y Sven Eckelmann
2021-11-20 12:39 ` [PATCH 4.4 01/11] batman-adv: Keep fragments equally sized Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: Keep fragments equally sized" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 02/11] batman-adv: Fix multicast TT issues with bogus ROAM flags Sven Eckelmann
2021-11-23 12:42   ` gregkh [this message]
2021-11-20 12:39 ` [PATCH 4.4 03/11] batman-adv: Prevent duplicated softif_vlan entry Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: Prevent duplicated softif_vlan entry" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 04/11] batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 05/11] batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 06/11] batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 07/11] batman-adv: set .owner to THIS_MODULE Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: set .owner to THIS_MODULE" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 08/11] batman-adv: Consider fragmentation for needed_headroom Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: Consider fragmentation for needed_headroom" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 09/11] batman-adv: Reserve needed_*room for fragments Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: Reserve needed_*room for fragments" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 10/11] batman-adv: Don't always reallocate the fragmentation skb head Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: Don't always reallocate the fragmentation skb head" has been added to the 4.4-stable tree gregkh
2021-11-20 12:39 ` [PATCH 4.4 11/11] batman-adv: Avoid WARN_ON timing related checks Sven Eckelmann
2021-11-23 12:42   ` Patch "batman-adv: Avoid WARN_ON timing related checks" has been added to the 4.4-stable tree gregkh
2021-11-23 12:41 ` [PATCH 4.4 00/11] batman-adv: Fixes for stable/linux-4.4.y Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=163767136325592@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linus.luessing@c0d3.blue \
    --cc=me@irrelefant.net \
    --cc=stable-commits@vger.kernel.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).