From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99762: batman-adv: mcast: validate tracker padding before forwarding
Date: Fri, 20 Nov 2026 06:52:28 +0100 [thread overview]
Message-ID: <2026112025-CVE-2026-99762-fdab@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: mcast: validate tracker padding before forwarding
A multicast tracker with an even number of destinations needs two
padding bytes after its destination list. batadv_mcast_forw_packet()
currently only checks that the count field and the addresses fit in
the tracker TVLV.
If an unpadded even tracker is compacted to an odd number of
destinations, batadv_mcast_forw_shrink_update_headers() includes those
missing padding bytes in the amount to remove. The subsequent memmove
can then write two bytes past the old packet tail. With no tailroom,
this corrupts skb_shared_info.
Include the required padding in the existing tracker length check.
This rejects the malformed tracker before either received or locally
generated packets can reach the compactor.
The Linux kernel CVE team has assigned CVE-2026-99762 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit 2dfe644a1ce017cacd449adabd68c3bc49199e11 and fixed in 6.12.118 with commit 441b922dd65fc50b9b32c2116c4058e96d0746c0
Issue introduced in 6.8 with commit 2dfe644a1ce017cacd449adabd68c3bc49199e11 and fixed in 6.18.64 with commit bc9419c51ec011447d63c5c262482d3a682f993a
Issue introduced in 6.8 with commit 2dfe644a1ce017cacd449adabd68c3bc49199e11 and fixed in 7.3.5 with commit dc52eedaf27cb9ca4f52202f391c1793c0c54eba
Issue introduced in 6.8 with commit 2dfe644a1ce017cacd449adabd68c3bc49199e11 and fixed in 7.4-rc2 with commit ea01fff30f631e67ee5f0a2b97855d772b3a35fc
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-99762
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/multicast_forw.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/441b922dd65fc50b9b32c2116c4058e96d0746c0
https://git.kernel.org/stable/c/bc9419c51ec011447d63c5c262482d3a682f993a
https://git.kernel.org/stable/c/dc52eedaf27cb9ca4f52202f391c1793c0c54eba
https://git.kernel.org/stable/c/ea01fff30f631e67ee5f0a2b97855d772b3a35fc
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=2026112025-CVE-2026-99762-fdab@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.