From: Josh Law <hlcj1234567@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, objecting@objecting.org
Subject: Re: + lib-ts_kmp-fix-integer-overflow-in-pattern-length-calculation.patch added to mm-nonmm-unstable branch
Date: Mon, 9 Mar 2026 20:45:45 +0000 [thread overview]
Message-ID: <b1324259-8cad-4fef-94b9-2a72ac5e54f4@gmail.com> (raw)
In-Reply-To: <20260309134310.6036ef100f81a943f0fe6e2b@linux-foundation.org>
9 Mar 2026 20:43:11 Andrew Morton <akpm@linux-foundation.org>:
> On Mon, 9 Mar 2026 20:35:07 +0000 Josh Law <hlcj1234567@gmail.com> wrote:
>
>> Do you think these patches require Cc: stable?
>> Idk the severity of the bug to you, the swapped arguments got Cc stable, overflow could cause some screwy bugs
>
> Probably not - is there any reason to believe any callers will hit this?
I’ve been looking at the callers. While most are in-kernel constants, xt_string in Netfilter allows for dynamic patterns. Even if it's currently mitigated elsewhere, hardening the allocation logic in ts_bm and ts_kmp feels like a 'must-have' for stable trees to prevent future heap overflow vectors. Basically... Better safe than sorry!
V/R
Josh law
next prev parent reply other threads:[~2026-03-09 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 20:24 + lib-ts_kmp-fix-integer-overflow-in-pattern-length-calculation.patch added to mm-nonmm-unstable branch Andrew Morton
2026-03-09 20:35 ` Josh Law
2026-03-09 20:43 ` Andrew Morton
2026-03-09 20:45 ` Josh Law [this message]
2026-03-09 20:54 ` Josh Law
2026-03-09 21:47 ` Josh Law
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=b1324259-8cad-4fef-94b9-2a72ac5e54f4@gmail.com \
--to=hlcj1234567@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=objecting@objecting.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.