security contact

Most active threads (last 7 days)

Recent patches

Latest 23 postings or standalone patches, newest first. Counts below cover matching patches in linux-doc touching this subsystem.

• security-bugs doc updates v1 · 9 matching patches

  Entire posting: PENDING · 11 of 14 reviewed Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH 01/14] docs: security-bugs: reorganize the document without changing its contents 2026-11-09
  • [PATCH 03/14] docs: security-bugs: never publish reproducers of bugs with a security impact 2026-11-09
  • [PATCH 05/14] docs: security-bugs: explain how to send a fix that can be applied 2026-11-09
  • [PATCH 06/14] docs: security-bugs: do not send archives or binary attachments 2026-11-09
  • [PATCH 07/14] docs: security-bugs: first-time reporters must send a single report first 2026-11-09
  • [PATCH 08/14] docs: security-bugs: explain what to do when a report gets no response 2026-11-09
  • [PATCH 09/14] docs: security-bugs: reports left unanswered for 7 days will be dropped 2026-11-09
  • [PATCH 11/14] docs: security-bugs: explain why directly sent reports add extra work 2026-11-09
  • [PATCH 12/14] docs: security-bugs: explain why AI-found bugs are handled publicly 2026-11-09
  2026-11-09 · Willy Tarreau <w@1wt.eu>
• REVIEWED · 1 review, 1 by a maintainer [PATCH 10/14] docs: security-bugs: add a section for maintainers receiving reports 2026-11-09 · Willy Tarreau <w@1wt.eu>
• REVIEWED · 1 review, 1 by a maintainer [PATCH 02/14] docs: security-bugs: clarify when to Cc the security team 2026-11-09 · Willy Tarreau <w@1wt.eu>
• docs: improve guidance for AI-assisted bug reports v1 · 2 matching patches

  Entire posting: LANDED Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH 3/5] docs: security-bugs: clarify what counts as a valid version 2026-08-02
  • [PATCH 5/5] docs: security-bugs: clarify some mandatory steps for AI reports 2026-08-02
  2026-08-02 · Willy Tarreau <w@1wt.eu>
• REVIEWED · 2 reviews, 2 by maintainers [PATCH AUTOSEL 7.0] Documentation: security-bugs: do not systematically Cc the security team 2026-05-20 · Sasha Levin <sashal@kernel.org>
• Documentation: security-bugs: new updates covering triage and AI v3 · 3 matching patches

  Entire posting: LANDED Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH v3 1/3] Documentation: security-bugs: do not systematically Cc the security team 2026-05-09
  • [PATCH v3 2/3] Documentation: security-bugs: explain what is and is not a security bug 2026-05-09
  • [PATCH v3 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports 2026-05-09
  2026-05-09 · Willy Tarreau <w@1wt.eu>
• Documentation: security-bugs: new updates covering triage and AI v2 · 3 matching patches

  Entire posting: SUPERSEDED Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH v2 1/3] Documentation: security-bugs: do not systematically Cc the security team 2026-05-03
  • [PATCH v2 2/3] Documentation: security-bugs: explain what is and is not a security bug 2026-05-03
  • [PATCH v2 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports 2026-05-03
  2026-05-03 · Willy Tarreau <w@1wt.eu>
• Documentation: security-bugs: new updates covering triage and AI v1 · 3 matching patches

  Entire posting: SUPERSEDED Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH 1/3] Documentation: security-bugs: do not systematically Cc the security team 2026-04-26
  • [PATCH 2/3] Documentation: security-bugs: explain what is and is not a security bug 2026-04-26
  • [PATCH 3/3] Documentation: security-bugs: clarify requirements for AI-assisted reports 2026-04-26
  2026-04-26 · Willy Tarreau <w@1wt.eu>
• Documentation: clarify required info in security reports v2 · 3 matching patches

  Entire posting: LANDED Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH v2 1/3] Documentation: minor updates to the security contacts 2026-04-03
  • [PATCH v2 2/3] Documentation: explain how to find maintainers addresses for security reports 2026-04-03
  • [PATCH v2 3/3] Documentation: clarify the mandatory and desirable info for security reports 2026-04-03
  2026-04-03 · Willy Tarreau <w@1wt.eu>
• Documentation: clarify required info in security reports v1 · 3 matching patches

  Entire posting: SUPERSEDED Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH 1/3] Documentation: minor updates to the security contacts 2026-04-02
  • [PATCH 2/3] Documentation: explain how to find maintainers addresses for security reports 2026-04-02
  • [PATCH 3/3] Documentation: clarify the mandatory and desirable info for security reports 2026-04-02
  2026-04-02 · Willy Tarreau <w@1wt.eu>
• LANDED [PATCH] Documentation: insist on the plain-text requirement for security reports 2025-11-29 · Willy Tarreau <w@1wt.eu>
• LANDED [PATCH 2/2] Documentation: smooth the text flow in the security bug reporting process 2025-08-14 · Willy Tarreau <w@1wt.eu>
• LANDED [PATCH 1/2] Documentation: clarify the expected collaboration with security bugs reporters 2025-08-14 · Willy Tarreau <w@1wt.eu>
• LANDED · 4 reviews, 3 by maintainers [PATCH v5] Documentation: Document the Linux Kernel CVE process 2024-02-17 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• REVIEWED · 4 reviews, 3 by maintainers [PATCH v4] Documentation: Document the Linux Kernel CVE process 2024-02-15 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• REVIEWED · 1 review, 1 by a maintainer [PATCH v3] Documentation: Document the Linux Kernel CVE process 2024-02-14 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• REVIEWED · 1 review, 1 by a maintainer [PATCH v2] Documentation: Document the Linux Kernel CVE process 2024-02-14 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• [PATCH] Documentation: Document the Linux Kernel CVE process 2024-02-13 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• LANDED · 1 review, 1 by a maintainer [PATCH] Documentation: security-bugs.rst: linux-distros relaxed their rules 2023-10-15 · Willy Tarreau <w@1wt.eu>
• [RFC PATCH] Documentation: security-bugs.rst: linux-distros relaxed their rules 2023-10-07 · Willy Tarreau <w@1wt.eu>
• LANDED [PATCH 1/2] Documentation: security-bugs.rst: update preferences when dealing with the linux-distros group 2023-06-30 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• LANDED [PATCH 2/2] Documentation: security-bugs.rst: clarify CVE handling 2023-06-30 · Greg Kroah-Hartman <gregkh@linuxfoundation.org>
• Documentation/security-bugs: overhaul v3 · 7 matching patches

  Entire posting: PENDING · 1 of 7 landed Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH v3 1/7] Documentation/security-bugs: move from admin-guide/ to process/ 2023-03-05
  • [PATCH v3 2/7] Documentation/security-bugs: misc. improvements 2023-03-05
  • [PATCH v3 3/7] Documentation/security-bugs: improve security list section 2023-03-05
  • [PATCH v3 4/7] Documentation/security-bugs: add linux-distros and oss-security sections 2023-03-05
  • [PATCH v3 5/7] Documentation/security-bugs: add table of lists 2023-03-05
  • [PATCH v3 6/7] Documentation/security-bugs: clarify hardware vs. software vulnerabilities 2023-03-05
  • [PATCH v3 7/7] Documentation/security-bugs: document document design 2023-03-05
  2023-03-05 · Vegard Nossum <hidden>