tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Documentation: minor updates to the security contacts

This clarifies the fact that the bug reporters must use a valid
e-mail address to send their report, and that the security team
assists developers working on a fix but doesn't always produce
fixes on its own.

Cc: Eric Dumazet <edumazet@google.com>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Willy Tarreau <w@1wt.eu>
Link: https://patch.msgid.link/20260403062018.31080-2-w@1wt.eu
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

authored by

Willy Tarreau and committed by
Greg Kroah-Hartman f2b1cbef d78ceee1

+7 -5
+7 -5
Documentation/process/security-bugs.rst
··· 8 8 disclosed as quickly as possible. Please report security bugs to the 9 9 Linux kernel security team. 10 10 11 + Reports are to be sent over e-mail exclusively. Please use a working e-mail 12 + address, preferably the same that you want to appear in ``Reported-by`` tags 13 + if any. If unsure, send your report to yourself first. 14 + 11 15 The security team and maintainers almost always require additional 12 16 information beyond what was initially provided in a report and rely on 13 17 active and efficient collaboration with the reporter to perform further ··· 31 27 32 28 The Linux kernel security team can be contacted by email at 33 29 <security@kernel.org>. This is a private list of security officers 34 - who will help verify the bug report and develop and release a fix. 35 - If you already have a fix, please include it with your report, as 36 - that can speed up the process considerably. It is possible that the 37 - security team will bring in extra help from area maintainers to 38 - understand and fix the security vulnerability. 30 + who will help verify the bug report and assist developers working on a fix. 31 + It is possible that the security team will bring in extra help from area 32 + maintainers to understand and fix the security vulnerability. 39 33 40 34 Please send **plain text** emails without attachments where possible. 41 35 It is much harder to have a context-quoted discussion about a complex