Wednesday, January 6, 2021

[USN-4683-1] Linux kernel (OEM) vulnerability

==========================================================================
Ubuntu Security Notice USN-4683-1
January 07, 2021

linux-oem-5.6 vulnerability
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 20.04 LTS

Summary:

The system could be made to crash or expose sensitive information
under certain conditions.

Software Description:
- linux-oem-5.6: Linux kernel for OEM systems

Details:

Minh Yuan discovered that the framebuffer console driver in the Linux
kernel did not properly handle fonts in some conditions. A local attacker
could use this to cause a denial of service (system crash) or possibly
expose sensitive information (kernel memory).

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 20.04 LTS:
linux-image-5.6.0-1039-oem 5.6.0-1039.43
linux-image-oem-20.04 5.6.0.1039.37

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/4683-1
CVE-2020-28974

Package Information:
https://launchpad.net/ubuntu/+source/linux-oem-5.6/5.6.0-1039.43

[announce] Streaming link

Hello Folks,
Here is the streaming link for tonight:



adplug: SOname bump coming to released Fedora

I've submitted an update for adplug yesterday for all released branches of
Fedora (and EPEL), because it addresses 8 CVEs.

https://bodhi.fedoraproject.org/updates/?search=adplug-2.3.3

The API is compatible (but ABI bump), so it will just require a rebuild for
dependent packages. Given only two dependent packages in Fedora (and one in
EPEL), I've done the few required rebuilds already.


Regards,
Robert

[USN-4677-2] p11-kit vulnerability

==========================================================================
Ubuntu Security Notice USN-4677-2
January 06, 2021

p11-kit vulnerability
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 14.04 ESM

Summary:

Several security issues were fixed in p11-kit.

Software Description:
- p11-kit: p11-glue utilities

Details:

USN-4677-1 fixed a vulnerability in p11-kit. This update provides
the corresponding update for Ubuntu 14.04 ESM.

Original advisory details:

David Cook discovered that p11-kit incorrectly handled certain memory
operations. An attacker could use this issue to cause p11-kit to crash,
resulting in a denial of service, or possibly execute arbitrary code.

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 14.04 ESM:
libp11-kit0 0.20.2-2ubuntu2+esm1
p11-kit 0.20.2-2ubuntu2+esm1
p11-kit-modules 0.20.2-2ubuntu2+esm1

In general, a standard system update will make all the necessary changes.

References:
https://usn.ubuntu.com/4677-2
https://usn.ubuntu.com/4677-1
CVE-2020-29361

[announce] RSVPs for tonight's meeting

Please have RSVPs in by 12 noon EST today. Details will be sent out in
the early afternoon. RSVPs after 12 noon EST will receive meeting
details later in the day.

****


Next NYC*BUG: Jan 6th at 18:45 EST (23:45 UTC) NYC*BUG will host a Zoom
meeting entitled:

Chatting About TLS and Orcs, by Michael W. Lucas

More info:
https://www.nycbug.org/index?action=view&id=10679

For Zoom meeting details, email to rsvp AT lists.nycbug.org, and
details will be sent on the day of the meeting.

As with our successful December meeting entitled:
For the Love of Troff, by James K. Lowden
We will be fielding questions over IRC at #nycbug on Freenode
_______________________________________________
announce mailing list
announce@lists.nycbug.org
http://lists.nycbug.org:8080/mailman/listinfo/announce

[USN-4682-1] WavPack vulnerability

==========================================================================
Ubuntu Security Notice USN-4682-1
January 06, 2021

wavpack vulnerability
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 20.10
- Ubuntu 20.04 LTS
- Ubuntu 18.04 LTS

Summary:

WavPack could be made to execute arbitrary code or crash if it received a specially
crafted WAV file.

Software Description:
- wavpack: audio codec (lossy and lossless) - encoder and decoder

Details:

It was discovered that WavPack incorrectly handled certain WAV files.
An attacker could possibly use this issue to execute arbitrary code or
cause a crash.

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 20.10:
wavpack 5.3.0-1ubuntu0.1

Ubuntu 20.04 LTS:
wavpack 5.2.0-1ubuntu0.1

Ubuntu 18.04 LTS:
wavpack 5.1.0-2ubuntu1.5

In general, a standard system update will make all the necessary changes.

References:
https://usn.ubuntu.com/4682-1
CVE-2020-35738

Package Information:
https://launchpad.net/ubuntu/+source/wavpack/5.3.0-1ubuntu0.1
https://launchpad.net/ubuntu/+source/wavpack/5.2.0-1ubuntu0.1
https://launchpad.net/ubuntu/+source/wavpack/5.1.0-2ubuntu1.5

Tuesday, January 5, 2021

[USN-4681-1] Linux kernel vulnerabilities

==========================================================================
Ubuntu Security Notice USN-4681-1
January 06, 2021

linux, linux-aws, linux-kvm, linux-lts-xenial, linux-raspi2,
linux-snapdragon vulnerabilities
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 16.04 LTS
- Ubuntu 14.04 ESM

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 (V8) systems
- linux-snapdragon: Linux kernel for Qualcomm Snapdragon processors
- linux-lts-xenial: Linux hardware enablement kernel from Xenial for Trusty

Details:

Ryan Hall discovered that the Intel 700 Series Ethernet Controllers driver
in the Linux kernel did not properly deallocate memory in some conditions.
A local attacker could use this to cause a denial of service (kernel memory
exhaustion). (CVE-2019-0148)

It was discovered that the console keyboard driver in the Linux kernel
contained a race condition. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2020-25656)

Minh Yuan discovered that the tty driver in the Linux kernel contained race
conditions when handling fonts. A local attacker could possibly use this to
expose sensitive information (kernel memory). (CVE-2020-25668)

Jinoh Kang discovered that the Xen event channel infrastructure in the
Linux kernel contained a race condition. An attacker in guest could
possibly use this to cause a denial of service (dom0 crash).
(CVE-2020-27675)

Minh Yuan discovered that the framebuffer console driver in the Linux
kernel did not properly handle fonts in some conditions. A local attacker
could use this to cause a denial of service (system crash) or possibly
expose sensitive information (kernel memory). (CVE-2020-28974)

It was discovered that Power 9 processors could be coerced to expose
information from the L1 cache in certain situations. A local attacker could
use this to expose sensitive information. (CVE-2020-4788)

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-1085-kvm 4.4.0-1085.94
linux-image-4.4.0-1119-aws 4.4.0-1119.133
linux-image-4.4.0-1143-raspi2 4.4.0-1143.153
linux-image-4.4.0-1147-snapdragon 4.4.0-1147.157
linux-image-4.4.0-198-generic 4.4.0-198.230
linux-image-4.4.0-198-generic-lpae 4.4.0-198.230
linux-image-4.4.0-198-lowlatency 4.4.0-198.230
linux-image-4.4.0-198-powerpc-e500mc 4.4.0-198.230
linux-image-4.4.0-198-powerpc-smp 4.4.0-198.230
linux-image-4.4.0-198-powerpc64-emb 4.4.0-198.230
linux-image-4.4.0-198-powerpc64-smp 4.4.0-198.230
linux-image-aws 4.4.0.1119.124
linux-image-generic 4.4.0.198.204
linux-image-generic-lpae 4.4.0.198.204
linux-image-kvm 4.4.0.1085.83
linux-image-lowlatency 4.4.0.198.204
linux-image-powerpc-e500mc 4.4.0.198.204
linux-image-powerpc-smp 4.4.0.198.204
linux-image-powerpc64-emb 4.4.0.198.204
linux-image-powerpc64-smp 4.4.0.198.204
linux-image-raspi2 4.4.0.1143.143
linux-image-snapdragon 4.4.0.1147.139
linux-image-virtual 4.4.0.198.204

