All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99588: batman-adv: tt: only update flags for TT events
Date: Fri, 20 Nov 2026 06:49:34 +0100	[thread overview]
Message-ID: <2026112021-CVE-2026-99588-ce5d@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

batman-adv: tt: only update flags for TT events

In the first implementation of the translation table events, it was only
possible to announce:

* ADD: new locally detected client
* DEL: disappeared local client

If an ADD event was queued and then a DEL event was queued in the same
timeslot, it is valid to destroy both events because nothing actually
changed for remode nodes

But with commit 3c4f7ab60cc2 ("batman-adv: improve the TT component to
support runtime flag changes") and subsequent changes, it could also happen
that there are extra ADD events:

* ADD: _NEW_ locally detected client
* ADD: already existing client with new flags
* DEL: disappeared local client

The first and the last type of event could in theory still be removed
together from the (to be announced) events queue. But if the "update flags"
ADD is dropped together with the DEL, it would still leave global
translation table of a remote node in the incorrect state - believing that
the client didn't disappear.

If a detected client was previously announced, a DEL event must only
overwrite the "update flags" ADD but the DEL itself must still continue to
exist in the (to be anounced) events queue. For now, adjustment of the
announced flags is used for everything instead of dropping already queued
up events completely.

Similarly, a DEL followed by an ADD caused both entries to be deleted. But
the new ADD could announce flags changes which were not yet present for the
client before it was marked for DELetion. The new ADD must therefore only
overwrite the DEL - but still be kept.

The Linux kernel CVE team has assigned CVE-2026-99588 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.13 with commit 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee and fixed in 6.12.118 with commit 92fb8f25fee4c8820b54a18f694b74b3adb79f34
	Issue introduced in 3.13 with commit 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee and fixed in 6.18.64 with commit 4cec0f6207e551ec4081e84a37918060dd2b51a7
	Issue introduced in 3.13 with commit 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee and fixed in 7.3.5 with commit 326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe
	Issue introduced in 3.13 with commit 3c4f7ab60cc21e8fc65b234f3a6174fc19a93fee and fixed in 7.4-rc2 with commit ad1fd828aa3944efc393b84b0d7c02483f1b5638

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-99588
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	net/batman-adv/translation-table.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/92fb8f25fee4c8820b54a18f694b74b3adb79f34
	https://git.kernel.org/stable/c/4cec0f6207e551ec4081e84a37918060dd2b51a7
	https://git.kernel.org/stable/c/326bea8dbc9dc741a39c33b4a8cb6ce07dc4cdbe
	https://git.kernel.org/stable/c/ad1fd828aa3944efc393b84b0d7c02483f1b5638

                 reply	other threads:[~2026-11-20  5:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2026112021-CVE-2026-99588-ce5d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.