[engineering.redhat.com #494100] Question on submitting patch for a security bug

Red Hat Product Security secalert at redhat.com
Mon Aug 5 17:38:48 UTC 2019

Hello Navid,

On Thu, 18 Jul 2019 01:30:20 GMT, emamd001 at umn.edu wrote:
> I've found a null dereference bug in the Linux kernel source code. I was
> wondering should I cc the patch to you as well (along with the
> maintainers)?

No. Please do not cc <secalert at redhat.com> on the upstream kernel patches.
It is meant for reporting security issues only.

Going through the patches here

1. Issues in ../staging/ drivers are not considered for CVE, they are not to be
in production environment.

2. Many of the patches listed fix NULL pointer dereference when memory
fails and returns NULL.

3. Do you happen to have reproducers for these issues? Could an unprivileged
user trigger them?

> Also, I was wondering what are the steps to get CVE for the bug (this is
> the first time I am reporting a bug)?

Generally CVE is assigned after confirming that a given issue really is a
security issue. And it may
have impact ranging from information leakage, DoS to privilege escalation or
maybe arbitrary code
execution. Every NULL pointer dereference is not security issue.

Hope it helps. Thank you.
Prasad J Pandit / Red Hat Product Security Team

More information about the dri-devel mailing list