From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72232: batman-adv: ensure minimal ethernet header on TX
Date: Sat, 15 Aug 2026 15:05:11 +0900 [thread overview]
Message-ID: <2026081549-CVE-2026-72232-a293@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: ensure minimal ethernet header on TX
As documented in commit 8bd67ebb50c0 ("net: bridge: xmit: make sure we have
at least eth header len bytes"), it is possible by for a local user with
eBPF TC hook access to attach a tc filter which truncates the packet and
redirects to an batadv interface. But the code assumes that at least
ETH_HLEN bytes are available and thus might read outside of the available
buffer.
The batadv_interface_tx() must therefore always check itself if enough data
is available for the ethernet header and don't rely on min_header_len.
The Linux kernel CVE team has assigned CVE-2026-72232 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 5.10.261 with commit 58799078afebd5115e052bf69ad6697f9759dd6f
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 5.15.212 with commit 38cd10b0aeec755d89f78722a2b83f4088ff0cb0
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 6.1.178 with commit 811fea37620f2097955d95ce81cfdba03fd30f1b
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 6.6.145 with commit e6640923afee619d9fa82b07394dc9498e202304
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 6.12.97 with commit 6b4f521e01257387906f8b969ad3450d8208d4e2
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 6.18.40 with commit 9e16b6751a8206de0b865d99bb02771e6751d12d
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 7.1.5 with commit dbeb4145d9778f922f459935da9a027750765a69
Issue introduced in 2.6.38 with commit c6c8fea29769d998d94fcec9b9f14d4b52b349d3 and fixed in 7.2-rc3 with commit 49df66b7993c80b80c7eb9a84ba5b3410c8296a0
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-72232
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/mesh-interface.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/58799078afebd5115e052bf69ad6697f9759dd6f
https://git.kernel.org/stable/c/38cd10b0aeec755d89f78722a2b83f4088ff0cb0
https://git.kernel.org/stable/c/811fea37620f2097955d95ce81cfdba03fd30f1b
https://git.kernel.org/stable/c/e6640923afee619d9fa82b07394dc9498e202304
https://git.kernel.org/stable/c/6b4f521e01257387906f8b969ad3450d8208d4e2
https://git.kernel.org/stable/c/9e16b6751a8206de0b865d99bb02771e6751d12d
https://git.kernel.org/stable/c/dbeb4145d9778f922f459935da9a027750765a69
https://git.kernel.org/stable/c/49df66b7993c80b80c7eb9a84ba5b3410c8296a0
reply other threads:[~2026-08-15 6:17 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=2026081549-CVE-2026-72232-a293@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.