From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core205, created. 1cd0abd563f6945e24cf9c8e837b6c0165ba420c
Date: Mon, 02 Nov 2026 10:53:59 +0000 (UTC) [thread overview]
Message-ID: <4jJ7qX02LSz2xM1@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, core205 has been created
at 1cd0abd563f6945e24cf9c8e837b6c0165ba420c (commit)
- Log -----------------------------------------------------------------
commit 1cd0abd563f6945e24cf9c8e837b6c0165ba420c
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Nov 2 10:53:03 2026 +0000
make.sh: Start Core Update 205
This update only ships the new kernel as an emergency update to fix a
crash in the Broadcom driver and CVE-2026-98432, a use-after-free
vulnerability in the TCP stack.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
commit 2c192dfd39e49b0ac56517f0a4bbcbf00cab1b8d
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Mon Nov 2 10:53:03 2026 +0000
kernel: update to 6.18.60
This is an emergency update that fixes two serious problems:
* CVE-2026-98432: A use-after-free vulnerability in the TCP stack
* A crash in the Broadcom network driver, fixed upstream in
https://git.ipfire.org/?p=thirdparty/kernel/stable.git;a=commitdiff;h=fbd977e513971ccb4f0762a7f59eac500e474f89
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-11-02 10:54 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=4jJ7qX02LSz2xM1@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox