From: Sasha Levin <sashal@kernel.org>
To: Loic <hackurx@opensec.fr>
Cc: stable@vger.kernel.org, colin.king@canonical.com,
alexander.h.duyck@intel.com, aaron.f.brown@intel.com,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH] e1000: avoid null pointer dereference on invalid stat type
Date: Sat, 17 Nov 2018 09:37:56 -0500 [thread overview]
Message-ID: <20181117143756.GP1706@sasha-vm> (raw)
In-Reply-To: <20181109141706.044436edb88f95b9aacc7cb3@opensec.fr>
On Fri, Nov 09, 2018 at 02:17:06PM +0100, Loic wrote:
>Hello,
>
>Please picked up this patch for linux 4.4 and 4.9.
>Compiled/tested without problem.
>
>Thank.
>
>[ Upstream commit 5983587c8c5ef00d6886477544ad67d495bc5479 ]
>
>From: Colin Ian King <colin.king@canonical.com>
>Date: Fri, 22 Sep 2017 18:13:48 +0100
>Subject: [PATCH] e1000: avoid null pointer dereference on invalid stat type
>
>Currently if the stat type is invalid then data[i] is being set
>either by dereferencing a null pointer p, or it is reading from
>an incorrect previous location if we had a valid stat type
>previously. Fix this by skipping over the read of p on an invalid
>stat type.
>
>Detected by CoverityScan, CID#113385 ("Explicit null dereferenced")
>
>Signed-off-by: Colin Ian King <colin.king@canonical.com>
>Reviewed-by: Alexander Duyck <alexander.h.duyck@intel.com>
>Tested-by: Aaron Brown <aaron.f.brown@intel.com>
>Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Queued for 4.9 and 4.4, thank you.
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-18 0:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 13:17 [PATCH] e1000: avoid null pointer dereference on invalid stat type Loic
2018-11-17 14:37 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-21 22:01 Colin King
2017-09-21 22:01 ` Colin King
2017-09-22 11:50 ` Dan Carpenter
2017-09-22 11:50 ` Dan Carpenter
2017-09-22 11:55 ` Colin Ian King
2017-09-22 11:55 ` Colin Ian King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181117143756.GP1706@sasha-vm \
--to=sashal@kernel.org \
--cc=aaron.f.brown@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=colin.king@canonical.com \
--cc=hackurx@opensec.fr \
--cc=jeffrey.t.kirsher@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.