1Linux kernel developers take security very seriously. As such, we'd 2like to know when a security bug is found so that it can be fixed and 3disclosed as quickly as possible. Please report security bugs to the 4Linux kernel security team. 5 61) Contact 7 8The Linux kernel security team can be contacted by email at 9<security@kernel.org>. This is a private list of security officers 10who will help verify the bug report and develop and release a fix. 11It is possible that the security team will bring in extra help from 12area maintainers to understand and fix the security vulnerability. 13 14As it is with any bug, the more information provided the easier it 15will be to diagnose and fix. Please review the procedure outlined in 16REPORTING-BUGS if you are unclear about what information is helpful. 17Any exploit code is very helpful and will not be released without 18consent from the reporter unless it has already been made public. 19 202) Disclosure 21 22The goal of the Linux kernel security team is to work with the 23bug submitter to bug resolution as well as disclosure. We prefer 24to fully disclose the bug as soon as possible. It is reasonable to 25delay disclosure when the bug or the fix is not yet fully understood, 26the solution is not well-tested or for vendor coordination. However, we 27expect these delays to be short, measurable in days, not weeks or months. 28A disclosure date is negotiated by the security team working with the 29bug submitter as well as vendors. However, the kernel security team 30holds the final say when setting a disclosure date. The timeframe for 31disclosure is from immediate (esp. if it's already publically known) 32to a few weeks. As a basic default policy, we expect report date to 33disclosure date to be on the order of 7 days. 34 353) Non-disclosure agreements 36 37The Linux kernel security team is not a formal body and therefore unable 38to enter any non-disclosure agreements. 39