From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72349: netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt()
Date: Sat, 15 Aug 2026 15:07:08 +0900 [thread overview]
Message-ID: <2026081511-CVE-2026-72349-bef4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfilter: xt_rateest: fix u64 truncation in xt_rateest_mt()
On links faster than ~34 Gbps, where byte rate may exceed 2^32-1
(~ 4.3 GBps), the comparison result becomes incorrect because the
truncated value no longer reflects the actual estimator rate.
Fix by changing the local variables to u64.
The Linux kernel CVE team has assigned CVE-2026-72349 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 5.10.261 with commit 77e9ba358d63fe2eb03c90d29ea85651d95cf2e6
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 5.15.212 with commit a3ba938f45cb00f6bf49d3aa3647df9b017f5f08
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 6.1.178 with commit bab305dd769d78074adca73505cc2509e1206bf2
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 6.6.145 with commit 5da915fc159c6b4091669447588e520183969cca
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 6.12.97 with commit d5cc4c12a4b90bf099199c3c49ecda7e694f2a2b
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 6.18.40 with commit e702f6dd5d21e331f55fd9168c0210542008546d
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 7.1.5 with commit 905a927b2e6fec7b174e9e5644d271047b61378f
Issue introduced in 4.10 with commit 1c0d32fde5bdf1184bc274f864c09799278a1114 and fixed in 7.2-rc3 with commit 444853cd438201007da5359821adcc2995655ab1
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-72349
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/netfilter/xt_rateest.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/77e9ba358d63fe2eb03c90d29ea85651d95cf2e6
https://git.kernel.org/stable/c/a3ba938f45cb00f6bf49d3aa3647df9b017f5f08
https://git.kernel.org/stable/c/bab305dd769d78074adca73505cc2509e1206bf2
https://git.kernel.org/stable/c/5da915fc159c6b4091669447588e520183969cca
https://git.kernel.org/stable/c/d5cc4c12a4b90bf099199c3c49ecda7e694f2a2b
https://git.kernel.org/stable/c/e702f6dd5d21e331f55fd9168c0210542008546d
https://git.kernel.org/stable/c/905a927b2e6fec7b174e9e5644d271047b61378f
https://git.kernel.org/stable/c/444853cd438201007da5359821adcc2995655ab1
reply other threads:[~2026-08-15 6:23 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=2026081511-CVE-2026-72349-bef4@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.