Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
	binutils@sourceware.org, gdb@sourceware.org
Subject: Sourceware server reboots for Copy Fail CVE-2026-31431
Date: Fri, 1 May 2026 21:24:30 +0200	[thread overview]
Message-ID: <20260501192430.GU11304@gnu.wildebeest.org> (raw)

Hi all,

Because of a local privilege escalation vulnerability in the linux
kernel (Copy Fail CVE-2026-31431) we have been updating kernel
packages (for Debian and Fedora Core OS) and installing band-aids [1]
on various servers/vms. Which required reboots. We will likely have to
reboot some servers/vms again in the coming days. Apologies for the
disruption.

See https://sourceware.org/sourceware-wiki/servers-and-services-2026/
for the various servers, vms and services.

Thanks to Claudio and Frank for helping run the update scripts and/or
installing the security band-aids.

Cheers,

Mark

[1] https://sourceware.org/cgit/systemtap/tree/testsuite/systemtap.examples/security-band-aids/cve-2026-31431.stp

                 reply	other threads:[~2026-05-01 19:28 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=20260501192430.GU11304@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=overseers@sourceware.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