Ubuntu 14.04 ESM:
linux-image-4.4.0-1083-aws 4.4.0-1083.87
linux-image-4.4.0-198-generic 4.4.0-198.230~14.04.1
linux-image-4.4.0-198-generic-lpae 4.4.0-198.230~14.04.1
linux-image-4.4.0-198-lowlatency 4.4.0-198.230~14.04.1
linux-image-4.4.0-198-powerpc-e500mc 4.4.0-198.230~14.04.1
linux-image-4.4.0-198-powerpc-smp 4.4.0-198.230~14.04.1
linux-image-4.4.0-198-powerpc64-emb 4.4.0-198.230~14.04.1
linux-image-4.4.0-198-powerpc64-smp 4.4.0-198.230~14.04.1
linux-image-aws 4.4.0.1083.80
linux-image-generic-lpae-lts-xenial 4.4.0.198.173
linux-image-generic-lts-xenial 4.4.0.198.173
linux-image-lowlatency-lts-xenial 4.4.0.198.173
linux-image-powerpc-e500mc-lts-xenial 4.4.0.198.173
linux-image-powerpc-smp-lts-xenial 4.4.0.198.173
linux-image-powerpc64-emb-lts-xenial 4.4.0.198.173
linux-image-powerpc64-smp-lts-xenial 4.4.0.198.173
linux-image-virtual-lts-xenial 4.4.0.198.173

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/4681-1
CVE-2019-0148, CVE-2020-25656, CVE-2020-25668, CVE-2020-27675,
CVE-2020-28974, CVE-2020-4788

Package Information:
https://launchpad.net/ubuntu/+source/linux/4.4.0-198.230
https://launchpad.net/ubuntu/+source/linux-aws/4.4.0-1119.133
https://launchpad.net/ubuntu/+source/linux-kvm/4.4.0-1085.94
https://launchpad.net/ubuntu/+source/linux-raspi2/4.4.0-1143.153
https://launchpad.net/ubuntu/+source/linux-snapdragon/4.4.0-1147.157

[USN-4678-1] Linux kernel vulnerabilities

==========================================================================
Ubuntu Security Notice USN-4678-1
January 06, 2021

linux, linux-aws, linux-azure, linux-gcp, linux-kvm, linux-oracle,
linux-raspi vulnerabilities
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 20.10

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-azure: Linux kernel for Microsoft Azure Cloud systems
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
- linux-kvm: Linux kernel for cloud environments
- linux-oracle: Linux kernel for Oracle Cloud systems
- linux-raspi: Linux kernel for Raspberry Pi (V8) systems

Details:

It was discovered that the AMD Running Average Power Limit (RAPL) driver in
the Linux kernel did not properly restrict access to power data. A local
attacker could possibly use this to expose sensitive information.
(CVE-2020-12912)

Jann Horn discovered that the io_uring subsystem in the Linux kernel did
not properly perform reference counting in some situations. A local
attacker could use this to expose sensitive information or possibly
escalate privileges. (CVE-2020-29534)

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 20.10:
linux-image-5.8.0-1011-raspi 5.8.0-1011.14
linux-image-5.8.0-1011-raspi-nolpae 5.8.0-1011.14
linux-image-5.8.0-1014-kvm 5.8.0-1014.15
linux-image-5.8.0-1014-oracle 5.8.0-1014.14
linux-image-5.8.0-1015-gcp 5.8.0-1015.15
linux-image-5.8.0-1016-azure 5.8.0-1016.17
linux-image-5.8.0-1017-aws 5.8.0-1017.18
linux-image-5.8.0-34-generic 5.8.0-34.37
linux-image-5.8.0-34-generic-64k 5.8.0-34.37
linux-image-5.8.0-34-generic-lpae 5.8.0-34.37
linux-image-5.8.0-34-lowlatency 5.8.0-34.37
linux-image-aws 5.8.0.1017.19
linux-image-azure 5.8.0.1016.16
linux-image-gcp 5.8.0.1015.15
linux-image-generic 5.8.0.34.39
linux-image-generic-64k 5.8.0.34.39
linux-image-generic-lpae 5.8.0.34.39
linux-image-gke 5.8.0.1015.15
linux-image-kvm 5.8.0.1014.16
linux-image-lowlatency 5.8.0.34.39
linux-image-oracle 5.8.0.1014.14
linux-image-raspi 5.8.0.1011.14
linux-image-raspi-nolpae 5.8.0.1011.14
linux-image-virtual 5.8.0.34.39

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/4678-1
CVE-2020-12912, CVE-2020-29534

Package Information:
https://launchpad.net/ubuntu/+source/linux/5.8.0-34.37
https://launchpad.net/ubuntu/+source/linux-aws/5.8.0-1017.18
https://launchpad.net/ubuntu/+source/linux-azure/5.8.0-1016.17
https://launchpad.net/ubuntu/+source/linux-gcp/5.8.0-1015.15
https://launchpad.net/ubuntu/+source/linux-kvm/5.8.0-1014.15
https://launchpad.net/ubuntu/+source/linux-oracle/5.8.0-1014.14
https://launchpad.net/ubuntu/+source/linux-raspi/5.8.0-1011.14

[USN-4680-1] Linux kernel vulnerabilities

==========================================================================
Ubuntu Security Notice USN-4680-1
January 06, 2021

linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-gcp,
linux-gcp-4.15, linux-gke-4.15, linux-hwe, linux-kvm, linux-oracle,
linux-raspi2, linux-snapdragon vulnerabilities
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
- Ubuntu 14.04 ESM

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-azure-4.15: Linux kernel for Microsoft Azure Cloud systems
- linux-gcp-4.15: Linux kernel for Google Cloud Platform (GCP) systems
- linux-gke-4.15: Linux kernel for Google Container Engine (GKE) systems
- linux-kvm: Linux kernel for cloud environments
- linux-oracle: Linux kernel for Oracle Cloud systems
- linux-raspi2: Linux kernel for Raspberry Pi (V8) systems
- linux-snapdragon: Linux kernel for Qualcomm Snapdragon processors
- linux-aws-hwe: Linux kernel for Amazon Web Services (AWS-HWE) systems
- linux-azure: Linux kernel for Microsoft Azure Cloud systems
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
- linux-hwe: Linux hardware enablement (HWE) kernel

Details:

It was discovered that debugfs in the Linux kernel as used by blktrace
contained a use-after-free in some situations. A privileged local attacker
could possibly use this to cause a denial of service (system crash).
(CVE-2019-19770)

It was discovered that a race condition existed in the binder IPC
implementation in the Linux kernel, leading to 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-2020-0423)

Daniele Antonioli, Nils Ole Tippenhauer, and Kasper Rasmussen discovered
that legacy pairing and secure-connections pairing authentication in the
Bluetooth protocol could allow an unauthenticated user to complete
authentication without pairing credentials via adjacent access. A
physically proximate attacker could use this to impersonate a previously
paired Bluetooth device. (CVE-2020-10135)

It was discovered that the console keyboard driver in the Linux kernel
contained a race condition. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2020-25656)

Minh Yuan discovered that the tty driver in the Linux kernel contained race
conditions when handling fonts. A local attacker could possibly use this to
expose sensitive information (kernel memory). (CVE-2020-25668)

Keyu Man discovered that the ICMP global rate limiter in the Linux kernel
could be used to assist in scanning open UDP ports. A remote attacker could
use to facilitate attacks on UDP based services that depend on source port
randomization. (CVE-2020-25705)

Jinoh Kang discovered that the Xen event channel infrastructure in the
Linux kernel contained a race condition. An attacker in guest could
possibly use this to cause a denial of service (dom0 crash).
(CVE-2020-27675)

Daniel Axtens discovered that PowerPC RTAS implementation in the Linux
kernel did not properly restrict memory accesses in some situations. A
privileged local attacker could use this to arbitrarily modify kernel
memory, potentially bypassing kernel lockdown restrictions.
(CVE-2020-27777)

