From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99760: batman-adv: tt: ignore ROAM flag of received ADD changes
Date: Fri, 20 Nov 2026 06:52:26 +0100 [thread overview]
Message-ID: <2026112024-CVE-2026-99760-4ff9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: tt: ignore ROAM flag of received ADD changes
A received TT change (OGM diff or full table response) with the ROAM flag
but without DEL is handled by batadv_tt_global_add() like a ROAMING_ADV:
* a newly created global entry gets BATADV_TT_CLIENT_ROAM and is
therefore excluded from the global CRC. The sender has it in its local
CRC and the receiver has to request the full table again
* batadv_tt_global_purge_local() removes the local entry of the
receiver. The receiver's own client is considered as roamed to the sender
and frames for it are rerouted
The ROAM flag only has a meaning together with DEL. Drop it on reception to
keep it from populating the global table with a temporary ROAMING entry
which is not part of the CRC - and therefore causing a CRC mismatch.
The Linux kernel CVE team has assigned CVE-2026-99760 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.8 with commit 068ee6e204e1f48ba24ec91ce40f5ca833a57a81 and fixed in 6.12.118 with commit 06d1e0a779c823c9299a1a59e882365732faa48d
Issue introduced in 3.8 with commit 068ee6e204e1f48ba24ec91ce40f5ca833a57a81 and fixed in 6.18.64 with commit 08eef283c81a11da88d1159c17336c40d1834a42
Issue introduced in 3.8 with commit 068ee6e204e1f48ba24ec91ce40f5ca833a57a81 and fixed in 7.3.5 with commit 1654eeaccde3bc9fd71b6b316bcc8eb6f4f9c012
Issue introduced in 3.8 with commit 068ee6e204e1f48ba24ec91ce40f5ca833a57a81 and fixed in 7.4-rc2 with commit c5d68abe6e7f1dbd132a602cb696fe1fff0389eb
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-99760
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/06d1e0a779c823c9299a1a59e882365732faa48d
https://git.kernel.org/stable/c/08eef283c81a11da88d1159c17336c40d1834a42
https://git.kernel.org/stable/c/1654eeaccde3bc9fd71b6b316bcc8eb6f4f9c012
https://git.kernel.org/stable/c/c5d68abe6e7f1dbd132a602cb696fe1fff0389eb
reply other threads:[~2026-11-20 6:03 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=2026112024-CVE-2026-99760-4ff9@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.