From: David Miller <davem@davemloft.net>
To: alban.browaeys@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: core: Fix slab-out-of-bounds in netdev_stats_to_stats64
Date: Mon, 03 Jul 2017 02:41:01 -0700 (PDT) [thread overview]
Message-ID: <20170703.024101.611675879403798301.davem@davemloft.net> (raw)
In-Reply-To: <20170703012013.4009-1-alban.browaeys@gmail.com>
From: Alban Browaeys <alban.browaeys@gmail.com>
Date: Mon, 3 Jul 2017 03:20:13 +0200
> commit 9256645af098 ("net/core: relax BUILD_BUG_ON in
> netdev_stats_to_stats64") made an attempt to read beyond
> the size of the source a possibility.
>
> Fix to only copy src size to dest. As dest might be bigger than src.
...
> Signed-off-by: Alban Browaeys <alban.browaeys@gmail.com>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2017-07-03 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 1:20 [PATCH] net: core: Fix slab-out-of-bounds in netdev_stats_to_stats64 Alban Browaeys
2017-07-03 9:41 ` David Miller [this message]
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=20170703.024101.611675879403798301.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alban.browaeys@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).