CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Pavel Machek <pavel@nabladev.com>
Cc: 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: CVE-2026-99288: Re: [kernel-cve-report] New CVE entries this week
Date: Wed, 18 Nov 2026 07:09:08 +0100	[thread overview]
Message-ID: <63257a1a-dcbd-46ea-958d-fd4fc876cd2e@siemens.com> (raw)
In-Reply-To: <avzGdm2kkPzk8cLD@duo.ucw.cz>

On 17.11.26 22:26, Pavel Machek wrote:
> Hi!
> 
>>> CVE-2026-99288: inet: reject unhashed sockets during established lookups
>>>
>>> Announce: https://www.cve.org/CVERecord?id=CVE-2026-99288
>>>
>>> Introduced commit is not determined.
>>> Introduced by 079096f ("tcp/dccp: install syn_recv requests into ehash
>>> table") in v4.4-rc1.
>>>
>>> Fixed status
>>> mainline: [4e2b3ef19e0e04adca38442f07dd6bc93c712bf1]
>>> stable/6.12: [d69100340b4cae08d40f898f1b601032403f6be6]
>>> stable/6.18: [8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd]
>>> stable/7.3: [eb8a2d156f2c1d862fffdfd1b3432bfbcd939879]
>>>
>>
>> This one is gaining attention now ("NoisyTCP") because it allows remote
>> DoS in default configurations. Score: 7.5. Are handling this
>> specifically already?
> 
> 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.

> 
> 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)?

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

  reply	other threads:[~2026-11-18  6:09 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 [this message]
2026-11-18  6:19       ` [cip-dev] " Dominique Martinet
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=63257a1a-dcbd-46ea-958d-fd4fc876cd2e@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --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