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-72230: batman-adv: frag: free unfragmentable packet
Date: Sat, 15 Aug 2026 15:05:09 +0900	[thread overview]
Message-ID: <2026081549-CVE-2026-72230-a67b@gregkh> (raw)

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

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

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

batman-adv: frag: free unfragmentable packet

The caller of batadv_frag_send_packet() assume that the skb provided to the
function are always consumed. But the pre-check for an empty payload or the
zero fragment size returned an error without any further actions.

A failed pre-check must use the same error handling code as the rest of the
function.

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


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

	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 5.10.261 with commit a5155aeeae8ead3c6081f7f197608033e4dcfe75
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 5.15.212 with commit 04ccbed8179e7d4d0906d00939300ddc5b48ce7e
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 6.1.178 with commit 601dff01a03ecced59938cdd69eeb2c66e4158f2
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 6.6.145 with commit 740542f11bf8c86411c429fbd7f84fc6bee80e76
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 6.12.97 with commit 59e1da1ab354d1f2b7bab8d44f846262f990ad9d
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 6.18.40 with commit 8f54162e07d3eea1e4ff21464cf2a815d79b6510
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 7.1.5 with commit 08047838817561cef33ada9774a2a4663d499ecb
	Issue introduced in 3.13 with commit ee75ed88879af88558818a5c6609d85f60ff0df4 and fixed in 7.2-rc3 with commit 6b628425aed49a1c7a4ffc997583840fc582d32b

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-72230
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/fragmentation.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/a5155aeeae8ead3c6081f7f197608033e4dcfe75
	https://git.kernel.org/stable/c/04ccbed8179e7d4d0906d00939300ddc5b48ce7e
	https://git.kernel.org/stable/c/601dff01a03ecced59938cdd69eeb2c66e4158f2
	https://git.kernel.org/stable/c/740542f11bf8c86411c429fbd7f84fc6bee80e76
	https://git.kernel.org/stable/c/59e1da1ab354d1f2b7bab8d44f846262f990ad9d
	https://git.kernel.org/stable/c/8f54162e07d3eea1e4ff21464cf2a815d79b6510
	https://git.kernel.org/stable/c/08047838817561cef33ada9774a2a4663d499ecb
	https://git.kernel.org/stable/c/6b628425aed49a1c7a4ffc997583840fc582d32b

                 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-72230-a67b@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.