From: Dominique Martinet <asmadeus@codewreck.org>
To: jan.kiszka@siemens.com
Cc: Pavel Machek <pavel@nabladev.com>,
Masami Ichikawa <masami.ichikawa@miraclelinux.com>,
cip-dev <cip-dev@lists.cip-project.org>,
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.x90@mail.toshiba>,
Ulrich Hecht <uli@fpond.eu>
Subject: Re: [cip-dev] CVE-2026-99288: Re: [kernel-cve-report] New CVE entries this week
Date: Wed, 18 Nov 2026 15:19:43 +0900 [thread overview]
Message-ID: <av1Dfxc5tjypOTpl@codewreck.org> (raw)
In-Reply-To: <63257a1a-dcbd-46ea-958d-fd4fc876cd2e@siemens.com>
Just drive-by comment as I was looking as this earlier today,
(hi & thanks for the work!)
Jan Kiszka via cip-dev wrote on Wed, Nov 18, 2026 at 07:09:08AM +0100:
> > I tried to do a quick research, and this seems to be more of server
> > issue, and may be hard/impossible to exploit in embedded
> > systems. Researcher's writeup seems to be at
> > https://github.com/V4bel/NoisyTCP . Quoting "so it can be triggered
> > against servers that have two or more RX queues, or where RPS
> > distributes packets across multiple CPUs."
>
> Just to be clear: We have server-like scenarios in scope as well.
> "Embedded" does not imply a specific size of the system or performance.
(FWIW we have some embedded boards with 3-4 queues on imx7d / imx8mp at
least; OTOH this seems very hard to hit in practice so I'm treating this
as low-ish priority at $job ( https://www.atmark-techno.com/ ))
> > sudo sysctl -w net.ipv4.tcp_syncookies=0 was cited as possible
> > workaround.
> >
> > If someone believes their machine are in danger, please let us know.
> >
> > We could do 6.12-cip fairly easily, older would be more tricky as
> > there was no suitable -stable release. But I don't think this is "as
> > bad" as bugs we did extra releases for.
>
> Can we support on this, or is this ongoing work already (<6.12)?
There are patches available as far back as 5.10 in the stable-queue repo:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue
I didn't check if the 5.10 patch can be picked up further easily, but
that's one less to do/some conflicts already resolved.
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2026-11-18 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 23:56 [kernel-cve-report] New CVE entries this week Masami Ichikawa
2026-11-16 19:17 ` Jan Kiszka
2026-11-17 21:26 ` CVE-2026-99288: " Pavel Machek
2026-11-18 6:09 ` Jan Kiszka
2026-11-18 6:19 ` Dominique Martinet [this message]
2026-11-18 6:23 ` nobuhiro.iwamatsu.x90
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=av1Dfxc5tjypOTpl@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@miraclelinux.com \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
--cc=uli@fpond.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox