All of lore.kernel.org
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: davem@davemloft.net, gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "net: Zero terminate ifr_name in dev_ifname()." has been added to the 4.9-stable tree
Date: Tue, 08 Aug 2017 16:29:52 -0700	[thread overview]
Message-ID: <150223499218142@kroah.com> (raw)


This is a note to let you know that I've just added the patch titled

    net: Zero terminate ifr_name in dev_ifname().

to the 4.9-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     net-zero-terminate-ifr_name-in-dev_ifname.patch
and it can be found in the queue-4.9 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


>From foo@baz Tue Aug  8 16:27:53 PDT 2017
From: "David S. Miller" <davem@davemloft.net>
Date: Wed, 19 Jul 2017 13:33:24 -0700
Subject: net: Zero terminate ifr_name in dev_ifname().

From: "David S. Miller" <davem@davemloft.net>


[ Upstream commit 63679112c536289826fec61c917621de95ba2ade ]

The ifr.ifr_name is passed around and assumed to be NULL terminated.

Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 net/core/dev_ioctl.c |    1 +
 1 file changed, 1 insertion(+)

--- a/net/core/dev_ioctl.c
+++ b/net/core/dev_ioctl.c
@@ -28,6 +28,7 @@ static int dev_ifname(struct net *net, s
 
 	if (copy_from_user(&ifr, arg, sizeof(struct ifreq)))
 		return -EFAULT;
+	ifr.ifr_name[IFNAMSIZ-1] = 0;
 
 	error = netdev_get_name(net, ifr.ifr_name, ifr.ifr_ifindex);
 	if (error)


Patches currently in stable-queue which might be from davem@davemloft.net are

queue-4.9/ipv4-ipv6-initialize-treq-txhash-in-cookie_v_check.patch
queue-4.9/openvswitch-fix-potential-out-of-bound-access-in-parse_ct.patch
queue-4.9/ipv6-don-t-increase-ipstats_mib_fragfails-twice-in-ip6_fragment.patch
queue-4.9/sctp-don-t-dereference-ptr-before-leaving-_sctp_walk_-params-errors.patch
queue-4.9/net-ethernet-nb8800-handle-all-4-rgmii-modes-identically.patch
queue-4.9/sctp-fix-the-check-for-_sctp_walk_params-and-_sctp_walk_errors.patch
queue-4.9/packet-fix-use-after-free-in-prb_retire_rx_blk_timer_expired.patch
queue-4.9/rtnetlink-allocate-more-memory-for-dev_set_mac_address.patch
queue-4.9/tcp_bbr-remove-sk_pacing_rate-0-transient-during-init.patch
queue-4.9/tcp_bbr-introduce-bbr_bw_to_pacing_rate-helper.patch
queue-4.9/sparc64-measure-receiver-forward-progress-to-avoid-send-mondo-timeout.patch
queue-4.9/sparc64-fix-exception-handling-in-ultrasparc-iii-memcpy.patch
queue-4.9/dccp-fix-a-memleak-that-dccp_ipv6-doesn-t-put-reqsk-properly.patch
queue-4.9/tcp_bbr-introduce-bbr_init_pacing_rate_from_rtt-helper.patch
queue-4.9/sparc64-prevent-perf-from-running-during-super-critical-sections.patch
queue-4.9/net-dsa-b53-add-missing-arl-entries-for-bcm53125.patch
queue-4.9/dccp-fix-a-memleak-that-dccp_ipv4-doesn-t-put-reqsk-properly.patch
queue-4.9/mcs7780-fix-initialization-when-config_vmap_stack-is-enabled.patch
queue-4.9/net-zero-terminate-ifr_name-in-dev_ifname.patch
queue-4.9/tcp_bbr-init-pacing-rate-on-first-rtt-sample.patch
queue-4.9/net-phy-correctly-process-phy_halted-in-phy_stop_machine.patch
queue-4.9/ipv6-avoid-overflow-of-offset-in-ip6_find_1stfragopt.patch
queue-4.9/xen-netback-correctly-schedule-rate-limited-queues.patch
queue-4.9/dccp-fix-a-memleak-for-dccp_feat_init-err-process.patch
queue-4.9/ipv4-initialize-fib_trie-prior-to-register_netdev_notifier-call.patch
queue-4.9/tcp_bbr-cut-pacing-rate-only-if-filled-pipe.patch

                 reply	other threads:[~2017-08-08 23:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=150223499218142@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=stable-commits@vger.kernel.org \
    --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.