Minh Yuan discovered that the framebuffer console driver in the Linux
kernel did not properly handle fonts in some conditions. A local attacker
could use this to cause a denial of service (system crash) or possibly
expose sensitive information (kernel memory). (CVE-2020-28974)

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-1062-oracle 4.15.0-1062.68
linux-image-4.15.0-1077-gke 4.15.0-1077.82
linux-image-4.15.0-1077-raspi2 4.15.0-1077.82
linux-image-4.15.0-1082-kvm 4.15.0-1082.84
linux-image-4.15.0-1091-aws 4.15.0-1091.96
linux-image-4.15.0-1091-gcp 4.15.0-1091.104
linux-image-4.15.0-1094-snapdragon 4.15.0-1094.103
linux-image-4.15.0-1103-azure 4.15.0-1103.114
linux-image-4.15.0-129-generic 4.15.0-129.132
linux-image-4.15.0-129-generic-lpae 4.15.0-129.132
linux-image-4.15.0-129-lowlatency 4.15.0-129.132
linux-image-aws-lts-18.04 4.15.0.1091.93
linux-image-azure-lts-18.04 4.15.0.1103.76
linux-image-gcp-lts-18.04 4.15.0.1091.109
linux-image-generic 4.15.0.129.116
linux-image-generic-lpae 4.15.0.129.116
linux-image-gke 4.15.0.1077.81
linux-image-gke-4.15 4.15.0.1077.81
linux-image-kvm 4.15.0.1082.78
linux-image-lowlatency 4.15.0.129.116
linux-image-oracle-lts-18.04 4.15.0.1062.72
linux-image-powerpc-e500mc 4.15.0.129.116
linux-image-powerpc-smp 4.15.0.129.116
linux-image-powerpc64-emb 4.15.0.129.116
linux-image-powerpc64-smp 4.15.0.129.116
linux-image-raspi2 4.15.0.1077.74
linux-image-snapdragon 4.15.0.1094.97
linux-image-virtual 4.15.0.129.116

Ubuntu 16.04 LTS:
linux-image-4.15.0-1062-oracle 4.15.0-1062.68~16.04.1
linux-image-4.15.0-1091-aws 4.15.0-1091.96~16.04.1
linux-image-4.15.0-1091-gcp 4.15.0-1091.104~16.04.1
linux-image-4.15.0-1103-azure 4.15.0-1103.114~16.04.1
linux-image-4.15.0-129-generic 4.15.0-129.132~16.04.1
linux-image-4.15.0-129-generic-lpae 4.15.0-129.132~16.04.1
linux-image-4.15.0-129-lowlatency 4.15.0-129.132~16.04.1
linux-image-aws-hwe 4.15.0.1091.85
linux-image-azure 4.15.0.1103.96
linux-image-gcp 4.15.0.1091.92
linux-image-generic-hwe-16.04 4.15.0.129.128
linux-image-generic-lpae-hwe-16.04 4.15.0.129.128
linux-image-gke 4.15.0.1091.92
linux-image-lowlatency-hwe-16.04 4.15.0.129.128
linux-image-oem 4.15.0.129.128
linux-image-oracle 4.15.0.1062.51
linux-image-virtual-hwe-16.04 4.15.0.129.128

Ubuntu 14.04 ESM:
linux-image-4.15.0-1103-azure 4.15.0-1103.114~14.04.1
linux-image-azure 4.15.0.1103.78

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/4680-1
CVE-2019-19770, CVE-2020-0423, CVE-2020-10135, CVE-2020-25656,
CVE-2020-25668, CVE-2020-25705, CVE-2020-27675, CVE-2020-27777,
CVE-2020-28974

Package Information:
https://launchpad.net/ubuntu/+source/linux/4.15.0-129.132
https://launchpad.net/ubuntu/+source/linux-aws/4.15.0-1091.96
https://launchpad.net/ubuntu/+source/linux-azure-4.15/4.15.0-1103.114
https://launchpad.net/ubuntu/+source/linux-gcp-4.15/4.15.0-1091.104
https://launchpad.net/ubuntu/+source/linux-gke-4.15/4.15.0-1077.82
https://launchpad.net/ubuntu/+source/linux-kvm/4.15.0-1082.84
https://launchpad.net/ubuntu/+source/linux-oracle/4.15.0-1062.68
https://launchpad.net/ubuntu/+source/linux-raspi2/4.15.0-1077.82
https://launchpad.net/ubuntu/+source/linux-snapdragon/4.15.0-1094.103
https://launchpad.net/ubuntu/+source/linux-aws-hwe/4.15.0-1091.96~16.04.1
https://launchpad.net/ubuntu/+source/linux-azure/4.15.0-1103.114~16.04.1
https://launchpad.net/ubuntu/+source/linux-gcp/4.15.0-1091.104~16.04.1
https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-129.132~16.04.1
https://launchpad.net/ubuntu/+source/linux-oracle/4.15.0-1062.68~16.04.1

