[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130207.233107.1094455509765442729.davem@davemloft.net>
Date: Thu, 07 Feb 2013 23:31:07 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: Ian.Campbell@...rix.com
Cc: netdev@...r.kernel.org, xen-devel@...ts.xen.org
Subject: Re: [PATCH v2 0/4] XSA-39 CVE-2013-021[67]: Linux netback DoS via
malicious guest ring.
From: Ian Campbell <Ian.Campbell@...rix.com>
Date: Thu, 7 Feb 2013 09:41:18 +0000
> The Xen netback implementation contains a couple of flaws which can
> allow a guest to cause a DoS in the backend domain, potentially
> affecting other domains in the system.
>
> CVE-2013-0216 is a failure to sanity check the ring producer/consumer
> pointers which can allow a guest to cause netback to loop for an
> extended period preventing other work from occurring.
>
> CVE-2013-0217 is a memory leak on an error path which is guest
> triggerable.
>
> The following series contains the fixes for these issues, as previously
> included in Xen Security Advisory 39:
> http://lists.xen.org/archives/html/xen-announce/2013-02/msg00001.html
>
> Changes in v2:
> - Typo and block comment format fixes
> - Added stable Cc
Applied, please don't add stable CC:'s to networking patches, instead
ask me to queue it up to my -stable todo pile instead.
I don't like it when patches instantly be submitted to -stable when
they hit Linus's tree, I'd rather it soak upstream for a week or two
instead. That's why I do it this way.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists