€•FŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ)/translations/zh_CN/process/security-bugs”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ)/translations/zh_TW/process/security-bugs”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ)/translations/it_IT/process/security-bugs”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ)/translations/ja_JP/process/security-bugs”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ)/translations/ko_KR/process/security-bugs”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ)/translations/sp_SP/process/security-bugs”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒtarget”“”)”}”(hŒ.. _securitybugs:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œ securitybugs”uh1h¡h KhhhžhhŸŒC/var/lib/git/docbuild/linux/Documentation/process/security-bugs.rst”ubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ Security bugs”h]”hŒ Security bugs”…””}”(hh·hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhh²hžhhŸh¯h KubhŒ paragraph”“”)”}”(hŒì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.”h]”hŒî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.”…””}”(hhÇhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Khh²hžhubh±)”}”(hhh]”(h¶)”}”(hŒContact”h]”hŒContact”…””}”(hhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhhÕhžhhŸh¯h K ubhÆ)”}”(hX¸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.”h]”(hŒ=The Linux kernel security team can be contacted by email at <”…””}”(hhæhžhhŸNh NubhŒ reference”“”)”}”(hŒsecurity@kernel.org”h]”hŒsecurity@kernel.org”…””}”(hhðhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:security@kernel.org”uh1hîhhæubhXh>. 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.”…””}”(hhæhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubhÆ)”}”(hXtAs 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.”h]”hXxAs 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.”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubhÆ)”}”(hXªPlease send plain text emails without attachments where possible. It is much harder to have a context-quoted discussion about a complex issue if all the details are hidden away in attachments. Think of it like a :doc:`regular patch submission <../process/submitting-patches>` (even if you don't have a patch yet): describe the problem and impact, list reproduction steps, and follow it with a proposed fix, all in plain text.”h]”(hŒÕPlease send plain text emails without attachments where possible. It is much harder to have a context-quoted discussion about a complex issue if all the details are hidden away in attachments. Think of it like a ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ?:doc:`regular patch submission <../process/submitting-patches>`”h]”hŒinline”“”)”}”(hj"h]”hŒregular patch submission”…””}”(hj&hžhhŸNh Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-doc”eh"]”h$]”h&]”uh1j$hj ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œprocess/security-bugs”Œ refdomain”j1Œreftype”Œdoc”Œ refexplicit”ˆŒrefwarn”ˆŒ reftarget”Œ../process/submitting-patches”uh1hhŸh¯h KhjubhŒ˜ (even if you don’t have a patch yet): describe the problem and impact, list reproduction steps, and follow it with a proposed fix, all in plain text.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KhhÕhžhubeh}”(h]”Œcontact”ah ]”h"]”Œcontact”ah$]”h&]”uh1h°hh²hžhhŸh¯h K ubh±)”}”(hhh]”(h¶)”}”(hŒ$Disclosure and embargoed information”h]”hŒ$Disclosure and embargoed information”…””}”(hjZhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjWhžhhŸh¯h K%ubhÆ)”}”(hŒQThe security list is not a disclosure channel. For that, see Coordination below.”h]”hŒQThe security list is not a disclosure channel. For that, see Coordination below.”…””}”(hjhhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K'hjWhžhubhÆ)”}”(hŒzOnce a robust fix has been developed, the release process starts. Fixes for publicly known bugs are released immediately.”h]”hŒzOnce a robust fix has been developed, the release process starts. Fixes for publicly known bugs are released immediately.”…””}”(hjvhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K*hjWhžhubhÆ)”}”(hX Although our preference is to release fixes for publicly undisclosed bugs as soon as they become available, this may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, with an exceptional extension to 14 calendar days if it is agreed that the criticality of the bug requires more time. The only valid reason for deferring the publication of a fix is to accommodate the logistics of QA and large scale rollouts which require release coordination.”h]”hX Although our preference is to release fixes for publicly undisclosed bugs as soon as they become available, this may be postponed at the request of the reporter or an affected party for up to 7 calendar days from the start of the release process, with an exceptional extension to 14 calendar days if it is agreed that the criticality of the bug requires more time. The only valid reason for deferring the publication of a fix is to accommodate the logistics of QA and large scale rollouts which require release coordination.”…””}”(hj„hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K-hjWhžhubhÆ)”}”(hX|While embargoed information may be shared with trusted individuals in order to develop a fix, such information will not be published alongside the fix or on any other disclosure channel without the permission of the reporter. This includes but is not limited to the original bug report and followup discussions (if any), exploits, CVE information or the identity of the reporter.”h]”hX|While embargoed information may be shared with trusted individuals in order to develop a fix, such information will not be published alongside the fix or on any other disclosure channel without the permission of the reporter. This includes but is not limited to the original bug report and followup discussions (if any), exploits, CVE information or the identity of the reporter.”…””}”(hj’hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K6hjWhžhubhÆ)”}”(hŒíIn other words our only interest is in getting bugs fixed. All other information submitted to the security list and any followup discussions of the report are treated confidentially even after the embargo has been lifted, in perpetuity.”h]”hŒíIn other words our only interest is in getting bugs fixed. All other information submitted to the security list and any followup discussions of the report are treated confidentially even after the embargo has been lifted, in perpetuity.”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h K=hjWhžhubeh}”(h]”Œ$disclosure-and-embargoed-information”ah ]”h"]”Œ$disclosure and embargoed information”ah$]”h&]”uh1h°hh²hžhhŸh¯h K%ubh±)”}”(hhh]”(h¶)”}”(hŒCoordination with other groups”h]”hŒCoordination with other groups”…””}”(hj¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhj¶hžhhŸh¯h KCubhÆ)”}”(hXºWhile the kernel security team solely focuses on getting bugs fixed, other groups focus on fixing issues in distros and coordinating disclosure between operating system vendors. Coordination is usually handled by the "linux-distros" mailing list and disclosure by the public "oss-security" mailing list, both of which are closely related and presented in the linux-distros wiki: ”h]”(hX…While the kernel security team solely focuses on getting bugs fixed, other groups focus on fixing issues in distros and coordinating disclosure between operating system vendors. Coordination is usually handled by the “linux-distros†mailing list and disclosure by the public “oss-security†mailing list, both of which are closely related and presented in the linux-distros wiki: <”…””}”(hjÇhžhhŸNh Nubhï)”}”(hŒ”…””}”(hjÇhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KEhj¶hžhubhÆ)”}”(hXµPlease note that the respective policies and rules are different since the 3 lists pursue different goals. Coordinating between the kernel security team and other teams is difficult since for the kernel security team occasional embargoes (as subject to a maximum allowed number of days) start from the availability of a fix, while for "linux-distros" they start from the initial post to the list regardless of the availability of a fix.”h]”hX¹Please note that the respective policies and rules are different since the 3 lists pursue different goals. Coordinating between the kernel security team and other teams is difficult since for the kernel security team occasional embargoes (as subject to a maximum allowed number of days) start from the availability of a fix, while for “linux-distros†they start from the initial post to the list regardless of the availability of a fix.”…””}”(hjèhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KMhj¶hžhubhÆ)”}”(hX As such, the kernel security team strongly recommends that as a reporter of a potential security issue you DO NOT contact the "linux-distros" mailing list UNTIL a fix is accepted by the affected code's maintainers and you have read the distros wiki page above and you fully understand the requirements that contacting "linux-distros" will impose on you and the kernel community. This also means that in general it doesn't make sense to Cc: both lists at once, except maybe for coordination if and while an accepted fix has not yet been merged. In other words, until a fix is accepted do not Cc: "linux-distros", and after it's merged do not Cc: the kernel security team.”h]”hX²As such, the kernel security team strongly recommends that as a reporter of a potential security issue you DO NOT contact the “linux-distros†mailing list UNTIL a fix is accepted by the affected code’s maintainers and you have read the distros wiki page above and you fully understand the requirements that contacting “linux-distros†will impose on you and the kernel community. This also means that in general it doesn’t make sense to Cc: both lists at once, except maybe for coordination if and while an accepted fix has not yet been merged. In other words, until a fix is accepted do not Cc: “linux-distrosâ€, and after it’s merged do not Cc: the kernel security team.”…””}”(hjöhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KUhj¶hžhubeh}”(h]”Œcoordination-with-other-groups”ah ]”h"]”Œcoordination with other groups”ah$]”h&]”uh1h°hh²hžhhŸh¯h KCubh±)”}”(hhh]”(h¶)”}”(hŒCVE assignment”h]”hŒCVE assignment”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhj hžhhŸh¯h KaubhÆ)”}”(hXGThe security team does not assign CVEs, nor do we require them for reports or fixes, as this can needlessly complicate the process and may delay the bug handling. If a reporter wishes to have a CVE identifier assigned for a confirmed issue, they can contact the :doc:`kernel CVE assignment team<../process/cve>` to obtain one.”h]”(hXThe security team does not assign CVEs, nor do we require them for reports or fixes, as this can needlessly complicate the process and may delay the bug handling. If a reporter wishes to have a CVE identifier assigned for a confirmed issue, they can contact the ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ1:doc:`kernel CVE assignment team<../process/cve>`”h]”j%)”}”(hj'h]”hŒkernel CVE assignment team”…””}”(hj)hžhhŸNh Nubah}”(h]”h ]”(j0Œstd”Œstd-doc”eh"]”h$]”h&]”uh1j$hj%ubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j=Œ refdomain”j3Œreftype”Œdoc”Œ refexplicit”ˆŒrefwarn”ˆjCŒ../process/cve”uh1hhŸh¯h KchjubhŒ to obtain one.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h Kchj hžhubeh}”(h]”Œcve-assignment”ah ]”h"]”Œcve assignment”ah$]”h&]”uh1h°hh²hžhhŸh¯h Kaubh±)”}”(hhh]”(h¶)”}”(hŒNon-disclosure agreements”h]”hŒNon-disclosure agreements”…””}”(hjZhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hµhjWhžhhŸh¯h KjubhÆ)”}”(hŒpThe Linux kernel security team is not a formal body and therefore unable to enter any non-disclosure agreements.”h]”hŒpThe Linux kernel security team is not a formal body and therefore unable to enter any non-disclosure agreements.”…””}”(hjhhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhŸh¯h KlhjWhžhubeh}”(h]”Œnon-disclosure-agreements”ah ]”h"]”Œnon-disclosure agreements”ah$]”h&]”uh1h°hh²hžhhŸh¯h Kjubeh}”(h]”(Œ security-bugs”h®eh ]”h"]”(Œ security bugs”Œ securitybugs”eh$]”h&]”uh1h°hhhžhhŸh¯h KŒexpect_referenced_by_name”}”j„h£sŒexpect_referenced_by_id”}”h®h£subeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¯uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hµNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j®Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¯Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”h®]”h£asŒnameids”}”(j„h®jƒj€jTjQj³j°j jjTjQj{jxuŒ nametypes”}”(j„ˆjƒ‰jT‰j³‰j ‰jT‰j{‰uh}”(h®h²j€h²jQhÕj°jWjj¶jQj jxjWuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”hŒsystem_message”“”)”}”(hhh]”hÆ)”}”(hhh]”hŒ2Hyperlink target "securitybugs" is not referenced.”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”uh1hÅhjubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h¯Œline”Kuh1jubaŒ transformer”NŒ include_log”]”Œ decoration”Nhžhub.