[USN-4679-1] Linux kernel vulnerabilities

==========================================================================
Ubuntu Security Notice USN-4679-1
January 06, 2021

linux, linux-aws, linux-aws-5.4, linux-azure, linux-azure-5.4, linux-gcp,
linux-gcp-5.4, linux-gke-5.4, linux-hwe-5.4, linux-kvm, linux-oracle,
linux-oracle-5.4, linux-raspi, linux-raspi-5.4 vulnerabilities
==========================================================================

A security issue affects these releases of Ubuntu and its derivatives:

- Ubuntu 20.04 LTS
- 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-azure: Linux kernel for Microsoft Azure Cloud systems
- linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
- linux-kvm: Linux kernel for cloud environments
- linux-oracle: Linux kernel for Oracle Cloud systems
- linux-raspi: Linux kernel for Raspberry Pi (V8) systems
- linux-aws-5.4: Linux kernel for Amazon Web Services (AWS) systems
- linux-azure-5.4: Linux kernel for Microsoft Azure cloud systems
- linux-gcp-5.4: Linux kernel for Google Cloud Platform (GCP) systems
- linux-gke-5.4: Linux kernel for Google Container Engine (GKE) systems
- linux-hwe-5.4: Linux hardware enablement (HWE) kernel
- linux-oracle-5.4: Linux kernel for Oracle Cloud systems
- linux-raspi-5.4: Linux kernel for Raspberry Pi (V8) systems

Details:

It was discovered that the console keyboard driver in the Linux kernel
contained a race condition. A local attacker could use this to expose
sensitive information (kernel memory). (CVE-2020-25656)

Minh Yuan discovered that the tty driver in the Linux kernel contained race
conditions when handling fonts. A local attacker could possibly use this to
expose sensitive information (kernel memory). (CVE-2020-25668)

Kiyin (尹亮) discovered that the perf subsystem in the Linux kernel did
not properly deallocate memory in some situations. A privileged attacker
could use this to cause a denial of service (kernel memory exhaustion).
(CVE-2020-25704)

Jinoh Kang discovered that the Xen event channel infrastructure in the
Linux kernel contained a race condition. An attacker in guest could
possibly use this to cause a denial of service (dom0 crash).
(CVE-2020-27675)

Daniel Axtens discovered that PowerPC RTAS implementation in the Linux
kernel did not properly restrict memory accesses in some situations. A
privileged local attacker could use this to arbitrarily modify kernel
memory, potentially bypassing kernel lockdown restrictions.
(CVE-2020-27777)

Minh Yuan discovered that the framebuffer console driver in the Linux
kernel did not properly handle fonts in some conditions. A local attacker
could use this to cause a denial of service (system crash) or possibly
expose sensitive information (kernel memory). (CVE-2020-28974)

Update instructions:

The problem can be corrected by updating your system to the following
package versions:

Ubuntu 20.04 LTS:
linux-image-5.4.0-1026-raspi 5.4.0-1026.29
linux-image-5.4.0-1031-kvm 5.4.0-1031.32
linux-image-5.4.0-1033-gcp 5.4.0-1033.35
linux-image-5.4.0-1034-aws 5.4.0-1034.35
linux-image-5.4.0-1034-oracle 5.4.0-1034.36
linux-image-5.4.0-1035-azure 5.4.0-1035.36
linux-image-5.4.0-59-generic 5.4.0-59.65
linux-image-5.4.0-59-generic-lpae 5.4.0-59.65
linux-image-5.4.0-59-lowlatency 5.4.0-59.65
linux-image-aws 5.4.0.1034.35
linux-image-azure 5.4.0.1035.33
linux-image-gcp 5.4.0.1033.42
linux-image-generic 5.4.0.59.62
linux-image-generic-lpae 5.4.0.59.62
linux-image-kvm 5.4.0.1031.29
linux-image-lowlatency 5.4.0.59.62
linux-image-oem 5.4.0.59.62
linux-image-oem-osp1 5.4.0.59.62
linux-image-oracle 5.4.0.1034.31
linux-image-raspi 5.4.0.1026.61
linux-image-raspi2 5.4.0.1026.61
linux-image-virtual 5.4.0.59.62

