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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <rt-4.0.13-23214-1565026728-1358.494100-5-0@engineering.redhat.com>
Date:   Mon, 5 Aug 2019 13:38:48 -0400
From:   Red Hat Product Security <secalert@...hat.com>
To:     b.zolnierkie@...sung.com, bob.liu@...cle.com,
        chuck.lever@...cle.com, davem@...emloft.net, emamd001@....edu,
        gregkh@...uxfoundation.org, kubakici@...pl, kvalo@...eaurora.org,
        navid.emamdoost@...il.com, sam@...nborg.org
CC:     airlied@...ux.ie, alexandre.belloni@...tlin.com,
        alexandre.torgue@...com, allison@...utok.net,
        andriy.shevchenko@...ux.intel.com, anna.schumaker@...app.com,
        axboe@...nel.dk, bfields@...ldses.org, colin.king@...onical.com,
        daniel@...ll.ch, devel@...verdev.osuosl.org,
        dri-devel@...ts.freedesktop.org, joabreu@...opsys.com,
        johnfwhitmore@...il.com, josef@...icpanda.com, jslaby@...e.com,
        kjlu@....edu, kstewart@...uxfoundation.org,
        linux-arm-kernel@...ts.infradead.org, linux-block@...r.kernel.org,
        linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-mediatek@...ts.infradead.org, linux-nfs@...r.kernel.org,
        linux-serial@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-wireless@...r.kernel.org, matthias.bgg@...il.com,
        matthias@...hat.com, mcoquelin.stm32@...il.com,
        nbd@...er.debian.org, netdev@...r.kernel.org,
        nishkadg.linux@...il.com, peppe.cavallaro@...com, smccaman@....edu,
        tglx@...utronix.de, thierry.reding@...il.com,
        trond.myklebust@...merspace.com, unglinuxdriver@...rochip.com,
        vishal@...lsio.com, vkoul@...nel.org
Subject: [engineering.redhat.com #494100] Question on submitting patch for a security bug

Hello Navid,

On Thu, 18 Jul 2019 01:30:20 GMT, emamd001@....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@...hat.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
used
in production environment.

2. Many of the patches listed fix NULL pointer dereference when memory
allocation
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