From: Dominique Martinet <asmadeus@codewreck.org>
To: Jose R Rodriguez <jose.r.r@metztli.com>, oss-security@lists.openwall.com
Cc: Greg KH <greg@kroah.com>,
Edward Shishkin <edward.shishkin@gmail.com>,
Reiserfs Devel <reiserfs-devel@vger.kernel.org>
Subject: Re: [oss-security] NoisyTCP — CVE-2026-99288 (Was Re: [oss-security] Backports available - cBPF JIT spray hardening)
Date: Fri, 20 Nov 2026 09:45:22 +0900 [thread overview]
Message-ID: <av-YIntXr75-vmym@codewreck.org> (raw)
In-Reply-To: <49ce58fc228f99240f9c3658622ca2d6@metztli.com>
Hi Jose,
(not sure why this comes as a reply to the bpf hardening CVE..)
Jose R Rodriguez wrote on Thu, Nov 19, 2026 at 03:25:25PM -0800:
> Since the time of your comment I have been keeping up with reiser4 -enhanced
> 5.15 LTS build iterations -- with the latest being 5.15.224.
> Notwithstanding, 'NoisyTCP — CVE-2026-99288' came along and the latest
> 5.15.225 LTS iteration did not address the critical vulnerability. I have
> the 5.15 LTS kernel(s) deployed online and I got spooked. Accordingly, on a
> best effort basis, I backported the patch from upstream:
The patch "inet: reject unhashed sockets during established lookups"
marked as fixing this CVE already has been backported to older trees,
including 5.15 already and is in the 5.15.226-rc1 (which will likely be
released today (11/20) or tomorrow)
You can already pull the patch from
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
if you want to rebuild your own kernel early
OTOH if you want quick fixes it's best to upgrade to a newer release if
possible - except for embedded or platforms with specific hardware it's
generally not too hard to switch to the latest LTS.
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2026-11-20 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dzp2vbih7jcsxjmcnxnefgi435b7re4kwxvxmvlxrmkra2p5br@vv5ckstkijym>
[not found] ` <14ad9b085cb3fb4b3a9fc091dde74540@metztli.com>
[not found] ` <6mqqzqzujeduybqeojfh7tmblksmqjksocri5ayeudze6l4fqm@ijx64jfxrwbt>
[not found] ` <2026073004-spruce-clambake-1785@gregkh>
2026-11-19 23:25 ` NoisyTCP — CVE-2026-99288 (Was Re: [oss-security] Backports available - cBPF JIT spray hardening) Jose R Rodriguez
2026-11-20 0:45 ` Dominique Martinet [this message]
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=av-YIntXr75-vmym@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=edward.shishkin@gmail.com \
--cc=greg@kroah.com \
--cc=jose.r.r@metztli.com \
--cc=oss-security@lists.openwall.com \
--cc=reiserfs-devel@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.