Ubuntu 18.04 LTS:
linux-image-5.4.0-1026-raspi 5.4.0-1026.29~18.04.1
linux-image-5.4.0-1033-gcp 5.4.0-1033.35~18.04.1
linux-image-5.4.0-1033-gke 5.4.0-1033.35~18.04.1
linux-image-5.4.0-1034-aws 5.4.0-1034.35~18.04.1
linux-image-5.4.0-1034-oracle 5.4.0-1034.36~18.04.1
linux-image-5.4.0-1035-azure 5.4.0-1035.36~18.04.1
linux-image-5.4.0-59-generic 5.4.0-59.65~18.04.1
linux-image-5.4.0-59-generic-lpae 5.4.0-59.65~18.04.1
linux-image-5.4.0-59-lowlatency 5.4.0-59.65~18.04.1
linux-image-aws 5.4.0.1034.19
linux-image-azure 5.4.0.1035.17
linux-image-gcp 5.4.0.1033.21
linux-image-generic-hwe-18.04 5.4.0.59.65~18.04.54
linux-image-generic-lpae-hwe-18.04 5.4.0.59.65~18.04.54
linux-image-gke-5.4 5.4.0.1033.35~18.04.2
linux-image-lowlatency-hwe-18.04 5.4.0.59.65~18.04.54
linux-image-oem 5.4.0.59.65~18.04.54
linux-image-oem-osp1 5.4.0.59.65~18.04.54
linux-image-oracle 5.4.0.1034.36~18.04.18
linux-image-raspi-hwe-18.04 5.4.0.1026.30
linux-image-snapdragon-hwe-18.04 5.4.0.59.65~18.04.54
linux-image-virtual-hwe-18.04 5.4.0.59.65~18.04.54

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/4679-1
CVE-2020-25656, CVE-2020-25668, CVE-2020-25704, CVE-2020-27675,
CVE-2020-27777, CVE-2020-28974

Package Information:
https://launchpad.net/ubuntu/+source/linux/5.4.0-59.65
https://launchpad.net/ubuntu/+source/linux-aws/5.4.0-1034.35
https://launchpad.net/ubuntu/+source/linux-azure/5.4.0-1035.36
https://launchpad.net/ubuntu/+source/linux-gcp/5.4.0-1033.35
https://launchpad.net/ubuntu/+source/linux-kvm/5.4.0-1031.32
https://launchpad.net/ubuntu/+source/linux-oracle/5.4.0-1034.36
https://launchpad.net/ubuntu/+source/linux-raspi/5.4.0-1026.29
https://launchpad.net/ubuntu/+source/linux-aws-5.4/5.4.0-1034.35~18.04.1
https://launchpad.net/ubuntu/+source/linux-azure-5.4/5.4.0-1035.36~18.04.1
https://launchpad.net/ubuntu/+source/linux-gcp-5.4/5.4.0-1033.35~18.04.1
https://launchpad.net/ubuntu/+source/linux-gke-5.4/5.4.0-1033.35~18.04.1
https://launchpad.net/ubuntu/+source/linux-hwe-5.4/5.4.0-59.65~18.04.1
https://launchpad.net/ubuntu/+source/linux-oracle-5.4/5.4.0-1034.36~18.04.1
https://launchpad.net/ubuntu/+source/linux-raspi-5.4/5.4.0-1026.29~18.04.1

HOWTO: Change default branch on pagure.io projects

Per https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main#Phase0_-_2021-01-05
here's a short guide for any interested folks on how to change the
default branch in pagure.io projects:

Switching default branch from 'master' to 'main' on pagure.io

