view Documentation/SecurityBugs @ 452:c7ed6fe5dca0

kexec: dont initialise regions in reserve_memory()

There is no need to initialise efi_memmap_res and boot_param_res in
reserve_memory() for the initial xen domain as it is done in
machine_kexec_setup_resources() using values from the kexec hypercall.

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