From nobody Sun Jun 14 12:44:00 2026 Received: from mta1.formilux.org (mta1.formilux.org [51.159.59.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F052F26980F; Fri, 3 Apr 2026 06:20:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=51.159.59.229 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775197232; cv=none; b=RN/rh7hby59RsJ52WwyDDZcQZw/917/htkCAPaxuqIY257TTecEzashjzEQeHgHxZj55lEaXKZLyQQyAOQyjoWJXWwTEkpjB515lcCvoCiy32EfntsgH/R5S0nzP0cwH6KzqxgZeWwNd0v5nfeaxEBpmBMLVwIQCOV4/vSHRRQw= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775197232; c=relaxed/simple; bh=lYbGhSOqqQUEwZE0acX2UVUvqowOH0oH6Xm9dt/EAm8=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=tssSBgPti/W58Vya1y69sm8iRZ3YRSAtUxGw75Yn72TeES69/fQzo93+tIKOQ8Xv26GSd/Fre9bDt5nMsVOZForm4RtzUdnnX//jFAv0JBKM1xWq9VTkDcOXlcwnHMqbBwmI+W11YpJesa9vodqr7IX3deQb3YIqcv3OZ2dvUU8= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu; spf=pass smtp.mailfrom=1wt.eu; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b=SLhQCJSo; arc=none smtp.client-ip=51.159.59.229 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=1wt.eu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b="SLhQCJSo" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1wt.eu; s=mail; t=1775197220; bh=FV+TU1qQ5cdhGH80pRimkZ1mbKexd6nCcdrKQzpzcW0=; h=From:Message-ID:From; b=SLhQCJSoX4BpEWe2oExGeo6SGZIA992pHUJw+I67U2nX8pdpdqa/nWuLx7rzijd76 bTRJ8z40PXO8O8B3MG+29DijDwpJOedeVzLUQbuXSeRXHWvrKGqAvgWofTPGc8XaGQ /XnLxWAIr7y7vaOXPGY4/CSbsIlJsdVtcfHyilf8= Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by mta1.formilux.org (Postfix) with ESMTP id 229CFC0AAF; Fri, 03 Apr 2026 08:20:20 +0200 (CEST) From: Willy Tarreau To: greg@kroah.com Cc: edumazet@google.com, rdunlap@infradead.org, Jonathan Corbet , skhan@linuxfoundation.org, workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Willy Tarreau Subject: [PATCH v2 1/3] Documentation: minor updates to the security contacts Date: Fri, 3 Apr 2026 08:20:16 +0200 Message-ID: <20260403062018.31080-2-w@1wt.eu> X-Mailer: git-send-email 2.52.0 In-Reply-To: <20260403062018.31080-1-w@1wt.eu> References: <20260403062018.31080-1-w@1wt.eu> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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 Cc: Greg KH Signed-off-by: Willy Tarreau --- Documentation/process/security-bugs.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/Documentation/process/security-bugs.rst b/Documentation/proces= s/security-bugs.rst index c0cf93e11565..da7937fd59df 100644 --- a/Documentation/process/security-bugs.rst +++ b/Documentation/process/security-bugs.rst @@ -8,6 +8,10 @@ like to know when a security bug is found so that it can b= e fixed and disclosed as quickly as possible. Please report security bugs to the Linux kernel security team. =20 +Reports are to be sent over e-mail exclusively. Please use a working e-ma= il +address, preferably the same that you want to appear in ``Reported-by`` ta= gs +if any. If unsure, send your report to yourself first. + The security team and maintainers almost always require additional information beyond what was initially provided in a report and rely on active and efficient collaboration with the reporter to perform further @@ -27,11 +31,9 @@ made public. =20 The Linux kernel security team can be contacted by email at . This is a private list of security officers -who will help verify the bug report and develop and release a fix. -If you already have a fix, please include it with your report, as -that can speed up the process considerably. It is possible that the -security team will bring in extra help from area maintainers to -understand and fix the security vulnerability. +who will help verify the bug report and assist developers working on a fix. +It is possible that the security team will bring in extra help from area +maintainers to understand and fix the security vulnerability. =20 Please send **plain text** emails without attachments where possible. It is much harder to have a context-quoted discussion about a complex --=20 2.52.0 From nobody Sun Jun 14 12:44:00 2026 Received: from mta1.formilux.org (mta1.formilux.org [51.159.59.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6BCE9366079; Fri, 3 Apr 2026 06:20:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=51.159.59.229 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775197246; cv=none; b=mfpFEVEyoy+yBNKkBDKwl20ZrOsb0X9lWy7HkMLGZeKW3b7nKb1A2ub7kz+6WMPM7XW5wxBJOYkGAJQ9j8yAukCNLvvzzqYs7zRW2DMuPmzBg/7gaO/9T6Kt32Vth7287W9+fTQbHq0csrLyYbfd/gMB4/RVm+AVfFOJavxsScI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775197246; c=relaxed/simple; bh=CX5fvbfdCr2+GmJiW78tpM7ubdGx/BZsicNUbEJ1hy4=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=Mg/nAcMEEY7JtNuqaUnTIk9Dg2jDh81Wgus74qg5JEd9y8U+/bikayQmf7vL56brSeT8sI6drHIwqqn86lvjZYzNnDnOnZFktrD4vHXzlPbbvvEQn0fsjG/GQs6pQqwZg0gKJf6IYcJ8TD28zQAiXGJ6nCza3bgZ5/sMYQXIo3o= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu; spf=pass smtp.mailfrom=1wt.eu; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b=Py6ooHAG; arc=none smtp.client-ip=51.159.59.229 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=1wt.eu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b="Py6ooHAG" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1wt.eu; s=mail; t=1775197236; bh=Wd/ig26Ooqk3eYbA7Ljsc6Wa5J1s4tW85iBVUTwDQHs=; h=From:Message-ID:From; b=Py6ooHAGz18jknl2utaJqYU/QJTcyA3XuzRSg1CfDAWVHJ5AnagcyNVJwnCD1tV3X vWH0H2fRbXv+gVJyWCZhadJVCu2X5PdfVAVnHlN0f6d97MvypeZ1fEdjeXm7WjmWfm zGvYm0XJkdcN+/MsVP6hTmc5Kiwhomisbmig2nlw= Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by mta1.formilux.org (Postfix) with ESMTP id 01ADDC0AAF; Fri, 03 Apr 2026 08:20:36 +0200 (CEST) From: Willy Tarreau To: greg@kroah.com Cc: edumazet@google.com, rdunlap@infradead.org, Jonathan Corbet , skhan@linuxfoundation.org, workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Willy Tarreau Subject: [PATCH v2 2/3] Documentation: explain how to find maintainers addresses for security reports Date: Fri, 3 Apr 2026 08:20:17 +0200 Message-ID: <20260403062018.31080-3-w@1wt.eu> X-Mailer: git-send-email 2.52.0 In-Reply-To: <20260403062018.31080-1-w@1wt.eu> References: <20260403062018.31080-1-w@1wt.eu> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" These days, 80% of the work done by the security team consists in locating the affected subsystem in a report, running get_maintainers on it, forwarding the report to these persons and responding to the reporter with them in Cc. This is a huge and unneeded overhead that we must try to lower for a better overall efficiency. This patch adds a complete section explaining how to figure the list of recipients to send the report to. Cc: Eric Dumazet Cc: Greg KH Signed-off-by: Willy Tarreau Reviewed-by: Kees Cook --- Documentation/process/security-bugs.rst | 76 ++++++++++++++++++++++++- 1 file changed, 73 insertions(+), 3 deletions(-) diff --git a/Documentation/process/security-bugs.rst b/Documentation/proces= s/security-bugs.rst index da7937fd59df..ac97fc78fecd 100644 --- a/Documentation/process/security-bugs.rst +++ b/Documentation/process/security-bugs.rst @@ -5,8 +5,75 @@ Security bugs =20 Linux kernel developers take security very seriously. As such, we'd like to know when a security bug is found so that it can be fixed and -disclosed as quickly as possible. Please report security bugs to the -Linux kernel security team. +disclosed as quickly as possible. + +Identifying contacts +-------------------- + +The most effective way to report a security bug is to send it directly to = the +affected subsystem's maintainers and Cc: the Linux kernel security team. = Do +not send it to a public list at this stage, unless you have good reasons to +consider the issue as being public or trivial to discover (e.g. result of a +widely available automated vulnerability scanning tool that can be repeate= d by +anyone). + +If you're sending a report for issues affecting multiple parts in the kern= el, +even if they're fairly similar issues, please send individual messages (th= ink +that maintainers will not all work on the issues at the same time). The on= ly +exception is when an issue concerns closely related parts maintained by the +exact same subset of maintainers, and these parts are expected to be fixed= all +at once by the same commit, then it may be acceptable to report them at on= ce. + +One difficulty for most first-time reporters is to figure the right list of +recipients to send a report to. In the Linux kernel, all official maintai= ners +are trusted, so the consequences of accidentally including the wrong maint= ainer +are essentially a bit more noise for that person, i.e. nothing dramatic. = As +such, a suitable method to figure the list of maintainers (which kernel +security officers use) is to rely on the get_maintainers.pl script, tuned = to +only report maintainers. This script, when passed a file name, will look = for +its path in the MAINTAINERS file to figure a hierarchical list of relevant +maintainers. Calling it a first time with the finest level of filtering w= ill +most of the time return a short list of this specific file's maintainers:: + + $ ./scripts/get_maintainer.pl --no-l --no-r --pattern-depth 1 \ + drivers/example.c + Developer One (maintainer:example driver) + Developer Two (maintainer:example driver) + +These two maintainers should then receive the message. If the command doe= s not +return anything, it means the affected file is part of a wider subsystem, = so we +should be less specific:: + + $ ./scripts/get_maintainer.pl --no-l --no-r drivers/example.c + Developer One (maintainer:example subsystem) + Developer Two (maintainer:example subsystem) + Developer Three (maintainer:example subsystem [GENERA= L]) + Developer Four (maintainer:example subsystem [GENERAL= ]) + +Here, picking the first, most specific ones, is sufficient. When the list= is +long, it is possible to produce a comma-delimited e-mail address list on a +single line suitable for use in the To: field of a mailer like this:: + + $ ./scripts/get_maintainer.pl --no-tree --no-l --no-r --no-n --m \ + --no-git-fallback --no-substatus --no-rolestats --no-multiline \ + --pattern-depth 1 drivers/example.c + dev1@example.com, dev2@example.org + +or this for the wider list:: + + $ ./scripts/get_maintainer.pl --no-tree --no-l --no-r --no-n --m \ + --no-git-fallback --no-substatus --no-rolestats --no-multiline \ + drivers/example.c + dev1@example.com, dev2@example.org, dev3@example.com, dev4@example.org + +If at this point you're still facing difficulties spotting the right +maintainers, **and only in this case**, it's possible to send your report = to +the Linux kernel security team only. Your message will be triaged, and you +will receive instructions about whom to contact, if needed. Your message = may +equally be forwarded as-is to the relevant maintainers. + +Sending the report +------------------ =20 Reports are to be sent over e-mail exclusively. Please use a working e-ma= il address, preferably the same that you want to appear in ``Reported-by`` ta= gs @@ -29,6 +96,7 @@ information is helpful. Any exploit code is very helpful= and will not be released without consent from the reporter unless it has already been made public. =20 +The report must be sent to maintainers, with the security team in ``Cc:``. The Linux kernel security team can be contacted by email at . This is a private list of security officers who will help verify the bug report and assist developers working on a fix. @@ -44,7 +112,9 @@ reproduction steps, and follow it with a proposed fix, a= ll in plain text. Markdown, HTML and RST formatted reports are particularly frowned upon sin= ce they're quite hard to read for humans and encourage to use dedicated viewe= rs, sometimes online, which by definition is not acceptable for a confidential -security report. +security report. Note that some mailers tend to mangle formatting of plain +text by default, please consult Documentation/process/email-clients.rst for +more info. =20 Disclosure and embargoed information ------------------------------------ --=20 2.52.0 From nobody Sun Jun 14 12:44:00 2026 Received: from mta1.formilux.org (mta1.formilux.org [51.159.59.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C864D374186; Fri, 3 Apr 2026 06:20:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=51.159.59.229 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775197255; cv=none; b=hE9+RVrGPfD6z6J07yxXgTrXRUVmJeQquTTE5k/DF7GuTbisY0ibikfRf5AtWbgo2COQ4NQuc82H8nXdo4RKsiZ2DffnS/vVezis1LqCf5cB2rAYbfydC0eQ83OPxF6uU+zz56vz0Mrn44suJa+8ErIv22AtU1Lbg5oobr6E6+w= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775197255; c=relaxed/simple; bh=n8LECQJ4x4kKLegzjCk6W2ZTgGIHzFc04My1vTX+7DQ=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=UMSsdNw64LFf3woEXLOzWkxRy9SgF7GAuulN1KJv3dKXKIF8T9ZTZwDgT54HHeduAve50ZkrI8mvh6UOVM4FNzhY2sKSPKv9cvCr252KRIeWnyHYRzfxaxf/hHxwQcHY5Z/iC1dbQp1WcnD//Ab9n2NosPIeP7Qi5cKqjG7yH3k= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu; spf=pass smtp.mailfrom=1wt.eu; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b=sw+dmHnL; arc=none smtp.client-ip=51.159.59.229 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=1wt.eu Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=1wt.eu Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=1wt.eu header.i=@1wt.eu header.b="sw+dmHnL" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1wt.eu; s=mail; t=1775197244; bh=6mMBFjBX7EcspuOEDXNCtlc+Rfv6QdGApiTNJWlPIec=; h=From:Message-ID:From; b=sw+dmHnLixyk6KSbg5AoMHrLV3AfL7HQAsqRXUqBY53dE0VHaeRTVo5xQH6Gwcaew 8Wyh+pHqGj6PBljj/xHvzF40yIkgOq45BGqaANtNPD6QTiY39atltqZlsWSAkK3X7L gP0FnlPP2vUByoS8/7A+bYW3HDa9jo16mJAd+pwo= Received: from 1wt.eu (ded1.1wt.eu [163.172.96.212]) by mta1.formilux.org (Postfix) with ESMTP id F0A14C0AB0; Fri, 03 Apr 2026 08:20:43 +0200 (CEST) From: Willy Tarreau To: greg@kroah.com Cc: edumazet@google.com, rdunlap@infradead.org, Jonathan Corbet , skhan@linuxfoundation.org, workflows@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Willy Tarreau Subject: [PATCH v2 3/3] Documentation: clarify the mandatory and desirable info for security reports Date: Fri, 3 Apr 2026 08:20:18 +0200 Message-ID: <20260403062018.31080-4-w@1wt.eu> X-Mailer: git-send-email 2.52.0 In-Reply-To: <20260403062018.31080-1-w@1wt.eu> References: <20260403062018.31080-1-w@1wt.eu> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" A significant part of the effort of the security team consists in begging reporters for patch proposals, or asking them to provide them in regular format, and most of the time they're willing to provide this, they just didn't know that it would help. So let's add a section detailing the required and desirable contents in a security report to help reporters write more actionable reports which do not require round trips. Cc: Eric Dumazet Cc: Greg KH Signed-off-by: Willy Tarreau --- Documentation/process/security-bugs.rst | 66 ++++++++++++++++++++++--- 1 file changed, 59 insertions(+), 7 deletions(-) diff --git a/Documentation/process/security-bugs.rst b/Documentation/proces= s/security-bugs.rst index ac97fc78fecd..0b1f6d8e3cbe 100644 --- a/Documentation/process/security-bugs.rst +++ b/Documentation/process/security-bugs.rst @@ -7,6 +7,65 @@ Linux kernel developers take security very seriously. As = such, we'd like to know when a security bug is found so that it can be fixed and disclosed as quickly as possible. =20 +Preparing your report +--------------------- + +Like with any bug report, a security bug report requires a lot of analysis= work +from the developers, so the more information you can share about the issue= , the +better. Please review the procedure outlined in +Documentation/admin-guide/reporting-issues.rst if you are unclear about wh= at +information is helpful. The following information are absolutely necessar= y in +**any** security bug report: + + * **affected kernel version range**: with no version indication, your re= port + will not be processed. A significant part of reports are for bugs that + have already been fixed, so it is extremely important that vulnerabili= ties + are verified on recent versions (development tree or latest stable + version), at least by verifying that the code has not changed since the + version where it was detected. + + * **description of the problem**: a detailed description of the problem,= with + traces showing its manifestation, and why you consider that the observ= ed + behavior as a problem in the kernel, is necessary. + + * **reproducer**: developers will need to be able to reproduce the probl= em to + consider a fix as effective. This includes both a way to trigger the = issue + and a way to confirm it happens. A reproducer with low complexity + dependencies will be needed (source code, shell script, sequence of + instructions, file-system image etc). Binary-only executables are not + accepted. Working exploits are extremely helpful and will not be rele= ased + without consent from the reporter, unless they are already public. By + definition if an issue cannot be reproduced, it is not exploitable, th= us it + is not a security bug. + + * **conditions**: if the bug depends on certain configuration options, + sysctls, permissions, timing, code modifications etc, these should be + indicated. + +In addition, the following information are highly desirable: + + * **suspected location of the bug**: the file names and functions where = the + bug is suspected to be present are very important, at least to help fo= rward + the report to the appropriate maintainers. When not possible (for exa= mple, + "system freezes each time I run this command"), the security team will= help + identify the source of the bug. + + * **a proposed fix**: bug reporters who have analyzed the cause of a bug= in + the source code almost always have an accurate idea on how to fix it, + because they spent a long time studying it and its implications. Prop= osing + a tested fix will save maintainers a lot of time, even if the fix ends= up + not being the right one, because it helps understand the bug. When + proposing a tested fix, please always format it in a way that can be + immediately merged (see Documentation/process/submitting-patches.rst). + This will save some back-and-forth exchanges if it is accepted, and you + will be credited for finding and fixing this issue. Note that in this= case + only a ``Signed-off-by:`` tag is needed, without ``Reported-by:` when = the + reporter and author are the same. + + * **mitigations**: very often during a bug analysis, some ways of mitiga= ting + the issue appear. It is useful to share them, as they can be helpful to + keep end users protected during the time it takes them to apply the fi= x. + Identifying contacts -------------------- =20 @@ -89,13 +148,6 @@ run additional tests. Reports where the reporter does = not respond promptly or cannot effectively discuss their findings may be abandoned if the communication does not quickly improve. =20 -As it is with any bug, the more information provided the easier it -will be to diagnose and fix. Please review the procedure outlined in -'Documentation/admin-guide/reporting-issues.rst' if you are unclear about = what -information is helpful. Any exploit code is very helpful and will not -be released without consent from the reporter unless it has already been -made public. - The report must be sent to maintainers, with the security team in ``Cc:``. The Linux kernel security team can be contacted by email at . This is a private list of security officers --=20 2.52.0