If you have an existing project using 'master' as it's default branch:
git clone ssh://git@pagure.io/YOURPROJECT.git
(This checks out your repo with it's current 'master' branch)

git checkout -b main
(This creates a local 'main' branch)

git push
(This pushes the new 'main' branch to pagure.io)

Go to your project, Settings, "Default Branch", set to 'main', click "Make Default"
(This switches the 'default' branch you get if you do not specify one)

git push origin :master
(This deletes the old 'master' branch)

If you have are just creating a new project:
When creating the project specify 'main' as the default branch.

(This will be changed soon to default that way)

Q&A:

Q: What happens to pull-requests that are against the old 'main' branch?
A: They will show an error, you will need to get the submitter to open a new pull-request
against the new branch name (we will be fixing pagure so it allows updating the
target branch of a PR in the (near) future)

Q: I want to call the default branch something else, do I have to use 'main'?
A: main is becoming a industry wide name, so people are going to expect it.
That said, it's your project and you can name it anything you like.

Q: What happens to Documentation/Issues/Pull Requests repos associated to the projects?
A: We are not changing anything on theses repos for now, we will update you when we change
the default branch on these repos.

Q: What happens to users who have a checkout of the old default branch?
A: If they do a 'git pull' they will get:

* [new branch] main -> origin/main
Your configuration specifies to merge with the ref 'refs/heads/master'
from the remote, but no such ref was fetched.

They need to do 'git checkout main' and pull will work fine again.

As a reminder, on 2021-01-06 (tomorrow), we will be changing the following pagure.io
repos to use 'main' as default branch:

pagure.io:
releng
releng/*
fedora-comps
fedora-kickstarts
fedora-infrastructure
fedora-lorax-templates
fedora-mediawikitheme
fedora-packager
fedora-infra/*
infra-docs
koji-fedmsg-plugin
workstation-ostree-config
pungi-fedora
fedora-docs/*
fedora-docs-i18n/*

See https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main
for more information.

kevin

Fedora 34 Change: Signed RPM Contents (late System-Wide Change)


Note that this change was submitted after the deadline, but since it can be shipped in an complete state, I am still processing it for Fedora 34.


== Summary ==
We want to add signatures to individual files that are part of shipped RPMs.
These signatures will use the Linux IMA (Integrity Measurement Architecture) scheme, which means they can be used to enforce runtime policies to ensure execution of only trusted files.

== Owner ==
* Name: [[User:Puiterwijk| Patrick Uiterwijk]]
* Email: puiterwijk@redhat.com
* Name: [[User:Pbrobinson| Peter Robinson]]
* Email: pbrobinson@gmail.com


== Detailed Description ==

During signing builds, the files in it will be signed with IMA signatures..
These signatures will be made with a key that's kept by the Fedora Infrastructure team, and installed on the sign vaults.


== Benefit to Fedora ==

Having all files signed with a verifiable key means that system owners can use the kernel Integrity and Measurement Architecture (IMA) to enforce only verified files can be executed, or define other policies.

== Scope ==
* Proposal owners:
The proposal owners will write the code for sigul to pass the required arguments, generate the keys in Infrastructure and get them deployed to the sign vaults.

* Other developers:
Nothing needed from other developers

* Release engineering:
A mass rebuild would be nice (as it ensures all packages are signed), but is not required to implement the change itself.

* Policies and guidelines:
No impact

* Trademark approval:
No impact

* Alignment with Objectives:
This aligns with the Internet of Things objective.

== Upgrade/compatibility impact ==
For standard Fedora users there will be no impact. If an advanced user was already signing their own files (for the Fedora shipped RPMs) for IMA functionality, they will just overwrite the existing signature.

== How To Test ==
The signatures can be tested "in vitro" by running `evmctl ima_verify --sigfile --key publiccert.der -v myfile.txt`.
This should result in the system reporting "<filename>: verification is OK".
The full system could be tested by enrolling the Fedora IMA key to the kernel `_ima` keyring, and adding a policy that verifies (some) files to be verified against the key.  (instructions to follow).

== User Experience ==
If the user deploys an IMA policy to verify all or some files, they should be able to trust the signatures made by the Fedora build system.

== Dependencies ==
No external package dependencies.

== Contingency Plan ==

* Contingency mechanism: If the change is not finished in time, we have probably not yet started signing new files. Signing can easily be disabled by updating the config file should issues arise.
If we did start signing, but haven't signed everything, that is okay, since then packages will get signed as they're bumped by developers, and they'll be all signed in the next major release.

* Contingency deadline: We could ship with this feature in an unfinished state.
* Blocks release? No
* Blocks product? N/A

== Documentation ==
Documentation to follow.


--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis