Lines Matching refs:bug

3 Before reporting a bug make sure nobody else already reported it. The easiest way to do this is to …
7 Make sure to mention the exact kernel branch and revision where the bug occured.
11 If the bug is reproducible, include the reproducer (C source if possible, otherwise a syzkaller pro…
15 …ate the reproducer manually, that greatly helps kernel developers to figure out why the bug occurs.
17 If you want to get extra credit, you can try to undestand the bug and develop a fix yourself.
18 If you can't figure out the right fix, but have some understanding of the bug, please add your thou…
22 If you believe that a found bug poses potential security threat, consider following the instruction…
28 1. Report the bug privately to `security@kernel.org`. In this case it should be fixed in the upstre…
29 2. Report the bug privately to a vendor such as Red Hat (`secalert@redhat.com`) or SUSE (`security@…
30 3. Report the bug publicly to `oss-security@lists.openwall.com`.
45 1. Report the bug publicly to kernel developers as described above and wait until a fix is committe…
46 2. Request a CVE from MITRE through [the web form](https://cveform.mitre.org/). Describe the bug de…
47 3. Once a CVE is assigned, send the bug details, the CVE number and a link to the fix to `oss-secur…
53 1. Understand the bug and develop a patch with a fix if possible. Optionally develop a proof-of-con…