On Thu, 2018-05-03 at 00:06 +0100, Dominic Hargreaves wrote:
> On Tue, May 01, 2018 at 05:12:02PM +0000, Ben Hutchings wrote:
> > -------------------------------------------------------------------------
> > Debian Security Advisory DSA-4187-1                   secur...@debian.org
> > https://www.debian.org/security/                            Ben Hutchings
> > May 01, 2018                          https://www.debian.org/security/faq
> > -------------------------------------------------------------------------
> > 
> > Package        : linux
> > CVE ID         : CVE-2015-9016 CVE-2017-0861 CVE-2017-5715 CVE-2017-5753
> >                  CVE-2017-13166 CVE-2017-13220 CVE-2017-16526 CVE-2017-16911
> >                  CVE-2017-16912 CVE-2017-16913 CVE-2017-16914 CVE-2017-18017
> >                  CVE-2017-18203 CVE-2017-18216 CVE-2017-18232 CVE-2017-18241
> >                  CVE-2018-1066 CVE-2018-1068 CVE-2018-1092 CVE-2018-5332
> >                  CVE-2018-5333 CVE-2018-5750 CVE-2018-5803 CVE-2018-6927
> >                  CVE-2018-7492 CVE-2018-7566 CVE-2018-7740 CVE-2018-7757
> >                  CVE-2018-7995 CVE-2018-8781 CVE-2018-8822 CVE-2018-1000004
> >                  CVE-2018-1000199
> > 
> > Several vulnerabilities have been discovered in the Linux kernel that
> > may lead to a privilege escalation, denial of service or information
> > leaks.
> 
> There are multiple reports on #ganeti that this update breaks networking
> in certain circumstances, probably multiple tun/tap device configurations.
> No more details or a proper bug report yet as I haven't experienced this
> myself, but mentioning in case it saves anyone else breakage.[...]

I believe I understand this. Creating a tun/tap device using a name
pattern such as "tun%d" (or empty name) will now fail if the number
substituted is not 0.  There is an upstream fix for this that I failed
to spot in time.

Ben.

-- 
Ben Hutchings - Debian developer, member of kernel, installer and LTS teams

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to