linux-kernel - Re: ixgbe: fix potential null dereference

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: <CAKocOON0V3WGLPpdVAq_9+o9GT=kJ192wywsS_m_yNTMKcUTow@mail.gmail.com>
Date:	Thu, 21 Feb 2013 10:42:53 -0700
From:	Shuah Khan <shuahkhan@...il.com>
To:	jeffrey.t.kirsher@...el.com, joshua.a.hay@...el.com,
	phillip.j.schmitt@...el.com
Cc:	stable <stable@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: ixgbe: fix potential null dereference

On Wed, Feb 20, 2013 at 8:32 PM, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org> wrote:
> Gitweb:     http://git.kernel.org/linus/;a=commit;h=f752be9c3de4fbb6a9b2c060f3794bd928a0ad7a
> Commit:     f752be9c3de4fbb6a9b2c060f3794bd928a0ad7a
> Parent:     07ce870bed2f631ad53a2c1a90db20b5f8126ab9
> Author:     Josh Hay <joshua.a.hay@...el.com>
> AuthorDate: Fri Jan 4 03:34:36 2013 +0000
> Committer:  Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> CommitDate: Tue Feb 5 01:43:49 2013 -0800
>
>     ixgbe: fix potential null dereference
>
>     This patch adds a default case which goes to the next loop iteration
>     in the case where p is not set, preventing p from being dereferenced.
>
>     Signed-off-by: Josh Hay <joshua.a.hay@...el.com>
>     Tested-by: Phil Schmitt <phillip.j.schmitt@...el.com>
>     Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> ---

Jeff/Josh,

Should this patch be considered for stable release 3.7 and 3.4. It
applied cleanly to both of these releases. I haven't tested it yet
though.

-- Shuah
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/