==========================================================================
Ubuntu Security Notice USN-3758-2
August 30, 2018
libx11 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 12.04 ESM
Summary:
Several security issues were fixed in libx11.
Software Description:
- libx11: X11 client-side library
Details:
USN-3758-1 fixed several vulnerabilities in libx11. This update
provides the corresponding update for Ubuntu 12.04 ESM.
Original advisory details:
Tobias Stoeckmann discovered that libx11 incorrectly handled certain
images. An attacker could possibly use this issue to access sensitive
information (CVE-2016-7942)
Tobias Stoeckmann discovered that libx11 incorrectly handled certain
inputs. An attacker could possibly use this issue to access sensitive
information. (CVE-2016-7943)
It was discovered that libx11 incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a denial of
service. (CVE-2018-14598, CVE-2018-14599, CVE-2018-14600)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 12.04 ESM:
libx11-6 2:1.4.99.1-0ubuntu2.4
libx11-dev 2:1.4.99.1-0ubuntu2.4
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://usn.ubuntu.com/usn/usn-3758-2
https://usn.ubuntu.com/usn/usn-3758-1
CVE-2016-7942, CVE-2016-7943, CVE-2018-14598, CVE-2018-14599,
CVE-2018-14600
Thursday, August 30, 2018
[USN-3758-1] libx11 vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3758-1
August 30, 2018
libx11 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in libx11.
Software Description:
- libx11: X11 client-side library
Details:
Tobias Stoeckmann discovered that libx11 incorrectly handled certain
images. An attacker could possibly use this issue to access sensitive
information (CVE-2016-7942)
Tobias Stoeckmann discovered that libx11 incorrectly handled certain
inputs. An attacker could possibly use this issue to access sensitive
information. (CVE-2016-7943)
It was discovered that libx11 incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2018-14598, CVE-2018-14599, CVE-2018-14600)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
libx11-6 2:1.6.4-3ubuntu0.1
libx11-dev 2:1.6.4-3ubuntu0.1
Ubuntu 16.04 LTS:
libx11-6 2:1.6.3-1ubuntu2.1
libx11-dev 2:1.6.3-1ubuntu2.1
Ubuntu 14.04 LTS:
libx11-6 2:1.6.2-1ubuntu2.1
libx11-dev 2:1.6.2-1ubuntu2.1
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://usn.ubuntu.com/usn/usn-3758-1
CVE-2016-7942, CVE-2016-7943, CVE-2018-14598, CVE-2018-14599,
CVE-2018-14600
Package Information:
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.3-1ubuntu2.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.2-1ubuntu2.1
Ubuntu Security Notice USN-3758-1
August 30, 2018
libx11 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in libx11.
Software Description:
- libx11: X11 client-side library
Details:
Tobias Stoeckmann discovered that libx11 incorrectly handled certain
images. An attacker could possibly use this issue to access sensitive
information (CVE-2016-7942)
Tobias Stoeckmann discovered that libx11 incorrectly handled certain
inputs. An attacker could possibly use this issue to access sensitive
information. (CVE-2016-7943)
It was discovered that libx11 incorrectly handled certain inputs.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2018-14598, CVE-2018-14599, CVE-2018-14600)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
libx11-6 2:1.6.4-3ubuntu0.1
libx11-dev 2:1.6.4-3ubuntu0.1
Ubuntu 16.04 LTS:
libx11-6 2:1.6.3-1ubuntu2.1
libx11-dev 2:1.6.3-1ubuntu2.1
Ubuntu 14.04 LTS:
libx11-6 2:1.6.2-1ubuntu2.1
libx11-dev 2:1.6.2-1ubuntu2.1
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://usn.ubuntu.com/usn/usn-3758-1
CVE-2016-7942, CVE-2016-7943, CVE-2018-14598, CVE-2018-14599,
CVE-2018-14600
Package Information:
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.3-1ubuntu2.1
https://launchpad.net/ubuntu/+source/libx11/2:1.6.2-1ubuntu2.1
Wednesday, August 29, 2018
[USN-3757-1] poppler vulnerability
==========================================================================
Ubuntu Security Notice USN-3757-1
August 29, 2018
poppler vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
poppler could be made to crash if it received specially crafted
PDF file.
Software Description:
- poppler: PDF rendering library
Details:
Hosein Askari discovered that poppler incorrectly handled certain PDF
files. An attacker could possible use this issue to cause a denial of
service.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
libpoppler73 0.62.0-2ubuntu2.2
poppler-utils 0.62.0-2ubuntu2.2
Ubuntu 16.04 LTS:
libpoppler58 0.41.0-0ubuntu1.8
poppler-utils 0.41.0-0ubuntu1.8
Ubuntu 14.04 LTS:
libpoppler44 0.24.5-2ubuntu4.12
poppler-utils 0.24.5-2ubuntu4.12
In general, a standard system update will make all the necessary
changes.
References:
https://usn.ubuntu.com/usn/usn-3757-1
CVE-2018-13988
Package Information:
https://launchpad.net/ubuntu/+source/poppler/0.62.0-2ubuntu2.2
https://launchpad.net/ubuntu/+source/poppler/0.41.0-0ubuntu1.8
https://launchpad.net/ubuntu/+source/poppler/0.24.5-2ubuntu4.12
Ubuntu Security Notice USN-3757-1
August 29, 2018
poppler vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
poppler could be made to crash if it received specially crafted
PDF file.
Software Description:
- poppler: PDF rendering library
Details:
Hosein Askari discovered that poppler incorrectly handled certain PDF
files. An attacker could possible use this issue to cause a denial of
service.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
libpoppler73 0.62.0-2ubuntu2.2
poppler-utils 0.62.0-2ubuntu2.2
Ubuntu 16.04 LTS:
libpoppler58 0.41.0-0ubuntu1.8
poppler-utils 0.41.0-0ubuntu1.8
Ubuntu 14.04 LTS:
libpoppler44 0.24.5-2ubuntu4.12
poppler-utils 0.24.5-2ubuntu4.12
In general, a standard system update will make all the necessary
changes.
References:
https://usn.ubuntu.com/usn/usn-3757-1
CVE-2018-13988
Package Information:
https://launchpad.net/ubuntu/+source/poppler/0.62.0-2ubuntu2.2
https://launchpad.net/ubuntu/+source/poppler/0.41.0-0ubuntu1.8
https://launchpad.net/ubuntu/+source/poppler/0.24.5-2ubuntu4.12
Tuesday, August 28, 2018
[USN-3752-3] Linux kernel (Azure, GCP, OEM) vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3752-3
August 28, 2018
linux-azure, linux-oem, linux-gcp vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux-azure: Linux kernel for Microsoft Azure Cloud systems
- linux-oem: Linux kernel for OEM processors
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
Details:
It was discovered that, when attempting to handle an out-of-memory
situation, a null pointer dereference could be triggered in the Linux
kernel in some circumstances. A local attacker could use this to cause a
denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate xattr information. An attacker could use
this to construct a malicious xfs image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed
data reported that it was in a ready state before it had gathered
sufficient entropy. An attacker could use this to expose sensitive
information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle
processes mapping some memory elements onto files. A local attacker could
use this to block utilities that examine the procfs filesystem to report
operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep xattr information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer
overflow in the CDROM driver implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket
handling code in the Linux kernel. A local attacker could use this to cause
a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel
did not properly perform permission checks in some situations when nested
virtualization is used. An attacker in a guest VM could possibly use this
to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Jakub Jirasek discovered that multiple use-after-free errors existed in the
USB/IP implementation in the Linux kernel. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5814)
It was discovered that a race condition existed in the ARM Advanced
Microcontroller Bus Architecture (AMBA) driver in the Linux kernel that
could result in a double free. A local attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-9415)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
linux-image-4.15.0-1017-oem 4.15.0-1017.20
linux-image-4.15.0-1022-azure 4.15.0-1022.23
linux-image-azure 4.15.0.1022.22
linux-image-azure-edge 4.15.0.1022.22
linux-image-oem 4.15.0.1017.19
Ubuntu 16.04 LTS:
linux-image-4.15.0-1018-gcp 4.15.0-1018.19~16.04.2
linux-image-4.15.0-1022-azure 4.15.0-1022.22~16.04.1
linux-image-azure 4.15.0.1022.28
linux-image-gcp 4.15.0.1018.32
linux-image-gke 4.15.0.1018.32
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3752-3
https://usn.ubuntu.com/usn/usn-3752-1
CVE-2018-1000200, CVE-2018-1000204, CVE-2018-10323, CVE-2018-10840,
CVE-2018-10881, CVE-2018-1093, CVE-2018-1108, CVE-2018-1120,
CVE-2018-11412, CVE-2018-11506, CVE-2018-12232, CVE-2018-12233,
CVE-2018-12904, CVE-2018-13094, CVE-2018-13405, CVE-2018-13406,
CVE-2018-5814, CVE-2018-9415
Package Information:
https://launchpad.net/ubuntu/+source/linux-azure/4.15.0-1022.23
https://launchpad.net/ubuntu/+source/linux-oem/4.15.0-1017.20
https://launchpad.net/ubuntu/+source/linux-azure/4.15.0-1022.22~16.04.1
https://launchpad.net/ubuntu/+source/linux-gcp/4.15.0-1018.19~16.04.2
Ubuntu Security Notice USN-3752-3
August 28, 2018
linux-azure, linux-oem, linux-gcp vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux-azure: Linux kernel for Microsoft Azure Cloud systems
- linux-oem: Linux kernel for OEM processors
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
Details:
It was discovered that, when attempting to handle an out-of-memory
situation, a null pointer dereference could be triggered in the Linux
kernel in some circumstances. A local attacker could use this to cause a
denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate xattr information. An attacker could use
this to construct a malicious xfs image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed
data reported that it was in a ready state before it had gathered
sufficient entropy. An attacker could use this to expose sensitive
information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle
processes mapping some memory elements onto files. A local attacker could
use this to block utilities that examine the procfs filesystem to report
operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep xattr information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer
overflow in the CDROM driver implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket
handling code in the Linux kernel. A local attacker could use this to cause
a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel
did not properly perform permission checks in some situations when nested
virtualization is used. An attacker in a guest VM could possibly use this
to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Jakub Jirasek discovered that multiple use-after-free errors existed in the
USB/IP implementation in the Linux kernel. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5814)
It was discovered that a race condition existed in the ARM Advanced
Microcontroller Bus Architecture (AMBA) driver in the Linux kernel that
could result in a double free. A local attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-9415)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
linux-image-4.15.0-1017-oem 4.15.0-1017.20
linux-image-4.15.0-1022-azure 4.15.0-1022.23
linux-image-azure 4.15.0.1022.22
linux-image-azure-edge 4.15.0.1022.22
linux-image-oem 4.15.0.1017.19
Ubuntu 16.04 LTS:
linux-image-4.15.0-1018-gcp 4.15.0-1018.19~16.04.2
linux-image-4.15.0-1022-azure 4.15.0-1022.22~16.04.1
linux-image-azure 4.15.0.1022.28
linux-image-gcp 4.15.0.1018.32
linux-image-gke 4.15.0.1018.32
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3752-3
https://usn.ubuntu.com/usn/usn-3752-1
CVE-2018-1000200, CVE-2018-1000204, CVE-2018-10323, CVE-2018-10840,
CVE-2018-10881, CVE-2018-1093, CVE-2018-1108, CVE-2018-1120,
CVE-2018-11412, CVE-2018-11506, CVE-2018-12232, CVE-2018-12233,
CVE-2018-12904, CVE-2018-13094, CVE-2018-13405, CVE-2018-13406,
CVE-2018-5814, CVE-2018-9415
Package Information:
https://launchpad.net/ubuntu/+source/linux-azure/4.15.0-1022.23
https://launchpad.net/ubuntu/+source/linux-oem/4.15.0-1017.20
https://launchpad.net/ubuntu/+source/linux-azure/4.15.0-1022.22~16.04.1
https://launchpad.net/ubuntu/+source/linux-gcp/4.15.0-1018.19~16.04.2
[CentOS-announce] CESA-2018:2570 Important CentOS 7 bind Security Update
CentOS Errata and Security Advisory 2018:2570 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2018:2570
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
ee4027789eafae8c2855a1702e117ff6dc517820a231df6eab0aed16eece8fab bind-9.9.4-61.el7_5.1.x86_64.rpm
45e7ad9b9c08a7ca8e78b95084a9b61caf86d664290d660c3ee6fd41661058f3 bind-chroot-9.9.4-61.el7_5.1.x86_64.rpm
303502657386d0c4e394811ba56b8d72025c92be2237e2045eb85c2661233807 bind-devel-9.9.4-61.el7_5.1.i686.rpm
1e2110e750b3adb5857904f19167109f418ee1f430f900308f1e009c7c1944d8 bind-devel-9.9.4-61.el7_5.1.x86_64.rpm
44328049069dfe2efbfb2c5e14c10d5482e23d39009eec290032232697d91cbb bind-libs-9.9.4-61.el7_5.1.i686.rpm
db10791c7f7966843cd78ec1b71025935d4caee8746b01622068eb8cb404bea2 bind-libs-9.9.4-61.el7_5.1.x86_64.rpm
8850fc3b588e95fc9a72b857cbccfd18093cc1c69b95b85eeec608433964d044 bind-libs-lite-9.9.4-61.el7_5.1.i686.rpm
c3fff9b6f6fca10a4fe77653fde96568f6a6353d8bf6fd87d526c45de7bed1a2 bind-libs-lite-9.9.4-61.el7_5.1.x86_64.rpm
2953e193ef6197ac414bf6ed2d15f59e3c85ffb824dd89a06f98189844eb1010 bind-license-9.9.4-61.el7_5.1.noarch.rpm
5c9df998d37413f862f619d0815e3131eba2e172ae63decf0efbeb5259fe633f bind-lite-devel-9.9.4-61.el7_5.1.i686.rpm
d77653fd680bfeef0dfd799fe1a8f2f6027e63693108567e3c6bba2474d0cd87 bind-lite-devel-9.9.4-61.el7_5.1.x86_64.rpm
1ef96a7ea43061542dbc97c4c7a2b1d9dc26b002d1593b0980b6027ca343a7aa bind-pkcs11-9.9.4-61.el7_5.1.x86_64.rpm
6f0afbee32b1536325fbdcffccbe81aff3b47d8e2de0dedc981cd393c22120c4 bind-pkcs11-devel-9.9.4-61.el7_5.1.i686.rpm
6e27874eaa335a46cede258f11e23ad20e8ef7678886698d275cd7c3e8bfc8d9 bind-pkcs11-devel-9.9.4-61.el7_5.1.x86_64.rpm
971f7b0c47c778862444dffafc36616cb7dba597af7e721d8ab9e92e0be8e2ce bind-pkcs11-libs-9.9.4-61.el7_5.1.i686.rpm
a865deb5b2c4771820fdbdea2e42a01a891644d6ed9ca0a06fb532142c411044 bind-pkcs11-libs-9.9.4-61.el7_5.1.x86_64.rpm
65d05f02bdf025e23ea9d9142e3255432ec39c5c6b29e5fe6920dfd665bf8b99 bind-pkcs11-utils-9.9.4-61.el7_5.1.x86_64.rpm
790f90103359863a59b552100ba8a3c03067795bab42fb518625fa54143e66ca bind-sdb-9.9.4-61.el7_5.1.x86_64.rpm
a3bbb400e22a538a3c2b98e8a241714d58fb2713e2f3bb6a2f140068b606283f bind-sdb-chroot-9.9.4-61.el7_5.1.x86_64.rpm
3c474addd9b809ec82d7d8f9cad68ea950b658d43c2a362fc4ffe94ad2e3f12d bind-utils-9.9.4-61.el7_5.1.x86_64.rpm
Source:
3b9245b26b6677828475193eface9f2e30c478bf3b38f37e507398b04e082b8c bind-9.9.4-61.el7_5.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Upstream details at : https://access.redhat.com/errata/RHSA-2018:2570
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
ee4027789eafae8c2855a1702e117ff6dc517820a231df6eab0aed16eece8fab bind-9.9.4-61.el7_5.1.x86_64.rpm
45e7ad9b9c08a7ca8e78b95084a9b61caf86d664290d660c3ee6fd41661058f3 bind-chroot-9.9.4-61.el7_5.1.x86_64.rpm
303502657386d0c4e394811ba56b8d72025c92be2237e2045eb85c2661233807 bind-devel-9.9.4-61.el7_5.1.i686.rpm
1e2110e750b3adb5857904f19167109f418ee1f430f900308f1e009c7c1944d8 bind-devel-9.9.4-61.el7_5.1.x86_64.rpm
44328049069dfe2efbfb2c5e14c10d5482e23d39009eec290032232697d91cbb bind-libs-9.9.4-61.el7_5.1.i686.rpm
db10791c7f7966843cd78ec1b71025935d4caee8746b01622068eb8cb404bea2 bind-libs-9.9.4-61.el7_5.1.x86_64.rpm
8850fc3b588e95fc9a72b857cbccfd18093cc1c69b95b85eeec608433964d044 bind-libs-lite-9.9.4-61.el7_5.1.i686.rpm
c3fff9b6f6fca10a4fe77653fde96568f6a6353d8bf6fd87d526c45de7bed1a2 bind-libs-lite-9.9.4-61.el7_5.1.x86_64.rpm
2953e193ef6197ac414bf6ed2d15f59e3c85ffb824dd89a06f98189844eb1010 bind-license-9.9.4-61.el7_5.1.noarch.rpm
5c9df998d37413f862f619d0815e3131eba2e172ae63decf0efbeb5259fe633f bind-lite-devel-9.9.4-61.el7_5.1.i686.rpm
d77653fd680bfeef0dfd799fe1a8f2f6027e63693108567e3c6bba2474d0cd87 bind-lite-devel-9.9.4-61.el7_5.1.x86_64.rpm
1ef96a7ea43061542dbc97c4c7a2b1d9dc26b002d1593b0980b6027ca343a7aa bind-pkcs11-9.9.4-61.el7_5.1.x86_64.rpm
6f0afbee32b1536325fbdcffccbe81aff3b47d8e2de0dedc981cd393c22120c4 bind-pkcs11-devel-9.9.4-61.el7_5.1.i686.rpm
6e27874eaa335a46cede258f11e23ad20e8ef7678886698d275cd7c3e8bfc8d9 bind-pkcs11-devel-9.9.4-61.el7_5.1.x86_64.rpm
971f7b0c47c778862444dffafc36616cb7dba597af7e721d8ab9e92e0be8e2ce bind-pkcs11-libs-9.9.4-61.el7_5.1.i686.rpm
a865deb5b2c4771820fdbdea2e42a01a891644d6ed9ca0a06fb532142c411044 bind-pkcs11-libs-9.9.4-61.el7_5.1.x86_64.rpm
65d05f02bdf025e23ea9d9142e3255432ec39c5c6b29e5fe6920dfd665bf8b99 bind-pkcs11-utils-9.9.4-61.el7_5.1.x86_64.rpm
790f90103359863a59b552100ba8a3c03067795bab42fb518625fa54143e66ca bind-sdb-9.9.4-61.el7_5.1.x86_64.rpm
a3bbb400e22a538a3c2b98e8a241714d58fb2713e2f3bb6a2f140068b606283f bind-sdb-chroot-9.9.4-61.el7_5.1.x86_64.rpm
3c474addd9b809ec82d7d8f9cad68ea950b658d43c2a362fc4ffe94ad2e3f12d bind-utils-9.9.4-61.el7_5.1.x86_64.rpm
Source:
3b9245b26b6677828475193eface9f2e30c478bf3b38f37e507398b04e082b8c bind-9.9.4-61.el7_5.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2018:2557 Important CentOS 7 postgresql Security Update
CentOS Errata and Security Advisory 2018:2557 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2018:2557
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
435c54da90ac6a986123ebeed8a46ca06198945148412400bcc25165b20b0901 postgresql-9.2.24-1.el7_5.i686.rpm
88083a8c3867858fc230fb8e123d1884ad447630af3d0b7cdbc9f415a2cb7691 postgresql-9.2.24-1.el7_5.x86_64.rpm
26607e1d2c701a5a0a8203fc4a4ddd74c3f7d5ed6d9b121753535c673bf3df82 postgresql-contrib-9.2.24-1.el7_5.x86_64.rpm
fae26c6c1a2e35d21388f9e9bb601e2e65ebf6ebee491c7879fe3e841c89d2bd postgresql-devel-9.2.24-1.el7_5.i686.rpm
97d1b913fd93b28fedcff9d9889b74a86c1c8fc80619ca2a9f9050cc21a2c840 postgresql-devel-9.2.24-1.el7_5.x86_64.rpm
f06e0c08f35f44e82d81c6a953a2095229c5c8ea6a1ed557ed3428b2d982b2a0 postgresql-docs-9.2.24-1.el7_5.x86_64.rpm
5fb3d8e7c46ef84c38761fbf8eb0fa45b3d6bb78271be062d864d7038ce42dcf postgresql-libs-9.2.24-1.el7_5.i686.rpm
d8435352291ac2627b65f0a3a65f41906390307cf2300d020dfb793e705cdb06 postgresql-libs-9.2.24-1.el7_5.x86_64.rpm
2a20977c047a2a3e7efef79b589ba8bf95285a5fad766dd485f258d33b8b3201 postgresql-plperl-9.2.24-1.el7_5.x86_64.rpm
8b0d205949e154882da55d7d472489ba7414b856ed59039614b6590c75a45c60 postgresql-plpython-9.2.24-1.el7_5.x86_64.rpm
75fe3d5666368c6f0bc80e64c203b91286f1e4c81ed82bbd5db988b9425fcbbd postgresql-pltcl-9.2.24-1.el7_5.x86_64.rpm
6955c0e9151487a7bde24418fee9af6072916190e1879c20a8ee95623cb56e05 postgresql-server-9.2.24-1.el7_5.x86_64.rpm
2232aae0691e140707437ba1422329bd6193aacb98929508838f8f8a37f062b8 postgresql-static-9.2.24-1.el7_5.i686.rpm
a1ec84aeb970a247c7075be4e2e44dc1d1662a5f4ce63b20b65ebd69fad3aeae postgresql-static-9.2.24-1.el7_5.x86_64.rpm
70a4adbd0edfe7f982395b928129e82da3cc6ce4bcee4e30dd395116da1c60b4 postgresql-test-9.2.24-1.el7_5.x86_64.rpm
fd8c23fc70230e52d47f56b0ed72325152e59e9dcdb777b55805acef4ac96ce7 postgresql-upgrade-9.2.24-1.el7_5.x86_64.rpm
Source:
9fd884c340f9aae296653aff2b30fcc4362acba9912508bb07c8778dc8e78f9e postgresql-9.2.24-1.el7_5.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Upstream details at : https://access.redhat.com/errata/RHSA-2018:2557
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
435c54da90ac6a986123ebeed8a46ca06198945148412400bcc25165b20b0901 postgresql-9.2.24-1.el7_5.i686.rpm
88083a8c3867858fc230fb8e123d1884ad447630af3d0b7cdbc9f415a2cb7691 postgresql-9.2.24-1.el7_5.x86_64.rpm
26607e1d2c701a5a0a8203fc4a4ddd74c3f7d5ed6d9b121753535c673bf3df82 postgresql-contrib-9.2.24-1.el7_5.x86_64.rpm
fae26c6c1a2e35d21388f9e9bb601e2e65ebf6ebee491c7879fe3e841c89d2bd postgresql-devel-9.2.24-1.el7_5.i686.rpm
97d1b913fd93b28fedcff9d9889b74a86c1c8fc80619ca2a9f9050cc21a2c840 postgresql-devel-9.2.24-1.el7_5.x86_64.rpm
f06e0c08f35f44e82d81c6a953a2095229c5c8ea6a1ed557ed3428b2d982b2a0 postgresql-docs-9.2.24-1.el7_5.x86_64.rpm
5fb3d8e7c46ef84c38761fbf8eb0fa45b3d6bb78271be062d864d7038ce42dcf postgresql-libs-9.2.24-1.el7_5.i686.rpm
d8435352291ac2627b65f0a3a65f41906390307cf2300d020dfb793e705cdb06 postgresql-libs-9.2.24-1.el7_5.x86_64.rpm
2a20977c047a2a3e7efef79b589ba8bf95285a5fad766dd485f258d33b8b3201 postgresql-plperl-9.2.24-1.el7_5.x86_64.rpm
8b0d205949e154882da55d7d472489ba7414b856ed59039614b6590c75a45c60 postgresql-plpython-9.2.24-1.el7_5.x86_64.rpm
75fe3d5666368c6f0bc80e64c203b91286f1e4c81ed82bbd5db988b9425fcbbd postgresql-pltcl-9.2.24-1.el7_5.x86_64.rpm
6955c0e9151487a7bde24418fee9af6072916190e1879c20a8ee95623cb56e05 postgresql-server-9.2.24-1.el7_5.x86_64.rpm
2232aae0691e140707437ba1422329bd6193aacb98929508838f8f8a37f062b8 postgresql-static-9.2.24-1.el7_5.i686.rpm
a1ec84aeb970a247c7075be4e2e44dc1d1662a5f4ce63b20b65ebd69fad3aeae postgresql-static-9.2.24-1.el7_5.x86_64.rpm
70a4adbd0edfe7f982395b928129e82da3cc6ce4bcee4e30dd395116da1c60b4 postgresql-test-9.2.24-1.el7_5.x86_64.rpm
fd8c23fc70230e52d47f56b0ed72325152e59e9dcdb777b55805acef4ac96ce7 postgresql-upgrade-9.2.24-1.el7_5.x86_64.rpm
Source:
9fd884c340f9aae296653aff2b30fcc4362acba9912508bb07c8778dc8e78f9e postgresql-9.2.24-1.el7_5.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2018:2571 Important CentOS 6 bind Security Update
CentOS Errata and Security Advisory 2018:2571 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2018:2571
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
248124b6482789bfbb5f6e656a98e915769c55168b3d23009652527526e331a8 bind-9.8.2-0.68.rc1.el6_10.1.i686.rpm
f1c0a5f60d808dafd3d67b4ce198019bc13632e07f71cefb29a75ebe2af4fd63 bind-chroot-9.8.2-0.68.rc1.el6_10.1.i686.rpm
87bffb7bd45681565d5ef4b18579169f187d4fa66fbec4741c570430ee0c06d2 bind-devel-9.8.2-0.68.rc1.el6_10.1.i686.rpm
2f6f7ac42ca47afd420d62c6f21ef2d4e7d1505fedb6a9a70bc9b2c6461e50d9 bind-libs-9.8.2-0.68.rc1.el6_10.1.i686.rpm
1ed256461a14d8fe827d6aaa3aa46a8e6ed9ce55532aa3c27a5eba1921f06257 bind-sdb-9.8.2-0.68.rc1.el6_10.1.i686.rpm
7e481a255c517a66d7222957ad199ef61455f918f1ba80160ab42a07f1b1f544 bind-utils-9.8.2-0.68.rc1.el6_10.1.i686.rpm
x86_64:
960846e8ce3a15bab85789a29ad4e9ac3e9d00b9d9fe158a07ab16eec065fabc bind-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
09b0b1148ddb2de55b5165b51be9c3c250ccb981fbdc4e01934c8a23a1c4c098 bind-chroot-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
87bffb7bd45681565d5ef4b18579169f187d4fa66fbec4741c570430ee0c06d2 bind-devel-9.8.2-0.68.rc1.el6_10.1.i686.rpm
0018e4f38542d2d56fa15893ffb5cd34e8023fdc2b30a3b42d28666fe55d946a bind-devel-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
2f6f7ac42ca47afd420d62c6f21ef2d4e7d1505fedb6a9a70bc9b2c6461e50d9 bind-libs-9.8.2-0.68.rc1.el6_10.1.i686.rpm
a885a7dd62446139f83677fde3dc9769ba2990463575cba4e8f4914d7ffa22a5 bind-libs-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
dc3892983716d2275054bbfea53267131b78806cb2926444a8ea6d846193929b bind-sdb-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
baf936fc48052e6ba44bd76af3a14094c0b16c26c92923ff83ffc597a58ed23e bind-utils-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
Source:
8564b64b5870e90091523c0fb7e9bc86d99d43faefafa91132f4be497e8eb259 bind-9.8.2-0.68.rc1.el6_10.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Upstream details at : https://access.redhat.com/errata/RHSA-2018:2571
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
248124b6482789bfbb5f6e656a98e915769c55168b3d23009652527526e331a8 bind-9.8.2-0.68.rc1.el6_10.1.i686.rpm
f1c0a5f60d808dafd3d67b4ce198019bc13632e07f71cefb29a75ebe2af4fd63 bind-chroot-9.8.2-0.68.rc1.el6_10.1.i686.rpm
87bffb7bd45681565d5ef4b18579169f187d4fa66fbec4741c570430ee0c06d2 bind-devel-9.8.2-0.68.rc1.el6_10.1.i686.rpm
2f6f7ac42ca47afd420d62c6f21ef2d4e7d1505fedb6a9a70bc9b2c6461e50d9 bind-libs-9.8.2-0.68.rc1.el6_10.1.i686.rpm
1ed256461a14d8fe827d6aaa3aa46a8e6ed9ce55532aa3c27a5eba1921f06257 bind-sdb-9.8.2-0.68.rc1.el6_10.1.i686.rpm
7e481a255c517a66d7222957ad199ef61455f918f1ba80160ab42a07f1b1f544 bind-utils-9.8.2-0.68.rc1.el6_10.1.i686.rpm
x86_64:
960846e8ce3a15bab85789a29ad4e9ac3e9d00b9d9fe158a07ab16eec065fabc bind-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
09b0b1148ddb2de55b5165b51be9c3c250ccb981fbdc4e01934c8a23a1c4c098 bind-chroot-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
87bffb7bd45681565d5ef4b18579169f187d4fa66fbec4741c570430ee0c06d2 bind-devel-9.8.2-0.68.rc1.el6_10.1.i686.rpm
0018e4f38542d2d56fa15893ffb5cd34e8023fdc2b30a3b42d28666fe55d946a bind-devel-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
2f6f7ac42ca47afd420d62c6f21ef2d4e7d1505fedb6a9a70bc9b2c6461e50d9 bind-libs-9.8.2-0.68.rc1.el6_10.1.i686.rpm
a885a7dd62446139f83677fde3dc9769ba2990463575cba4e8f4914d7ffa22a5 bind-libs-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
dc3892983716d2275054bbfea53267131b78806cb2926444a8ea6d846193929b bind-sdb-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
baf936fc48052e6ba44bd76af3a14094c0b16c26c92923ff83ffc597a58ed23e bind-utils-9.8.2-0.68.rc1.el6_10.1.x86_64.rpm
Source:
8564b64b5870e90091523c0fb7e9bc86d99d43faefafa91132f4be497e8eb259 bind-9.8.2-0.68.rc1.el6_10.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Monday, August 27, 2018
Fedora 29 Beta Freeze
Hi all,
Today's an important day on the Fedora 29 schedule[1], with several significant cut-offs. First of all today is
the Bodhi activation point [2]. That means that from now all Fedora 29 packages must be submitted to
updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the
fedora repository.
Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception
bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-
testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to
'stable' as usual until the Final freeze.
Finally, Today is the '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 29 Changes
must now be code complete, meaning all the code required to enable to the new change is finished. The level
of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested
by this deadline'.
Finally, today is also the Software String freeze[7], which means that strings marked for translation in Fedora-
translated projects should not now be changed for Fedora 29.
Mohan Boddu
[USN-3756-1] Intel Microcode vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3756-1
August 27, 2018
intel-microcode vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
The system could be made to expose sensitive information.
Software Description:
- intel-microcode: Processor microcode for Intel CPUs
Details:
It was discovered that memory present in the L1 data cache of an Intel CPU
core may be exposed to a malicious process that is executing on the CPU
core. This vulnerability is also known as L1 Terminal Fault (L1TF). A local
attacker in a guest virtual machine could use this to expose sensitive
information (memory from other guests or the host OS). (CVE-2018-3646)
Jann Horn and Ken Johnson discovered that microprocessors utilizing
speculative execution of a memory read may allow unauthorized memory reads
via a sidechannel attack. This flaw is known as Spectre Variant 4. A local
attacker could use this to expose sensitive information, including kernel
memory. (CVE-2018-3639)
Zdenek Sojka, Rudolf Marek, Alex Zuepke, and Innokentiy Sennovskiy
discovered that microprocessors that perform speculative reads of
system registers may allow unauthorized disclosure of system parameters
via a sidechannel attack. This vulnerability is also known as Rogue
System Register Read (RSRE). An attacker could use this to expose
sensitive information. (CVE-2018-3640)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
intel-microcode 3.20180807a.0ubuntu0.18.04.1
Ubuntu 16.04 LTS:
intel-microcode 3.20180807a.0ubuntu0.16.04.1
Ubuntu 14.04 LTS:
intel-microcode 3.20180807a.0ubuntu0.14.04.1
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://usn.ubuntu.com/usn/usn-3756-1
CVE-2018-3639, CVE-2018-3640, CVE-2018-3646
Package Information:
https://launchpad.net/ubuntu/+source/intel-microcode/3.20180807a.0ubuntu0.18.04.1
https://launchpad.net/ubuntu/+source/intel-microcode/3.20180807a.0ubuntu0.16.04.1
https://launchpad.net/ubuntu/+source/intel-microcode/3.20180807a.0ubuntu0.14.04.1
Ubuntu Security Notice USN-3756-1
August 27, 2018
intel-microcode vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
The system could be made to expose sensitive information.
Software Description:
- intel-microcode: Processor microcode for Intel CPUs
Details:
It was discovered that memory present in the L1 data cache of an Intel CPU
core may be exposed to a malicious process that is executing on the CPU
core. This vulnerability is also known as L1 Terminal Fault (L1TF). A local
attacker in a guest virtual machine could use this to expose sensitive
information (memory from other guests or the host OS). (CVE-2018-3646)
Jann Horn and Ken Johnson discovered that microprocessors utilizing
speculative execution of a memory read may allow unauthorized memory reads
via a sidechannel attack. This flaw is known as Spectre Variant 4. A local
attacker could use this to expose sensitive information, including kernel
memory. (CVE-2018-3639)
Zdenek Sojka, Rudolf Marek, Alex Zuepke, and Innokentiy Sennovskiy
discovered that microprocessors that perform speculative reads of
system registers may allow unauthorized disclosure of system parameters
via a sidechannel attack. This vulnerability is also known as Rogue
System Register Read (RSRE). An attacker could use this to expose
sensitive information. (CVE-2018-3640)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
intel-microcode 3.20180807a.0ubuntu0.18.04.1
Ubuntu 16.04 LTS:
intel-microcode 3.20180807a.0ubuntu0.16.04.1
Ubuntu 14.04 LTS:
intel-microcode 3.20180807a.0ubuntu0.14.04.1
After a standard system update you need to reboot your computer to make
all the necessary changes.
References:
https://usn.ubuntu.com/usn/usn-3756-1
CVE-2018-3639, CVE-2018-3640, CVE-2018-3646
Package Information:
https://launchpad.net/ubuntu/+source/intel-microcode/3.20180807a.0ubuntu0.18.04.1
https://launchpad.net/ubuntu/+source/intel-microcode/3.20180807a.0ubuntu0.16.04.1
https://launchpad.net/ubuntu/+source/intel-microcode/3.20180807a.0ubuntu0.14.04.1
[USN-3755-1] GD vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3755-1
August 27, 2018
libgd2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in GD.
Software Description:
- libgd2: GD Graphics Library
Details:
It was discovered that GD incorrectly handled certain images.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2018-1000222)
It was discovered that GD incorrectly handled certain GIF files.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2018-5711)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
libgd-tools 2.2.5-4ubuntu0.2
libgd3 2.2.5-4ubuntu0.2
Ubuntu 16.04 LTS:
libgd-tools 2.1.1-4ubuntu0.16.04.10
libgd3 2.1.1-4ubuntu0.16.04.10
Ubuntu 14.04 LTS:
libgd-tools 2.1.0-3ubuntu0.10
libgd3 2.1.0-3ubuntu0.10
In general, a standard system update will make all the necessary
changes.
References:
https://usn.ubuntu.com/usn/usn-3755-1
CVE-2018-1000222, CVE-2018-5711
Package Information:
https://launchpad.net/ubuntu/+source/libgd2/2.2.5-4ubuntu0.2
https://launchpad.net/ubuntu/+source/libgd2/2.1.1-4ubuntu0.16.04.10
https://launchpad.net/ubuntu/+source/libgd2/2.1.0-3ubuntu0.10
Ubuntu Security Notice USN-3755-1
August 27, 2018
libgd2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in GD.
Software Description:
- libgd2: GD Graphics Library
Details:
It was discovered that GD incorrectly handled certain images.
An attacker could possibly use this issue to execute arbitrary code.
(CVE-2018-1000222)
It was discovered that GD incorrectly handled certain GIF files.
An attacker could possibly use this issue to cause a denial of service.
(CVE-2018-5711)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
libgd-tools 2.2.5-4ubuntu0.2
libgd3 2.2.5-4ubuntu0.2
Ubuntu 16.04 LTS:
libgd-tools 2.1.1-4ubuntu0.16.04.10
libgd3 2.1.1-4ubuntu0.16.04.10
Ubuntu 14.04 LTS:
libgd-tools 2.1.0-3ubuntu0.10
libgd3 2.1.0-3ubuntu0.10
In general, a standard system update will make all the necessary
changes.
References:
https://usn.ubuntu.com/usn/usn-3755-1
CVE-2018-1000222, CVE-2018-5711
Package Information:
https://launchpad.net/ubuntu/+source/libgd2/2.2.5-4ubuntu0.2
https://launchpad.net/ubuntu/+source/libgd2/2.1.1-4ubuntu0.16.04.10
https://launchpad.net/ubuntu/+source/libgd2/2.1.0-3ubuntu0.10
Friday, August 24, 2018
Fwd: fedora-tagger sunset - week post F29 beta freeze
Dear all,
The Fedora Infrastructure is running the fedora-tagger [0] service,
however it gets little usage and also has no one really maintaining it
or fixing issues with it. Earlier this year [1] we have tried to
support community members who expressed their interests in maintaining
this application, unfortunately this effort did not results in a new
version being released.
During our last meeting [2], we agreed to retire this service a week
after the end of the F29 beta freeze (see F29 schedule [3]).
Once the F29 beta freeze is over, we will communicate a sunset date.
Regards,
Clément
[0] - https://apps.fedoraproject.org/tagger/
[1] - https://communityblog.fedoraproject.org/maintainers-package-tagger/
[2] - https://meetbot.fedoraproject.org/teams/infrastructure/infrastructure.2018-08-23-14.00.log.html
[3] - https://fedoraproject.org/wiki/Releases/29/Schedule?rd=Schedule
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/UPM46GFVAD4NHUMOMEWS3XGM52T2YV3T/
The Fedora Infrastructure is running the fedora-tagger [0] service,
however it gets little usage and also has no one really maintaining it
or fixing issues with it. Earlier this year [1] we have tried to
support community members who expressed their interests in maintaining
this application, unfortunately this effort did not results in a new
version being released.
During our last meeting [2], we agreed to retire this service a week
after the end of the F29 beta freeze (see F29 schedule [3]).
Once the F29 beta freeze is over, we will communicate a sunset date.
Regards,
Clément
[0] - https://apps.fedoraproject.org/tagger/
[1] - https://communityblog.fedoraproject.org/maintainers-package-tagger/
[2] - https://meetbot.fedoraproject.org/teams/infrastructure/infrastructure.2018-08-23-14.00.log.html
[3] - https://fedoraproject.org/wiki/Releases/29/Schedule?rd=Schedule
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/UPM46GFVAD4NHUMOMEWS3XGM52T2YV3T/
Thursday, August 23, 2018
[USN-3754-1] Linux kernel vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3754-1
August 24, 2018
linux vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
Details:
Ralf Spenneberg discovered that the ext4 implementation in the Linux kernel
did not properly validate meta block groups. An attacker with physical
access could use this to specially craft an ext4 image that causes a denial
of service (system crash). (CVE-2016-10208)
It was discovered that an information disclosure vulnerability existed in
the ACPI implementation of the Linux kernel. A local attacker could use
this to expose sensitive information (kernel memory addresses).
(CVE-2017-11472)
It was discovered that a buffer overflow existed in the ACPI table parsing
implementation in the Linux kernel. A local attacker could use this to
construct a malicious ACPI table that, when loaded, caused a denial of
service (system crash) or possibly execute arbitrary code.
(CVE-2017-11473)
It was discovered that the generic SCSI driver in the Linux kernel did not
properly initialize data returned to user space in some situations. A local
attacker could use this to expose sensitive information (kernel memory).
(CVE-2017-14991)
It was discovered that a race condition existed in the packet fanout
implementation in the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-15649)
Andrey Konovalov discovered that the Ultra Wide Band driver in the Linux
kernel did not properly check for an error condition. A physically
proximate attacker could use this to cause a denial of service (system
crash) or possibly execute arbitrary code. (CVE-2017-16526)
Andrey Konovalov discovered that the ALSA subsystem in the Linux kernel
contained a use-after-free vulnerability. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-16527)
Andrey Konovalov discovered that the ALSA subsystem in the Linux kernel did
not properly validate USB audio buffer descriptors. A physically proximate
attacker could use this cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2017-16529)
Andrey Konovalov discovered that the USB subsystem in the Linux kernel did
not properly validate USB interface association descriptors. A physically
proximate attacker could use this to cause a denial of service (system
crash). (CVE-2017-16531)
Andrey Konovalov discovered that the usbtest device driver in the Linux
kernel did not properly validate endpoint metadata. A physically proximate
attacker could use this to cause a denial of service (system crash).
(CVE-2017-16532)
Andrey Konovalov discovered that the USB subsystem in the Linux kernel did
not properly validate USB HID descriptors. A physically proximate attacker
could use this to cause a denial of service (system crash).
(CVE-2017-16533)
Andrey Konovalov discovered that the USB subsystem in the Linux kernel did
not properly validate USB BOS metadata. A physically proximate attacker
could use this to cause a denial of service (system crash).
(CVE-2017-16535)
Andrey Konovalov discovered that the Conexant cx231xx USB video capture
driver in the Linux kernel did not properly validate interface descriptors.
A physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2017-16536)
Andrey Konovalov discovered that the SoundGraph iMON USB driver in the
Linux kernel did not properly validate device metadata. A physically
proximate attacker could use this to cause a denial of service (system
crash). (CVE-2017-16537)
It was discovered that the DM04/QQBOX USB driver in the Linux kernel did
not properly handle device attachment and warm-start. A physically
proximate attacker could use this to cause a denial of service (system
crash) or possibly execute arbitrary code. (CVE-2017-16538)
Andrey Konovalov discovered an out-of-bounds read in the GTCO digitizer USB
driver for the Linux kernel. A physically proximate attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-16643)
Andrey Konovalov discovered that the video4linux driver for Hauppauge HD
PVR USB devices in the Linux kernel did not properly handle some error
conditions. A physically proximate attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2017-16644)
Andrey Konovalov discovered that the IMS Passenger Control Unit USB driver
in the Linux kernel did not properly validate device descriptors. A
physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2017-16645)
Andrey Konovalov discovered that the QMI WWAN USB driver did not properly
validate device descriptors. A physically proximate attacker could use this
to cause a denial of service (system crash). (CVE-2017-16650)
It was discovered that the USB Virtual Host Controller Interface (VHCI)
driver in the Linux kernel contained an information disclosure
vulnerability. A physically proximate attacker could use this to expose
sensitive information (kernel memory). (CVE-2017-16911)
It was discovered that the USB over IP implementation in the Linux kernel
did not validate endpoint numbers. A remote attacker could use this to
cause a denial of service (system crash). (CVE-2017-16912)
It was discovered that the USB over IP implementation in the Linux kernel
did not properly validate CMD_SUBMIT packets. A remote attacker could use
this to cause a denial of service (excessive memory consumption).
(CVE-2017-16913)
It was discovered that the USB over IP implementation in the Linux kernel
contained a NULL pointer dereference error. A remote attacker could use
this to cause a denial of service (system crash). (CVE-2017-16914)
It was discovered that the core USB subsystem in the Linux kernel did not
validate the number of configurations and interfaces in a device. A
physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2017-17558)
It was discovered that an integer overflow existed in the perf subsystem of
the Linux kernel. A local attacker could use this to cause a denial of
service (system crash). (CVE-2017-18255)
It was discovered that the keyring subsystem in the Linux kernel did not
properly prevent a user from creating keyrings for other users. A local
attacker could use this cause a denial of service or expose sensitive
information. (CVE-2017-18270)
Andy Lutomirski and Willy Tarreau discovered that the KVM implementation in
the Linux kernel did not properly emulate instructions on the SS segment
register. A local attacker in a guest virtual machine could use this to
cause a denial of service (guest OS crash) or possibly gain administrative
privileges in the guest OS. (CVE-2017-2583)
Dmitry Vyukov discovered that the KVM implementation in the Linux kernel
improperly emulated certain instructions. A local attacker could use this
to obtain sensitive information (kernel memory). (CVE-2017-2584)
It was discovered that the KLSI KL5KUSB105 serial-to-USB device driver in
the Linux kernel did not properly initialize memory related to logging. A
local attacker could use this to expose sensitive information (kernel
memory). (CVE-2017-5549)
Andrey Konovalov discovered an out-of-bounds access in the IPv6 Generic
Routing Encapsulation (GRE) tunneling implementation in the Linux kernel.
An attacker could use this to possibly expose sensitive information.
(CVE-2017-5897)
Andrey Konovalov discovered that the LLC subsytem in the Linux kernel did
not properly set up a destructor in certain situations. A local attacker
could use this to cause a denial of service (system crash). (CVE-2017-6345)
Dmitry Vyukov discovered race conditions in the Infrared (IrDA) subsystem
in the Linux kernel. A local attacker could use this to cause a denial of
service (deadlock). (CVE-2017-6348)
Andy Lutomirski discovered that the KVM implementation in the Linux kernel
was vulnerable to a debug exception error when single-stepping through a
syscall. A local attacker in a non-Linux guest vm could possibly use this
to gain administrative privileges in the guest vm. (CVE-2017-7518)
Tuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server
implementations in the Linux kernel did not properly handle certain long
RPC replies. A remote attacker could use this to cause a denial of service
(system crash). (CVE-2017-7645)
Pengfei Wang discovered that a race condition existed in the NXP SAA7164 TV
Decoder driver for the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-8831)
Pengfei Wang discovered that the Turtle Beach MultiSound audio device
driver in the Linux kernel contained race conditions when fetching from the
ring-buffer. A local attacker could use this to cause a denial of service
(infinite loop). (CVE-2017-9984, CVE-2017-9985)
It was discovered that the wait4() system call in the Linux kernel did not
properly validate its arguments in some situations. A local attacker could
possibly use this to cause a denial of service. (CVE-2018-10087)
It was discovered that the kill() system call implementation in the Linux
kernel did not properly validate its arguments in some situations. A local
attacker could possibly use this to cause a denial of service.
(CVE-2018-10124)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Zhong Jiang discovered that a use-after-free vulnerability existed in the
NUMA memory policy implementation in the Linux kernel. A local attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2018-10675)
Wen Xu discovered that a buffer overflow existed in the ext4 filesystem
implementation in the Linux kernel. An attacker could use this to construct
a malicious ext4 image that, when mounted, could cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2018-10877)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 file system that caused
a denial of service (system crash) when mounted. (CVE-2018-1092)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
It was discovered that the cdrom driver in the Linux kernel contained an
incorrect bounds check. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2018-10940)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Daniel Jiang discovered that a race condition existed in the ipv4 ping
socket implementation in the Linux kernel. A local privileged attacker
could use this to cause a denial of service (system crash). (CVE-2017-2671)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
It was discovered that a memory leak existed in the Serial Attached SCSI
(SAS) implementation in the Linux kernel. A physically proximate attacker
could use this to cause a denial of service (memory exhaustion).
(CVE-2018-10021)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 14.04 LTS:
linux-image-3.13.0-157-generic 3.13.0-157.207
linux-image-3.13.0-157-generic-lpae 3.13.0-157.207
linux-image-3.13.0-157-lowlatency 3.13.0-157.207
linux-image-3.13.0-157-powerpc-e500 3.13.0-157.207
linux-image-3.13.0-157-powerpc-e500mc 3.13.0-157.207
linux-image-3.13.0-157-powerpc-smp 3.13.0-157.207
linux-image-3.13.0-157-powerpc64-emb 3.13.0-157.207
linux-image-3.13.0-157-powerpc64-smp 3.13.0-157.207
linux-image-generic 3.13.0.157.167
linux-image-generic-lpae 3.13.0.157.167
linux-image-lowlatency 3.13.0.157.167
linux-image-powerpc-e500 3.13.0.157.167
linux-image-powerpc-e500mc 3.13.0.157.167
linux-image-powerpc-smp 3.13.0.157.167
linux-image-powerpc64-emb 3.13.0.157.167
linux-image-powerpc64-smp 3.13.0.157.167
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3754-1
CVE-2016-10208, CVE-2017-11472, CVE-2017-11473, CVE-2017-14991,
CVE-2017-15649, CVE-2017-16526, CVE-2017-16527, CVE-2017-16529,
CVE-2017-16531, CVE-2017-16532, CVE-2017-16533, CVE-2017-16535,
CVE-2017-16536, CVE-2017-16537, CVE-2017-16538, CVE-2017-16643,
CVE-2017-16644, CVE-2017-16645, CVE-2017-16650, CVE-2017-16911,
CVE-2017-16912, CVE-2017-16913, CVE-2017-16914, CVE-2017-17558,
CVE-2017-18255, CVE-2017-18270, CVE-2017-2583, CVE-2017-2584,
CVE-2017-2671, CVE-2017-5549, CVE-2017-5897, CVE-2017-6345,
CVE-2017-6348, CVE-2017-7518, CVE-2017-7645, CVE-2017-8831,
CVE-2017-9984, CVE-2017-9985, CVE-2018-1000204, CVE-2018-10021,
CVE-2018-10087, CVE-2018-10124, CVE-2018-10323, CVE-2018-10675,
CVE-2018-10877, CVE-2018-10881, CVE-2018-1092, CVE-2018-1093,
CVE-2018-10940, CVE-2018-12233, CVE-2018-13094, CVE-2018-13405,
CVE-2018-13406
Package Information:
https://launchpad.net/ubuntu/+source/linux/3.13.0-157.207
Ubuntu Security Notice USN-3754-1
August 24, 2018
linux vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
Details:
Ralf Spenneberg discovered that the ext4 implementation in the Linux kernel
did not properly validate meta block groups. An attacker with physical
access could use this to specially craft an ext4 image that causes a denial
of service (system crash). (CVE-2016-10208)
It was discovered that an information disclosure vulnerability existed in
the ACPI implementation of the Linux kernel. A local attacker could use
this to expose sensitive information (kernel memory addresses).
(CVE-2017-11472)
It was discovered that a buffer overflow existed in the ACPI table parsing
implementation in the Linux kernel. A local attacker could use this to
construct a malicious ACPI table that, when loaded, caused a denial of
service (system crash) or possibly execute arbitrary code.
(CVE-2017-11473)
It was discovered that the generic SCSI driver in the Linux kernel did not
properly initialize data returned to user space in some situations. A local
attacker could use this to expose sensitive information (kernel memory).
(CVE-2017-14991)
It was discovered that a race condition existed in the packet fanout
implementation in the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-15649)
Andrey Konovalov discovered that the Ultra Wide Band driver in the Linux
kernel did not properly check for an error condition. A physically
proximate attacker could use this to cause a denial of service (system
crash) or possibly execute arbitrary code. (CVE-2017-16526)
Andrey Konovalov discovered that the ALSA subsystem in the Linux kernel
contained a use-after-free vulnerability. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-16527)
Andrey Konovalov discovered that the ALSA subsystem in the Linux kernel did
not properly validate USB audio buffer descriptors. A physically proximate
attacker could use this cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2017-16529)
Andrey Konovalov discovered that the USB subsystem in the Linux kernel did
not properly validate USB interface association descriptors. A physically
proximate attacker could use this to cause a denial of service (system
crash). (CVE-2017-16531)
Andrey Konovalov discovered that the usbtest device driver in the Linux
kernel did not properly validate endpoint metadata. A physically proximate
attacker could use this to cause a denial of service (system crash).
(CVE-2017-16532)
Andrey Konovalov discovered that the USB subsystem in the Linux kernel did
not properly validate USB HID descriptors. A physically proximate attacker
could use this to cause a denial of service (system crash).
(CVE-2017-16533)
Andrey Konovalov discovered that the USB subsystem in the Linux kernel did
not properly validate USB BOS metadata. A physically proximate attacker
could use this to cause a denial of service (system crash).
(CVE-2017-16535)
Andrey Konovalov discovered that the Conexant cx231xx USB video capture
driver in the Linux kernel did not properly validate interface descriptors.
A physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2017-16536)
Andrey Konovalov discovered that the SoundGraph iMON USB driver in the
Linux kernel did not properly validate device metadata. A physically
proximate attacker could use this to cause a denial of service (system
crash). (CVE-2017-16537)
It was discovered that the DM04/QQBOX USB driver in the Linux kernel did
not properly handle device attachment and warm-start. A physically
proximate attacker could use this to cause a denial of service (system
crash) or possibly execute arbitrary code. (CVE-2017-16538)
Andrey Konovalov discovered an out-of-bounds read in the GTCO digitizer USB
driver for the Linux kernel. A physically proximate attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-16643)
Andrey Konovalov discovered that the video4linux driver for Hauppauge HD
PVR USB devices in the Linux kernel did not properly handle some error
conditions. A physically proximate attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2017-16644)
Andrey Konovalov discovered that the IMS Passenger Control Unit USB driver
in the Linux kernel did not properly validate device descriptors. A
physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2017-16645)
Andrey Konovalov discovered that the QMI WWAN USB driver did not properly
validate device descriptors. A physically proximate attacker could use this
to cause a denial of service (system crash). (CVE-2017-16650)
It was discovered that the USB Virtual Host Controller Interface (VHCI)
driver in the Linux kernel contained an information disclosure
vulnerability. A physically proximate attacker could use this to expose
sensitive information (kernel memory). (CVE-2017-16911)
It was discovered that the USB over IP implementation in the Linux kernel
did not validate endpoint numbers. A remote attacker could use this to
cause a denial of service (system crash). (CVE-2017-16912)
It was discovered that the USB over IP implementation in the Linux kernel
did not properly validate CMD_SUBMIT packets. A remote attacker could use
this to cause a denial of service (excessive memory consumption).
(CVE-2017-16913)
It was discovered that the USB over IP implementation in the Linux kernel
contained a NULL pointer dereference error. A remote attacker could use
this to cause a denial of service (system crash). (CVE-2017-16914)
It was discovered that the core USB subsystem in the Linux kernel did not
validate the number of configurations and interfaces in a device. A
physically proximate attacker could use this to cause a denial of service
(system crash). (CVE-2017-17558)
It was discovered that an integer overflow existed in the perf subsystem of
the Linux kernel. A local attacker could use this to cause a denial of
service (system crash). (CVE-2017-18255)
It was discovered that the keyring subsystem in the Linux kernel did not
properly prevent a user from creating keyrings for other users. A local
attacker could use this cause a denial of service or expose sensitive
information. (CVE-2017-18270)
Andy Lutomirski and Willy Tarreau discovered that the KVM implementation in
the Linux kernel did not properly emulate instructions on the SS segment
register. A local attacker in a guest virtual machine could use this to
cause a denial of service (guest OS crash) or possibly gain administrative
privileges in the guest OS. (CVE-2017-2583)
Dmitry Vyukov discovered that the KVM implementation in the Linux kernel
improperly emulated certain instructions. A local attacker could use this
to obtain sensitive information (kernel memory). (CVE-2017-2584)
It was discovered that the KLSI KL5KUSB105 serial-to-USB device driver in
the Linux kernel did not properly initialize memory related to logging. A
local attacker could use this to expose sensitive information (kernel
memory). (CVE-2017-5549)
Andrey Konovalov discovered an out-of-bounds access in the IPv6 Generic
Routing Encapsulation (GRE) tunneling implementation in the Linux kernel.
An attacker could use this to possibly expose sensitive information.
(CVE-2017-5897)
Andrey Konovalov discovered that the LLC subsytem in the Linux kernel did
not properly set up a destructor in certain situations. A local attacker
could use this to cause a denial of service (system crash). (CVE-2017-6345)
Dmitry Vyukov discovered race conditions in the Infrared (IrDA) subsystem
in the Linux kernel. A local attacker could use this to cause a denial of
service (deadlock). (CVE-2017-6348)
Andy Lutomirski discovered that the KVM implementation in the Linux kernel
was vulnerable to a debug exception error when single-stepping through a
syscall. A local attacker in a non-Linux guest vm could possibly use this
to gain administrative privileges in the guest vm. (CVE-2017-7518)
Tuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server
implementations in the Linux kernel did not properly handle certain long
RPC replies. A remote attacker could use this to cause a denial of service
(system crash). (CVE-2017-7645)
Pengfei Wang discovered that a race condition existed in the NXP SAA7164 TV
Decoder driver for the Linux kernel. A local attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2017-8831)
Pengfei Wang discovered that the Turtle Beach MultiSound audio device
driver in the Linux kernel contained race conditions when fetching from the
ring-buffer. A local attacker could use this to cause a denial of service
(infinite loop). (CVE-2017-9984, CVE-2017-9985)
It was discovered that the wait4() system call in the Linux kernel did not
properly validate its arguments in some situations. A local attacker could
possibly use this to cause a denial of service. (CVE-2018-10087)
It was discovered that the kill() system call implementation in the Linux
kernel did not properly validate its arguments in some situations. A local
attacker could possibly use this to cause a denial of service.
(CVE-2018-10124)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Zhong Jiang discovered that a use-after-free vulnerability existed in the
NUMA memory policy implementation in the Linux kernel. A local attacker
could use this to cause a denial of service (system crash) or possibly
execute arbitrary code. (CVE-2018-10675)
Wen Xu discovered that a buffer overflow existed in the ext4 filesystem
implementation in the Linux kernel. An attacker could use this to construct
a malicious ext4 image that, when mounted, could cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2018-10877)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 file system that caused
a denial of service (system crash) when mounted. (CVE-2018-1092)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
It was discovered that the cdrom driver in the Linux kernel contained an
incorrect bounds check. A local attacker could use this to expose sensitive
information (kernel memory). (CVE-2018-10940)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Daniel Jiang discovered that a race condition existed in the ipv4 ping
socket implementation in the Linux kernel. A local privileged attacker
could use this to cause a denial of service (system crash). (CVE-2017-2671)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
It was discovered that a memory leak existed in the Serial Attached SCSI
(SAS) implementation in the Linux kernel. A physically proximate attacker
could use this to cause a denial of service (memory exhaustion).
(CVE-2018-10021)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 14.04 LTS:
linux-image-3.13.0-157-generic 3.13.0-157.207
linux-image-3.13.0-157-generic-lpae 3.13.0-157.207
linux-image-3.13.0-157-lowlatency 3.13.0-157.207
linux-image-3.13.0-157-powerpc-e500 3.13.0-157.207
linux-image-3.13.0-157-powerpc-e500mc 3.13.0-157.207
linux-image-3.13.0-157-powerpc-smp 3.13.0-157.207
linux-image-3.13.0-157-powerpc64-emb 3.13.0-157.207
linux-image-3.13.0-157-powerpc64-smp 3.13.0-157.207
linux-image-generic 3.13.0.157.167
linux-image-generic-lpae 3.13.0.157.167
linux-image-lowlatency 3.13.0.157.167
linux-image-powerpc-e500 3.13.0.157.167
linux-image-powerpc-e500mc 3.13.0.157.167
linux-image-powerpc-smp 3.13.0.157.167
linux-image-powerpc64-emb 3.13.0.157.167
linux-image-powerpc64-smp 3.13.0.157.167
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3754-1
CVE-2016-10208, CVE-2017-11472, CVE-2017-11473, CVE-2017-14991,
CVE-2017-15649, CVE-2017-16526, CVE-2017-16527, CVE-2017-16529,
CVE-2017-16531, CVE-2017-16532, CVE-2017-16533, CVE-2017-16535,
CVE-2017-16536, CVE-2017-16537, CVE-2017-16538, CVE-2017-16643,
CVE-2017-16644, CVE-2017-16645, CVE-2017-16650, CVE-2017-16911,
CVE-2017-16912, CVE-2017-16913, CVE-2017-16914, CVE-2017-17558,
CVE-2017-18255, CVE-2017-18270, CVE-2017-2583, CVE-2017-2584,
CVE-2017-2671, CVE-2017-5549, CVE-2017-5897, CVE-2017-6345,
CVE-2017-6348, CVE-2017-7518, CVE-2017-7645, CVE-2017-8831,
CVE-2017-9984, CVE-2017-9985, CVE-2018-1000204, CVE-2018-10021,
CVE-2018-10087, CVE-2018-10124, CVE-2018-10323, CVE-2018-10675,
CVE-2018-10877, CVE-2018-10881, CVE-2018-1092, CVE-2018-1093,
CVE-2018-10940, CVE-2018-12233, CVE-2018-13094, CVE-2018-13405,
CVE-2018-13406
Package Information:
https://launchpad.net/ubuntu/+source/linux/3.13.0-157.207
[USN-3753-2] Linux kernel (Xenial HWE) vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3753-2
August 24, 2018
linux-lts-xenial, linux-aws vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux-aws: Linux kernel for Amazon Web Services (AWS) systems
- linux-lts-xenial: Linux hardware enablement kernel from Xenial for Trusty
Details:
USN-3753-1 fixed vulnerabilities in the Linux kernel for Ubuntu 16.04
LTS. This update provides the corresponding updates for the Linux
Hardware Enablement (HWE) kernel from Ubuntu 16.04 LTS for Ubuntu
14.04 LTS.
It was discovered that the generic SCSI driver in the Linux kernel did not
properly enforce permissions on kernel memory access. A local attacker
could use this to expose sensitive information or possibly elevate
privileges. (CVE-2017-13168)
Wen Xu discovered that a use-after-free vulnerability existed in the ext4
filesystem implementation in the Linux kernel. An attacker could use this
to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10876, CVE-2018-10879)
Wen Xu discovered that a buffer overflow existed in the ext4 filesystem
implementation in the Linux kernel. An attacker could use this to construct
a malicious ext4 image that, when mounted, could cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2018-10877)
Wen Xu discovered that an out-of-bounds write vulnerability existed in the
ext4 filesystem implementation in the Linux kernel. An attacker could use
this to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10878, CVE-2018-10882)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 14.04 LTS:
linux-image-4.4.0-1028-aws 4.4.0-1028.31
linux-image-4.4.0-134-generic 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-generic-lpae 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-lowlatency 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc-e500mc 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc-smp 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc64-emb 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc64-smp 4.4.0-134.160~14.04.1
linux-image-aws 4.4.0.1028.28
linux-image-generic-lpae-lts-xenial 4.4.0.134.114
linux-image-generic-lts-xenial 4.4.0.134.114
linux-image-lowlatency-lts-xenial 4.4.0.134.114
linux-image-powerpc-e500mc-lts-xenial 4.4.0.134.114
linux-image-powerpc-smp-lts-xenial 4.4.0.134.114
linux-image-powerpc64-emb-lts-xenial 4.4.0.134.114
linux-image-powerpc64-smp-lts-xenial 4.4.0.134.114
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3753-2
https://usn.ubuntu.com/usn/usn-3753-1
CVE-2017-13168, CVE-2018-10876, CVE-2018-10877, CVE-2018-10878,
CVE-2018-10879, CVE-2018-10881, CVE-2018-10882, CVE-2018-12233,
CVE-2018-13094, CVE-2018-13405, CVE-2018-13406
Package Information:
https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1028.31
https://launchpad.net/ubuntu/+source/linux-lts-xenial/4.4.0-134.160~14.04.1
Ubuntu Security Notice USN-3753-2
August 24, 2018
linux-lts-xenial, linux-aws vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 14.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux-aws: Linux kernel for Amazon Web Services (AWS) systems
- linux-lts-xenial: Linux hardware enablement kernel from Xenial for Trusty
Details:
USN-3753-1 fixed vulnerabilities in the Linux kernel for Ubuntu 16.04
LTS. This update provides the corresponding updates for the Linux
Hardware Enablement (HWE) kernel from Ubuntu 16.04 LTS for Ubuntu
14.04 LTS.
It was discovered that the generic SCSI driver in the Linux kernel did not
properly enforce permissions on kernel memory access. A local attacker
could use this to expose sensitive information or possibly elevate
privileges. (CVE-2017-13168)
Wen Xu discovered that a use-after-free vulnerability existed in the ext4
filesystem implementation in the Linux kernel. An attacker could use this
to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10876, CVE-2018-10879)
Wen Xu discovered that a buffer overflow existed in the ext4 filesystem
implementation in the Linux kernel. An attacker could use this to construct
a malicious ext4 image that, when mounted, could cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2018-10877)
Wen Xu discovered that an out-of-bounds write vulnerability existed in the
ext4 filesystem implementation in the Linux kernel. An attacker could use
this to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10878, CVE-2018-10882)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 14.04 LTS:
linux-image-4.4.0-1028-aws 4.4.0-1028.31
linux-image-4.4.0-134-generic 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-generic-lpae 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-lowlatency 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc-e500mc 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc-smp 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc64-emb 4.4.0-134.160~14.04.1
linux-image-4.4.0-134-powerpc64-smp 4.4.0-134.160~14.04.1
linux-image-aws 4.4.0.1028.28
linux-image-generic-lpae-lts-xenial 4.4.0.134.114
linux-image-generic-lts-xenial 4.4.0.134.114
linux-image-lowlatency-lts-xenial 4.4.0.134.114
linux-image-powerpc-e500mc-lts-xenial 4.4.0.134.114
linux-image-powerpc-smp-lts-xenial 4.4.0.134.114
linux-image-powerpc64-emb-lts-xenial 4.4.0.134.114
linux-image-powerpc64-smp-lts-xenial 4.4.0.134.114
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3753-2
https://usn.ubuntu.com/usn/usn-3753-1
CVE-2017-13168, CVE-2018-10876, CVE-2018-10877, CVE-2018-10878,
CVE-2018-10879, CVE-2018-10881, CVE-2018-10882, CVE-2018-12233,
CVE-2018-13094, CVE-2018-13405, CVE-2018-13406
Package Information:
https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1028.31
https://launchpad.net/ubuntu/+source/linux-lts-xenial/4.4.0-134.160~14.04.1
[USN-3753-1] Linux kernel vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3753-1
August 24, 2018
linux, linux-aws, linux-kvm, linux-raspi2, linux-snapdragon vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
- linux-aws: Linux kernel for Amazon Web Services (AWS) systems
- linux-kvm: Linux kernel for cloud environments
- linux-raspi2: Linux kernel for Raspberry Pi 2
- linux-snapdragon: Linux kernel for Snapdragon processors
Details:
It was discovered that the generic SCSI driver in the Linux kernel did not
properly enforce permissions on kernel memory access. A local attacker
could use this to expose sensitive information or possibly elevate
privileges. (CVE-2017-13168)
Wen Xu discovered that a use-after-free vulnerability existed in the ext4
filesystem implementation in the Linux kernel. An attacker could use this
to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10876, CVE-2018-10879)
Wen Xu discovered that a buffer overflow existed in the ext4 filesystem
implementation in the Linux kernel. An attacker could use this to construct
a malicious ext4 image that, when mounted, could cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2018-10877)
Wen Xu discovered that an out-of-bounds write vulnerability existed in the
ext4 filesystem implementation in the Linux kernel. An attacker could use
this to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10878, CVE-2018-10882)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 LTS:
linux-image-4.4.0-1032-kvm 4.4.0-1032.38
linux-image-4.4.0-1066-aws 4.4.0-1066.76
linux-image-4.4.0-1095-raspi2 4.4.0-1095.103
linux-image-4.4.0-1099-snapdragon 4.4.0-1099.104
linux-image-4.4.0-134-generic 4.4.0-134.160
linux-image-4.4.0-134-generic-lpae 4.4.0-134.160
linux-image-4.4.0-134-lowlatency 4.4.0-134.160
linux-image-4.4.0-134-powerpc-e500mc 4.4.0-134.160
linux-image-4.4.0-134-powerpc-smp 4.4.0-134.160
linux-image-4.4.0-134-powerpc64-emb 4.4.0-134.160
linux-image-4.4.0-134-powerpc64-smp 4.4.0-134.160
linux-image-aws 4.4.0.1066.68
linux-image-generic 4.4.0.134.140
linux-image-generic-lpae 4.4.0.134.140
linux-image-kvm 4.4.0.1032.31
linux-image-lowlatency 4.4.0.134.140
linux-image-powerpc-e500mc 4.4.0.134.140
linux-image-powerpc-smp 4.4.0.134.140
linux-image-powerpc64-emb 4.4.0.134.140
linux-image-powerpc64-smp 4.4.0.134.140
linux-image-raspi2 4.4.0.1095.95
linux-image-snapdragon 4.4.0.1099.91
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3753-1
CVE-2017-13168, CVE-2018-10876, CVE-2018-10877, CVE-2018-10878,
CVE-2018-10879, CVE-2018-10881, CVE-2018-10882, CVE-2018-12233,
CVE-2018-13094, CVE-2018-13405, CVE-2018-13406
Package Information:
https://launchpad.net/ubuntu/+source/linux/4.4.0-134.160
https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1066.76
https://launchpad.net/ubuntu/+source/linux-kvm/4.4.0-1032.38
https://launchpad.net/ubuntu/+source/linux-raspi2/4.4.0-1095.103
https://launchpad.net/ubuntu/+source/linux-snapdragon/4.4.0-1099.104
Ubuntu Security Notice USN-3753-1
August 24, 2018
linux, linux-aws, linux-kvm, linux-raspi2, linux-snapdragon vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
- linux-aws: Linux kernel for Amazon Web Services (AWS) systems
- linux-kvm: Linux kernel for cloud environments
- linux-raspi2: Linux kernel for Raspberry Pi 2
- linux-snapdragon: Linux kernel for Snapdragon processors
Details:
It was discovered that the generic SCSI driver in the Linux kernel did not
properly enforce permissions on kernel memory access. A local attacker
could use this to expose sensitive information or possibly elevate
privileges. (CVE-2017-13168)
Wen Xu discovered that a use-after-free vulnerability existed in the ext4
filesystem implementation in the Linux kernel. An attacker could use this
to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10876, CVE-2018-10879)
Wen Xu discovered that a buffer overflow existed in the ext4 filesystem
implementation in the Linux kernel. An attacker could use this to construct
a malicious ext4 image that, when mounted, could cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2018-10877)
Wen Xu discovered that an out-of-bounds write vulnerability existed in the
ext4 filesystem implementation in the Linux kernel. An attacker could use
this to construct a malicious ext4 image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10878, CVE-2018-10882)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 LTS:
linux-image-4.4.0-1032-kvm 4.4.0-1032.38
linux-image-4.4.0-1066-aws 4.4.0-1066.76
linux-image-4.4.0-1095-raspi2 4.4.0-1095.103
linux-image-4.4.0-1099-snapdragon 4.4.0-1099.104
linux-image-4.4.0-134-generic 4.4.0-134.160
linux-image-4.4.0-134-generic-lpae 4.4.0-134.160
linux-image-4.4.0-134-lowlatency 4.4.0-134.160
linux-image-4.4.0-134-powerpc-e500mc 4.4.0-134.160
linux-image-4.4.0-134-powerpc-smp 4.4.0-134.160
linux-image-4.4.0-134-powerpc64-emb 4.4.0-134.160
linux-image-4.4.0-134-powerpc64-smp 4.4.0-134.160
linux-image-aws 4.4.0.1066.68
linux-image-generic 4.4.0.134.140
linux-image-generic-lpae 4.4.0.134.140
linux-image-kvm 4.4.0.1032.31
linux-image-lowlatency 4.4.0.134.140
linux-image-powerpc-e500mc 4.4.0.134.140
linux-image-powerpc-smp 4.4.0.134.140
linux-image-powerpc64-emb 4.4.0.134.140
linux-image-powerpc64-smp 4.4.0.134.140
linux-image-raspi2 4.4.0.1095.95
linux-image-snapdragon 4.4.0.1099.91
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3753-1
CVE-2017-13168, CVE-2018-10876, CVE-2018-10877, CVE-2018-10878,
CVE-2018-10879, CVE-2018-10881, CVE-2018-10882, CVE-2018-12233,
CVE-2018-13094, CVE-2018-13405, CVE-2018-13406
Package Information:
https://launchpad.net/ubuntu/+source/linux/4.4.0-134.160
https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1066.76
https://launchpad.net/ubuntu/+source/linux-kvm/4.4.0-1032.38
https://launchpad.net/ubuntu/+source/linux-raspi2/4.4.0-1095.103
https://launchpad.net/ubuntu/+source/linux-snapdragon/4.4.0-1099.104
[USN-3752-1] Linux kernel vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3752-1
August 24, 2018
linux, linux-aws, linux-gcp, linux-kvm, linux-raspi2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
- linux-aws: Linux kernel for Amazon Web Services (AWS) systems
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
- linux-kvm: Linux kernel for cloud environments
- linux-raspi2: Linux kernel for Raspberry Pi 2
Details:
It was discovered that, when attempting to handle an out-of-memory
situation, a null pointer dereference could be triggered in the Linux
kernel in some circumstances. A local attacker could use this to cause a
denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate xattr information. An attacker could use
this to construct a malicious xfs image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed
data reported that it was in a ready state before it had gathered
sufficient entropy. An attacker could use this to expose sensitive
information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle
processes mapping some memory elements onto files. A local attacker could
use this to block utilities that examine the procfs filesystem to report
operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep xattr information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer
overflow in the CDROM driver implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket
handling code in the Linux kernel. A local attacker could use this to cause
a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel
did not properly perform permission checks in some situations when nested
virtualization is used. An attacker in a guest VM could possibly use this
to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Jakub Jirasek discovered that multiple use-after-free errors existed in the
USB/IP implementation in the Linux kernel. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5814)
It was discovered that a race condition existed in the ARM Advanced
Microcontroller Bus Architecture (AMBA) driver in the Linux kernel that
could result in a double free. A local attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-9415)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
linux-image-4.15.0-1018-gcp 4.15.0-1018.19
linux-image-4.15.0-1020-aws 4.15.0-1020.20
linux-image-4.15.0-1020-kvm 4.15.0-1020.20
linux-image-4.15.0-1021-raspi2 4.15.0-1021.23
linux-image-4.15.0-33-generic 4.15.0-33.36
linux-image-4.15.0-33-generic-lpae 4.15.0-33.36
linux-image-4.15.0-33-lowlatency 4.15.0-33.36
linux-image-4.15.0-33-snapdragon 4.15.0-33.36
linux-image-aws 4.15.0.1020.20
linux-image-gcp 4.15.0.1018.20
linux-image-generic 4.15.0.33.35
linux-image-generic-lpae 4.15.0.33.35
linux-image-gke 4.15.0.1018.20
linux-image-kvm 4.15.0.1020.20
linux-image-lowlatency 4.15.0.33.35
linux-image-raspi2 4.15.0.1021.19
linux-image-snapdragon 4.15.0.33.35
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3752-1
CVE-2018-1000200, CVE-2018-1000204, CVE-2018-10323, CVE-2018-10840,
CVE-2018-10881, CVE-2018-1093, CVE-2018-1108, CVE-2018-1120,
CVE-2018-11412, CVE-2018-11506, CVE-2018-12232, CVE-2018-12233,
CVE-2018-12904, CVE-2018-13094, CVE-2018-13405, CVE-2018-13406,
CVE-2018-5814, CVE-2018-9415
Package Information:
https://launchpad.net/ubuntu/+source/linux/4.15.0-33.36
https://launchpad.net/ubuntu/+source/linux-aws/4.15.0-1020.20
https://launchpad.net/ubuntu/+source/linux-gcp/4.15.0-1018.19
https://launchpad.net/ubuntu/+source/linux-kvm/4.15.0-1020.20
https://launchpad.net/ubuntu/+source/linux-raspi2/4.15.0-1021.23
Ubuntu Security Notice USN-3752-1
August 24, 2018
linux, linux-aws, linux-gcp, linux-kvm, linux-raspi2 vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 18.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux: Linux kernel
- linux-aws: Linux kernel for Amazon Web Services (AWS) systems
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
- linux-kvm: Linux kernel for cloud environments
- linux-raspi2: Linux kernel for Raspberry Pi 2
Details:
It was discovered that, when attempting to handle an out-of-memory
situation, a null pointer dereference could be triggered in the Linux
kernel in some circumstances. A local attacker could use this to cause a
denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate xattr information. An attacker could use
this to construct a malicious xfs image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed
data reported that it was in a ready state before it had gathered
sufficient entropy. An attacker could use this to expose sensitive
information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle
processes mapping some memory elements onto files. A local attacker could
use this to block utilities that examine the procfs filesystem to report
operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep xattr information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer
overflow in the CDROM driver implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket
handling code in the Linux kernel. A local attacker could use this to cause
a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel
did not properly perform permission checks in some situations when nested
virtualization is used. An attacker in a guest VM could possibly use this
to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Jakub Jirasek discovered that multiple use-after-free errors existed in the
USB/IP implementation in the Linux kernel. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5814)
It was discovered that a race condition existed in the ARM Advanced
Microcontroller Bus Architecture (AMBA) driver in the Linux kernel that
could result in a double free. A local attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-9415)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 18.04 LTS:
linux-image-4.15.0-1018-gcp 4.15.0-1018.19
linux-image-4.15.0-1020-aws 4.15.0-1020.20
linux-image-4.15.0-1020-kvm 4.15.0-1020.20
linux-image-4.15.0-1021-raspi2 4.15.0-1021.23
linux-image-4.15.0-33-generic 4.15.0-33.36
linux-image-4.15.0-33-generic-lpae 4.15.0-33.36
linux-image-4.15.0-33-lowlatency 4.15.0-33.36
linux-image-4.15.0-33-snapdragon 4.15.0-33.36
linux-image-aws 4.15.0.1020.20
linux-image-gcp 4.15.0.1018.20
linux-image-generic 4.15.0.33.35
linux-image-generic-lpae 4.15.0.33.35
linux-image-gke 4.15.0.1018.20
linux-image-kvm 4.15.0.1020.20
linux-image-lowlatency 4.15.0.33.35
linux-image-raspi2 4.15.0.1021.19
linux-image-snapdragon 4.15.0.33.35
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3752-1
CVE-2018-1000200, CVE-2018-1000204, CVE-2018-10323, CVE-2018-10840,
CVE-2018-10881, CVE-2018-1093, CVE-2018-1108, CVE-2018-1120,
CVE-2018-11412, CVE-2018-11506, CVE-2018-12232, CVE-2018-12233,
CVE-2018-12904, CVE-2018-13094, CVE-2018-13405, CVE-2018-13406,
CVE-2018-5814, CVE-2018-9415
Package Information:
https://launchpad.net/ubuntu/+source/linux/4.15.0-33.36
https://launchpad.net/ubuntu/+source/linux-aws/4.15.0-1020.20
https://launchpad.net/ubuntu/+source/linux-gcp/4.15.0-1018.19
https://launchpad.net/ubuntu/+source/linux-kvm/4.15.0-1020.20
https://launchpad.net/ubuntu/+source/linux-raspi2/4.15.0-1021.23
[USN-3752-2] Linux kernel (HWE) vulnerabilities
==========================================================================
Ubuntu Security Notice USN-3752-2
August 24, 2018
linux-hwe vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux-hwe: Linux hardware enablement (HWE) kernel
Details:
USN-3752-1 fixed vulnerabilities in the Linux kernel for Ubuntu 18.04
LTS. This update provides the corresponding updates for the Linux
Hardware Enablement (HWE) kernel from Ubuntu 18.04 LTS for Ubuntu
16.04 LTS.
It was discovered that, when attempting to handle an out-of-memory
situation, a null pointer dereference could be triggered in the Linux
kernel in some circumstances. A local attacker could use this to cause a
denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate xattr information. An attacker could use
this to construct a malicious xfs image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed
data reported that it was in a ready state before it had gathered
sufficient entropy. An attacker could use this to expose sensitive
information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle
processes mapping some memory elements onto files. A local attacker could
use this to block utilities that examine the procfs filesystem to report
operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep xattr information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer
overflow in the CDROM driver implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket
handling code in the Linux kernel. A local attacker could use this to cause
a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel
did not properly perform permission checks in some situations when nested
virtualization is used. An attacker in a guest VM could possibly use this
to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Jakub Jirasek discovered that multiple use-after-free errors existed in the
USB/IP implementation in the Linux kernel. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5814)
It was discovered that a race condition existed in the ARM Advanced
Microcontroller Bus Architecture (AMBA) driver in the Linux kernel that
could result in a double free. A local attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-9415)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 LTS:
linux-image-4.15.0-33-generic 4.15.0-33.36~16.04.1
linux-image-4.15.0-33-generic-lpae 4.15.0-33.36~16.04.1
linux-image-4.15.0-33-lowlatency 4.15.0-33.36~16.04.1
linux-image-generic-hwe-16.04 4.15.0.33.55
linux-image-generic-lpae-hwe-16.04 4.15.0.33.55
linux-image-lowlatency-hwe-16.04 4.15.0.33.55
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3752-2
https://usn.ubuntu.com/usn/usn-3752-1
CVE-2018-1000200, CVE-2018-1000204, CVE-2018-10323, CVE-2018-10840,
CVE-2018-10881, CVE-2018-1093, CVE-2018-1108, CVE-2018-1120,
CVE-2018-11412, CVE-2018-11506, CVE-2018-12232, CVE-2018-12233,
CVE-2018-12904, CVE-2018-13094, CVE-2018-13405, CVE-2018-13406,
CVE-2018-5814, CVE-2018-9415
Package Information:
https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-33.36~16.04.1
Ubuntu Security Notice USN-3752-2
August 24, 2018
linux-hwe vulnerabilities
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 16.04 LTS
Summary:
Several security issues were fixed in the Linux kernel.
Software Description:
- linux-hwe: Linux hardware enablement (HWE) kernel
Details:
USN-3752-1 fixed vulnerabilities in the Linux kernel for Ubuntu 18.04
LTS. This update provides the corresponding updates for the Linux
Hardware Enablement (HWE) kernel from Ubuntu 18.04 LTS for Ubuntu
16.04 LTS.
It was discovered that, when attempting to handle an out-of-memory
situation, a null pointer dereference could be triggered in the Linux
kernel in some circumstances. A local attacker could use this to cause a
denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate meta-data information. An attacker could
use this to construct a malicious xfs image that, when mounted, could cause
a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly validate xattr information. An attacker could use
this to construct a malicious xfs image that, when mounted, could cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep meta-data information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash).
(CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux
kernel did not properly handle corrupted meta data in some situations. An
attacker could use this to specially craft an ext4 filesystem that caused a
denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed
data reported that it was in a ready state before it had gathered
sufficient entropy. An attacker could use this to expose sensitive
information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle
processes mapping some memory elements onto files. A local attacker could
use this to block utilities that examine the procfs filesystem to report
operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux
kernel did not properly keep xattr information consistent in some
situations. An attacker could use this to construct a malicious ext4 image
that, when mounted, could cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer
overflow in the CDROM driver implementation of the Linux kernel. A local
attacker could use this to cause a denial of service (system crash) or
possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket
handling code in the Linux kernel. A local attacker could use this to cause
a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the
Linux kernel contained a buffer overflow when handling extended attributes.
A local attacker could use this to cause a denial of service (system crash)
or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel
did not properly perform permission checks in some situations when nested
virtualization is used. An attacker in a guest VM could possibly use this
to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux
kernel did not properly handle an error condition with a corrupted xfs
image. An attacker could use this to construct a malicious xfs image that,
when mounted, could cause a denial of service (system crash).
(CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file
creation when performed by a non-member of the group. A local attacker
could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the
Linux kernel contained an integer overflow. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-13406)
Jakub Jirasek discovered that multiple use-after-free errors existed in the
USB/IP implementation in the Linux kernel. A local attacker could use this
to cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2018-5814)
It was discovered that a race condition existed in the ARM Advanced
Microcontroller Bus Architecture (AMBA) driver in the Linux kernel that
could result in a double free. A local attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2018-9415)
It was discovered that an information leak existed in the generic SCSI
driver in the Linux kernel. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2018-1000204)
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 16.04 LTS:
linux-image-4.15.0-33-generic 4.15.0-33.36~16.04.1
linux-image-4.15.0-33-generic-lpae 4.15.0-33.36~16.04.1
linux-image-4.15.0-33-lowlatency 4.15.0-33.36~16.04.1
linux-image-generic-hwe-16.04 4.15.0.33.55
linux-image-generic-lpae-hwe-16.04 4.15.0.33.55
linux-image-lowlatency-hwe-16.04 4.15.0.33.55
After a standard system update you need to reboot your computer to make
all the necessary changes.
ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed.
Unless you manually uninstalled the standard kernel metapackages
(e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
linux-powerpc), a standard system upgrade will automatically perform
this as well.
References:
https://usn.ubuntu.com/usn/usn-3752-2
https://usn.ubuntu.com/usn/usn-3752-1
CVE-2018-1000200, CVE-2018-1000204, CVE-2018-10323, CVE-2018-10840,
CVE-2018-10881, CVE-2018-1093, CVE-2018-1108, CVE-2018-1120,
CVE-2018-11412, CVE-2018-11506, CVE-2018-12232, CVE-2018-12233,
CVE-2018-12904, CVE-2018-13094, CVE-2018-13405, CVE-2018-13406,
CVE-2018-5814, CVE-2018-9415
Package Information:
https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-33.36~16.04.1
OpenBSD Errata: August 24th, 2018 (vmml1tf)
Errata patches for the kernel have been released for OpenBSD 6.3 and 6.2.
The Intel L1TF bug allows a vmm guest to read host memory.
Binary updates for the amd64 platform are available via the syspatch utility.
Source code patches can be found on the respective errata pages:
https://www.openbsd.org/errata62.html
https://www.openbsd.org/errata63.html
Run the fw_update command to get updated CPU microcode before rebooting.
If your machine has SMT ("hyper-threading") capability, it must be disabled
in the BIOS.
The CPU microcode update is not available for OpenBSD 6.2, so a BIOS update
is required to receive the accelerated L1 cache solution there.
The Intel L1TF bug allows a vmm guest to read host memory.
Binary updates for the amd64 platform are available via the syspatch utility.
Source code patches can be found on the respective errata pages:
https://www.openbsd.org/errata62.html
https://www.openbsd.org/errata63.html
Run the fw_update command to get updated CPU microcode before rebooting.
If your machine has SMT ("hyper-threading") capability, it must be disabled
in the BIOS.
The CPU microcode update is not available for OpenBSD 6.2, so a BIOS update
is required to receive the accelerated L1 cache solution there.
OpenBSD Errata: August 24th, 2018 (fpufork)
Errata patches for the kernel have been released for OpenBSD 6.3 and 6.2.
State from the FPU of one userland process could be exposed to other
processes.
Binary updates for the amd64 platform are available via the syspatch utility.
Source code patches can be found on the respective errata pages:
https://www.openbsd.org/errata62.html
https://www.openbsd.org/errata63.html
As these affect the kernel, a reboot will be needed after patching.
State from the FPU of one userland process could be exposed to other
processes.
Binary updates for the amd64 platform are available via the syspatch utility.
Source code patches can be found on the respective errata pages:
https://www.openbsd.org/errata62.html
https://www.openbsd.org/errata63.html
As these affect the kernel, a reboot will be needed after patching.
copr-frontend: fix for webhook secrets leakage
Hello,
there have been security problem fixed in copr-frontend today. Basically by forking, you could get to webhook secrets of an original project being forked. Also the integration page where you can insert pagure api token was actually available under certain URL if you knew how this URL should be structured. Both of these problems are now fixed. See full details here: https://lists.fedoraproject.org/archives/list/copr-devel@lists.fedorahosted.org/thread/VOOOVQ4VOZIB4GKXZWSX7REWCX3WVTLN/
We will do full security audits now to prevent any future problems like this.
Sorry for this trouble
Copr team
Wednesday, August 22, 2018
Fedora 30 System-Wide Change proposal: Remove the Group: Tag From All Packages
https://fedoraproject.org/wiki/Changes/Remove_Group_Tag
== Summary ==
Remove the Group: tag from over 9000 source packages.
== Owner ==
* Name: Jason Tibbitts (tibbs)
* Email: tibbs@math.uh.edu
== Detailed Description ==
I will remove the Group: tag from all specfiles in Fedora dist-git
which still have it, verify that the result is syntactically correct,
then commit and push the change. Since this is a relatively minor
changeI am not planning to bump Release: or add %changelog entries,
but I do that if it is deemed necessary.
I am proposing this as an official change instead of just doing it (as
with other low risk packaging cleanups) because:
* It would be by far the largest mass package change we would ever
have attempted.
* It does technically cause a visible change in the resulting package.
If queried, rpm will show the group as "Unspecified" for every binary
package in the distribution instead of just the majority of them. It
is theoretically possible that someone could have a tool which uses
this information, although that tool most already be mostly useless.
* People would yell at me even more loudly if I posted the full 9000+
package and maintainer listing.
Since this changes many, many packages and has small but nonzero end
user visibility I am filing this as a system-wide change.
== Benefit to Fedora ==
9420 source packages (43% of the total count) come closer to
compliance with Fedora's packaging guidelines. The Group: tag has
been in a "should not use" state since March of 2017.
More useless cruft is removed from specfiles. This provides a slight
benefit to ease of maintenance and eliminates yet another bizarre
historical relic which confuses new packagers. Cargo cult behavior is
rampant and removing the cruft in one go will be another step towards
having system-wide clean specfiles.
The Group: tag is not required in any live Fedora or EPEL release.
RHEL5 did need it, but EPEL5 did not as it was supplied automatically
via magic in the epel-rpm-macros package. The
[[Packaging:Guidelines#Tags_and_Sections|Packaging Guidelines]] have
indicated that the Group: tag should not be used since March of 2017.
The tag is not used by Fedora currently; the concept was replaced long
ago by comps which permits a far more flexible classification of
packages. dnf has a "group" subcommand but this operates on comps
groups, not anything defined by the Group: tag. dnf does not display
information from Group: tag. If a package does include a Group: tag,
a direct rpm query will display it but otherwise will show
"Unspecified".
There was never any strong standard for the contents of the Group:
tag. Older versions of rpm (still present in RHEL7 but not in any
live Fedora release) contained a documentation file named GROUPS with
a list and rpmlint would check this, but it was never strongly adhered
to. The current package set has some quality examples like a Group
tag containing the string "Group:" and one containing only
"evelopment/Languages". It seems relatively obvious that nobody is
paying attention or making use of that data.
Among the tags which are at least in the recommended set which rpm
used to have, most do not convey particularly useful information. Of
the Group: tags which remain, 5438 contain "Development/Libraries",
1871 have "System Environment/Libraries" and 1346 are
"Development/Languages".
== Scope ==
* Proposal owners: Whip up a quick script, test it well to ensure that
it doesn't have unintended side effects, and handle outliers or
special cases manually. Then wait a few hours to push commits to
9000+ repositories.
* Other developers: Nothing besides dealing with any commit emails they receive.
* Release engineering: There should be no releng involvement. There
is no real need for any packages to be rebuilt. If there is an F30
rebuild scheduled, it would be advantageous for this change to be made
before that happens. I filed [https://pagure.io/releng/issue/7627] in
any case.
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List
of deliverables]]: There should be no change to deliverables besides
the fact that the packages no longer have Group: tags.
* Policies and guidelines: This is implementing a requirement of the
current packaging guidelines. The specific change mandating this
happened in March of 2017.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
There is no effect on upgrades. Packagers have always been free to
remove Group: tags, even within a stable release. This will simply
result in the rest of them going away.
== How To Test ==
There is not much to test. The change is simple and so if done with a
modicum of care it will not cause syntax errors in the packages.
Testers and maintainers can of course do local or koji builds after
the changes have been pushed to ensure that there are no problems, and
rpm -qip run on the resulting binary packages should only show Group:
tags of "Unspecified".
== User Experience ==
There should be no change to the end user experience unless there is
an expectation that the Group: tags of the changed packages will show
something other than "Unspecified".
== Dependencies ==
There are no dependencies.
== Contingency Plan ==
If there is some issue, it is simply possible to do nothing, or to
change only a subset of packages.
If changes are committed and it turns out that there is some
unforeseen negative effect, the changes can simply be reverted.
* Contingency mechanism: Either do nothing, or revert the changes in
the unlikely event that they cause issues.
* Contingency deadline: Before the mass rebuild.
* Blocks release? No
* Blocks product? N/A
== Documentation ==
The process is generally obvious and should not require much in the
way of involvement of anyone else.
== Release Notes ==
There should be no need to note this change in any release notes, as
it is merely the completion of a change which has been ongoing since
the time of Fedora 12.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/HVDGFF2DOLYKZCL7PJOSEI6UJJRQ5M77/
== Summary ==
Remove the Group: tag from over 9000 source packages.
== Owner ==
* Name: Jason Tibbitts (tibbs)
* Email: tibbs@math.uh.edu
== Detailed Description ==
I will remove the Group: tag from all specfiles in Fedora dist-git
which still have it, verify that the result is syntactically correct,
then commit and push the change. Since this is a relatively minor
changeI am not planning to bump Release: or add %changelog entries,
but I do that if it is deemed necessary.
I am proposing this as an official change instead of just doing it (as
with other low risk packaging cleanups) because:
* It would be by far the largest mass package change we would ever
have attempted.
* It does technically cause a visible change in the resulting package.
If queried, rpm will show the group as "Unspecified" for every binary
package in the distribution instead of just the majority of them. It
is theoretically possible that someone could have a tool which uses
this information, although that tool most already be mostly useless.
* People would yell at me even more loudly if I posted the full 9000+
package and maintainer listing.
Since this changes many, many packages and has small but nonzero end
user visibility I am filing this as a system-wide change.
== Benefit to Fedora ==
9420 source packages (43% of the total count) come closer to
compliance with Fedora's packaging guidelines. The Group: tag has
been in a "should not use" state since March of 2017.
More useless cruft is removed from specfiles. This provides a slight
benefit to ease of maintenance and eliminates yet another bizarre
historical relic which confuses new packagers. Cargo cult behavior is
rampant and removing the cruft in one go will be another step towards
having system-wide clean specfiles.
The Group: tag is not required in any live Fedora or EPEL release.
RHEL5 did need it, but EPEL5 did not as it was supplied automatically
via magic in the epel-rpm-macros package. The
[[Packaging:Guidelines#Tags_and_Sections|Packaging Guidelines]] have
indicated that the Group: tag should not be used since March of 2017.
The tag is not used by Fedora currently; the concept was replaced long
ago by comps which permits a far more flexible classification of
packages. dnf has a "group" subcommand but this operates on comps
groups, not anything defined by the Group: tag. dnf does not display
information from Group: tag. If a package does include a Group: tag,
a direct rpm query will display it but otherwise will show
"Unspecified".
There was never any strong standard for the contents of the Group:
tag. Older versions of rpm (still present in RHEL7 but not in any
live Fedora release) contained a documentation file named GROUPS with
a list and rpmlint would check this, but it was never strongly adhered
to. The current package set has some quality examples like a Group
tag containing the string "Group:" and one containing only
"evelopment/Languages". It seems relatively obvious that nobody is
paying attention or making use of that data.
Among the tags which are at least in the recommended set which rpm
used to have, most do not convey particularly useful information. Of
the Group: tags which remain, 5438 contain "Development/Libraries",
1871 have "System Environment/Libraries" and 1346 are
"Development/Languages".
== Scope ==
* Proposal owners: Whip up a quick script, test it well to ensure that
it doesn't have unintended side effects, and handle outliers or
special cases manually. Then wait a few hours to push commits to
9000+ repositories.
* Other developers: Nothing besides dealing with any commit emails they receive.
* Release engineering: There should be no releng involvement. There
is no real need for any packages to be rebuilt. If there is an F30
rebuild scheduled, it would be advantageous for this change to be made
before that happens. I filed [https://pagure.io/releng/issue/7627] in
any case.
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List
of deliverables]]: There should be no change to deliverables besides
the fact that the packages no longer have Group: tags.
* Policies and guidelines: This is implementing a requirement of the
current packaging guidelines. The specific change mandating this
happened in March of 2017.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
There is no effect on upgrades. Packagers have always been free to
remove Group: tags, even within a stable release. This will simply
result in the rest of them going away.
== How To Test ==
There is not much to test. The change is simple and so if done with a
modicum of care it will not cause syntax errors in the packages.
Testers and maintainers can of course do local or koji builds after
the changes have been pushed to ensure that there are no problems, and
rpm -qip run on the resulting binary packages should only show Group:
tags of "Unspecified".
== User Experience ==
There should be no change to the end user experience unless there is
an expectation that the Group: tags of the changed packages will show
something other than "Unspecified".
== Dependencies ==
There are no dependencies.
== Contingency Plan ==
If there is some issue, it is simply possible to do nothing, or to
change only a subset of packages.
If changes are committed and it turns out that there is some
unforeseen negative effect, the changes can simply be reverted.
* Contingency mechanism: Either do nothing, or revert the changes in
the unlikely event that they cause issues.
* Contingency deadline: Before the mass rebuild.
* Blocks release? No
* Blocks product? N/A
== Documentation ==
The process is generally obvious and should not require much in the
way of involvement of anyone else.
== Release Notes ==
There should be no need to note this change in any release notes, as
it is merely the completion of a change which has been ongoing since
the time of Fedora 12.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/HVDGFF2DOLYKZCL7PJOSEI6UJJRQ5M77/
Fedora 30 System-Wide Change proposal: New 128-bit IEEE long double ABI for IBM 64-bit POWER LE
https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition
== Summary ==
Transition IBM 64-bit POWER LE systems to the new 128-bit IEEE long double ABI.
== Owner ==
* Name: Carlos O'Donell (codonell)
* Email: carlos@redhat.com
== Detailed Description ==
IBM has designed a new long double ABI that adheres to the 128-bit
IEEE format. This format is more standard than the existing AIX
double-double or IBM long double (2 grouped 64-bit doubles) which has
discontinuous mantissas and is difficult for developers to use. In
Fedora 29 the plan is to switch to the new ABI for long double, while
still supporting old applications via compatibility symbols. Newly
compiled applications use either the old or new ABI but not a mix of
both. Changes are required in the core C libraries, and the compiler
and the compiler runtimes including the C++ standard libraries.
Therefore there is coordination required across the core toolchain
componenents e.g. gcc, binutils, glibc, gdb (to debug the new types).
== Benefit to Fedora ==
Fedora developers will be using a standard 128-bit IEEE format for
long double instead of the non-standard double-double AIX format which
has a discontinuous mantissa and multiple representations for the same
value.
== Scope ==
The change is relatively limited in that not many packages use the
long double floating point ABI. The double floating point ABI is much
more used, but not long double. It is estimated that few packages use
long double directly, and those packages will need to be rebuilt in
order to use the new ABI. This rebuilding can be targetted by
analyzing which packages have long double usage in their debug
information and rebuilding just those packages. However, we plan to
just use the existing mass rebuild for glibc 2.29 to handle this
issue.
* Proposal owners: Transition glibc to float128 format for long double
for IBM ppc64le. Transition gcc to the default for long double.
Implement support for the new <code>long double</code> format in
libstdc++. Ensure gdb can handle the new types.
* Other developers: Developers need to ensure that rawhide is stable
and ready for the Fedora 30 branch.
* Release engineering: A mass rebuild request has been filed for the
parent system-wide change to upgrade glibc to
2.29<br>[https://pagure.io/releng/issue/7475 #7475]
* Policies and guidelines: The policies and guidelines do not need to
be updated.
* Trademark approval: Not needed for this change
== Upgrade/compatibility impact ==
The library and language runtimes are backwards compatible with the
version shipped in Fedora.
We fully expect to fix all packaging changes in Fedora Rawhide first
when everything is ready.
== How To Test ==
The GNU C Library has its own testsuite, which is run during the
package build and examined by the glibc developers before being
uploaded. This test suite has 2500+ tests that run to verify the
correct operation of the library. In the future we'll also be running
the microbenchmark to look for performance regressions as well as
behavioural ones.
Specific testing for 128-bit IEEE long double ABI will be carried out
by the glibc testsuite. Integration smoke testing will be carried out
by the glibc developers to make sure new applications are built with
the correct defaults and work as expected.
Specific testing for 128-bit IEEE long double ABI will be carried out
by the gcc testsuite.
Specific smoke testing will be carried out using gdb to read and write
the new types.
== User Experience ==
Users will see a new 128-bit floating point ABI, but this will largely
be transparent to them. On POWER hardware that supports 128-bit long
double in hardware the compiler will use the hardware transparently to
accelerate floating point operations, otherwise software floating
point emulation will be used.
== Dependencies ==
This change requires coordination of glibc and gcc to change the
compiler defaults and build the compiler language runtimes correctly.
Also gdb must be able to support the new type to make the process of
transition seamless.
== Contingency Plan ==
* Contingency mechanism: Ship glibc 2.28 instead of glibc 2.29, or
ship glibc 2.29 without this feature if it is not ready.
* Contingency deadline: Final mass rebuild before Fedora release.
* Blocks release? Upgrading glibc does block the release. We should
not ship without the float128 ABI change.
== Documentation ==
The glibc/gcc manual contain the documentation for the release and
don't need any more additional work.
== Release Notes ==
* The ppc64le architecture changed the format of the <code>long
double</code> type to binary128. (Previously, a pair of two doubles
was used.)
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/WXKBQDBDPFX27U62NLYENB4PEGS3WQ2E/
== Summary ==
Transition IBM 64-bit POWER LE systems to the new 128-bit IEEE long double ABI.
== Owner ==
* Name: Carlos O'Donell (codonell)
* Email: carlos@redhat.com
== Detailed Description ==
IBM has designed a new long double ABI that adheres to the 128-bit
IEEE format. This format is more standard than the existing AIX
double-double or IBM long double (2 grouped 64-bit doubles) which has
discontinuous mantissas and is difficult for developers to use. In
Fedora 29 the plan is to switch to the new ABI for long double, while
still supporting old applications via compatibility symbols. Newly
compiled applications use either the old or new ABI but not a mix of
both. Changes are required in the core C libraries, and the compiler
and the compiler runtimes including the C++ standard libraries.
Therefore there is coordination required across the core toolchain
componenents e.g. gcc, binutils, glibc, gdb (to debug the new types).
== Benefit to Fedora ==
Fedora developers will be using a standard 128-bit IEEE format for
long double instead of the non-standard double-double AIX format which
has a discontinuous mantissa and multiple representations for the same
value.
== Scope ==
The change is relatively limited in that not many packages use the
long double floating point ABI. The double floating point ABI is much
more used, but not long double. It is estimated that few packages use
long double directly, and those packages will need to be rebuilt in
order to use the new ABI. This rebuilding can be targetted by
analyzing which packages have long double usage in their debug
information and rebuilding just those packages. However, we plan to
just use the existing mass rebuild for glibc 2.29 to handle this
issue.
* Proposal owners: Transition glibc to float128 format for long double
for IBM ppc64le. Transition gcc to the default for long double.
Implement support for the new <code>long double</code> format in
libstdc++. Ensure gdb can handle the new types.
* Other developers: Developers need to ensure that rawhide is stable
and ready for the Fedora 30 branch.
* Release engineering: A mass rebuild request has been filed for the
parent system-wide change to upgrade glibc to
2.29<br>[https://pagure.io/releng/issue/7475 #7475]
* Policies and guidelines: The policies and guidelines do not need to
be updated.
* Trademark approval: Not needed for this change
== Upgrade/compatibility impact ==
The library and language runtimes are backwards compatible with the
version shipped in Fedora.
We fully expect to fix all packaging changes in Fedora Rawhide first
when everything is ready.
== How To Test ==
The GNU C Library has its own testsuite, which is run during the
package build and examined by the glibc developers before being
uploaded. This test suite has 2500+ tests that run to verify the
correct operation of the library. In the future we'll also be running
the microbenchmark to look for performance regressions as well as
behavioural ones.
Specific testing for 128-bit IEEE long double ABI will be carried out
by the glibc testsuite. Integration smoke testing will be carried out
by the glibc developers to make sure new applications are built with
the correct defaults and work as expected.
Specific testing for 128-bit IEEE long double ABI will be carried out
by the gcc testsuite.
Specific smoke testing will be carried out using gdb to read and write
the new types.
== User Experience ==
Users will see a new 128-bit floating point ABI, but this will largely
be transparent to them. On POWER hardware that supports 128-bit long
double in hardware the compiler will use the hardware transparently to
accelerate floating point operations, otherwise software floating
point emulation will be used.
== Dependencies ==
This change requires coordination of glibc and gcc to change the
compiler defaults and build the compiler language runtimes correctly.
Also gdb must be able to support the new type to make the process of
transition seamless.
== Contingency Plan ==
* Contingency mechanism: Ship glibc 2.28 instead of glibc 2.29, or
ship glibc 2.29 without this feature if it is not ready.
* Contingency deadline: Final mass rebuild before Fedora release.
* Blocks release? Upgrading glibc does block the release. We should
not ship without the float128 ABI change.
== Documentation ==
The glibc/gcc manual contain the documentation for the release and
don't need any more additional work.
== Release Notes ==
* The ppc64le architecture changed the format of the <code>long
double</code> type to binary128. (Previously, a pair of two doubles
was used.)
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/WXKBQDBDPFX27U62NLYENB4PEGS3WQ2E/
Fedora 30 System-Wide Change proposal: Remove glibc-all-langpacks from buildroot
https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_buildroot
== Summary ==
glibc-minimal-langpack is added to @Buildsystem group and installed
into the minimal buildroot instead of glibc-all-langpacks. Packages
which need more locales than plain C/C.UTF-8/POSIX need to pull them
in through BuildRequires.
== Owner ==
* Name: Zbigniew Jędrzejewski-Szmek (zbyszek)
* Email: zbyszek@in.waw.pl
== Detailed Description ==
Right now glibc-all-langpacks is installed in buildroots (mock, koji,
…).
It is 24 MB, out of the total of 145 MB. Replacing it with
glibc-minimal-langpack,
which has negligible size, decreases the buildroot size by 17%.
glibc Requires glibc-langpack, and Suggests glibc-all-langpacks, so it
gets installed automatically to satisfy that dependency. If a
different
package providing glibc-langpack is installed, glibc-all-langpacks is
skipped.
This change is basically adding glibc-minimal-langpack to @Buildsystem
in comps and fixing any fallout in packages.
A quick grep over spec files reveals:
```
$ rg -l 'LC_CTYPE=[^C]' *.spec | wc -l
11
$ rg -l 'LC_ALL=[^C]' *.spec | wc -l
42
```
that there are at least ~50 packages which need adjustment. They can
be either switched over to C.UTF-8 or a BuildRequires can be added.
== Benefit to Fedora ==
The minimal buildroot becomes smaller, making builds slightly faster.
== Scope ==
* Proposal owners:
** adjust comps
** fix packages which can be identified without rebuilding (see grep
output above)
** fix fallout in the mass rebuild if anything is missed above
* Other developers: report breakage and/or fix their own packages
* Release engineering: [https://pagure.io/releng/issue/7610 #7610]
* Policies and guidelines: no changes needed
(The Packaging Guidelines already specify that all necessary
dependencies must be declared using BuildRequires.)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
This only affect package building process, so it has no end-user impact.
== How To Test ==
Verify that packages still build after the comps change.
== User Experience ==
Not visible to end-users.
== Dependencies ==
None.
== Contingency Plan ==
Revert the comps change. Any changes in packages would be backwards
compatible, so there's no need to revert them. There is also no need
to rebuild any packages already successfully built.
* Contingency mechanism: remove glibc-minimal-langpack from @Buildsystem
* Blocks release? not directly, but if packages fail to build, it
would be problem
* Blocks product? no
== Documentation ==
None
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/WSV6XZGC24EJGHWVKG63OOJQFDZ6ITP6/
== Summary ==
glibc-minimal-langpack is added to @Buildsystem group and installed
into the minimal buildroot instead of glibc-all-langpacks. Packages
which need more locales than plain C/C.UTF-8/POSIX need to pull them
in through BuildRequires.
== Owner ==
* Name: Zbigniew Jędrzejewski-Szmek (zbyszek)
* Email: zbyszek@in.waw.pl
== Detailed Description ==
Right now glibc-all-langpacks is installed in buildroots (mock, koji,
…).
It is 24 MB, out of the total of 145 MB. Replacing it with
glibc-minimal-langpack,
which has negligible size, decreases the buildroot size by 17%.
glibc Requires glibc-langpack, and Suggests glibc-all-langpacks, so it
gets installed automatically to satisfy that dependency. If a
different
package providing glibc-langpack is installed, glibc-all-langpacks is
skipped.
This change is basically adding glibc-minimal-langpack to @Buildsystem
in comps and fixing any fallout in packages.
A quick grep over spec files reveals:
```
$ rg -l 'LC_CTYPE=[^C]' *.spec | wc -l
11
$ rg -l 'LC_ALL=[^C]' *.spec | wc -l
42
```
that there are at least ~50 packages which need adjustment. They can
be either switched over to C.UTF-8 or a BuildRequires can be added.
== Benefit to Fedora ==
The minimal buildroot becomes smaller, making builds slightly faster.
== Scope ==
* Proposal owners:
** adjust comps
** fix packages which can be identified without rebuilding (see grep
output above)
** fix fallout in the mass rebuild if anything is missed above
* Other developers: report breakage and/or fix their own packages
* Release engineering: [https://pagure.io/releng/issue/7610 #7610]
* Policies and guidelines: no changes needed
(The Packaging Guidelines already specify that all necessary
dependencies must be declared using BuildRequires.)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
This only affect package building process, so it has no end-user impact.
== How To Test ==
Verify that packages still build after the comps change.
== User Experience ==
Not visible to end-users.
== Dependencies ==
None.
== Contingency Plan ==
Revert the comps change. Any changes in packages would be backwards
compatible, so there's no need to revert them. There is also no need
to rebuild any packages already successfully built.
* Contingency mechanism: remove glibc-minimal-langpack from @Buildsystem
* Blocks release? not directly, but if packages fail to build, it
would be problem
* Blocks product? no
== Documentation ==
None
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/message/WSV6XZGC24EJGHWVKG63OOJQFDZ6ITP6/
Subscribe to:
Posts (Atom)