MGASA-2020-0140 - Updated kernel packages fix security vulnerabilities

Publication date: 13 Mar 2020
URL: https://advisories.mageia.org/MGASA-2020-0140.html
Type: security
Affected Mageia releases: 7
CVE: CVE-2019-19768,
     CVE-2020-8647,
     CVE-2020-8648,
     CVE-2020-8649,
     CVE-2020-9383,
     CVE-2020-9391

This update is based on upstream 5.5.9 and fixes atleast the following
security vulnerabilities:

In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the
__blk_add_trace function in kernel/trace/blktrace.c (which is used to
fill out a blk_io_trace structure and place it in a per-cpu sub-buffer)
(CVE-2019-19768).

There is a use-after-free vulnerability in the Linux kernel through 5.5.2
in the vc_do_resize function in drivers/tty/vt/vt.c (CVE-2020-8647).

There is a use-after-free vulnerability in the Linux kernel through 5.5.2
in the n_tty_receive_buf_common function in drivers/tty/n_tty.c
(CVE-2020-8648).

There is a use-after-free vulnerability in the Linux kernel through 5.5.2
in the vgacon_invert_region function in drivers/video/console/vgacon.c. 
(CVE-2020-8649).

An issue was discovered in the Linux kernel through 5.5.6. set_fdc in
drivers/block/floppy.c leads to a wait_til_ready out-of-bounds read
because the FDC index is not checked for errors before assigning it,
aka CID-2e90ca68b0d2 (CVE-2020-9383).

An issue was discovered in the Linux kernel 5.4 and 5.5 through 5.5.6
on the AArch64 architecture. It ignores the top byte in the address
passed to the brk system call, potentially moving the memory break
downwards when the application expects it to move upwards, aka CID-
dcde237319e6. This has been observed to cause heap corruption with
the GNU C Library malloc implementation (CVE-2020-9391).

Other notable changes in this update:
- kernel is built with the updated gcc-8.4.0, thus fixing the issue
  with nvidia drivers complaining about gcc mismatch and failing the
  dkms-nvidia* builds.
- ahci: Add Intel Comet Lake H RAID PCI ID
- update Amd Sensor Fusion Hub driver to v4
- replace staging exfat driver with new upstream exfat driver
- update rtl8812au driver for more hw support (mga#26178)
- fscrypt: don't evict dirty inodes after removing key

References:
- https://bugs.mageia.org/show_bug.cgi?id=26331
- https://bugs.mageia.org/show_bug.cgi?id=26178
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.7
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.8
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.9
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19768
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8647
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8648
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8649
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9383
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9391

SRPMS:
- 7/core/kernel-5.5.9-1.mga7
- 7/core/kmod-virtualbox-6.0.18-5.mga7
- 7/core/kmod-xtables-addons-3.8-5.mga7

Mageia 2020-0140: kernel security update

This update is based on upstream 5.5.9 and fixes atleast the following security vulnerabilities: In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_t...

Summary

This update is based on upstream 5.5.9 and fixes atleast the following security vulnerabilities:
In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_trace function in kernel/trace/blktrace.c (which is used to fill out a blk_io_trace structure and place it in a per-cpu sub-buffer) (CVE-2019-19768).
There is a use-after-free vulnerability in the Linux kernel through 5.5.2 in the vc_do_resize function in drivers/tty/vt/vt.c (CVE-2020-8647).
There is a use-after-free vulnerability in the Linux kernel through 5.5.2 in the n_tty_receive_buf_common function in drivers/tty/n_tty.c (CVE-2020-8648).
There is a use-after-free vulnerability in the Linux kernel through 5.5.2 in the vgacon_invert_region function in drivers/video/console/vgacon.c. (CVE-2020-8649).
An issue was discovered in the Linux kernel through 5.5.6. set_fdc in drivers/block/floppy.c leads to a wait_til_ready out-of-bounds read because the FDC index is not checked for errors before assigning it, aka CID-2e90ca68b0d2 (CVE-2020-9383).
An issue was discovered in the Linux kernel 5.4 and 5.5 through 5.5.6 on the AArch64 architecture. It ignores the top byte in the address passed to the brk system call, potentially moving the memory break downwards when the application expects it to move upwards, aka CID- dcde237319e6. This has been observed to cause heap corruption with the GNU C Library malloc implementation (CVE-2020-9391).
Other notable changes in this update: - kernel is built with the updated gcc-8.4.0, thus fixing the issue with nvidia drivers complaining about gcc mismatch and failing the dkms-nvidia* builds. - ahci: Add Intel Comet Lake H RAID PCI ID - update Amd Sensor Fusion Hub driver to v4 - replace staging exfat driver with new upstream exfat driver - update rtl8812au driver for more hw support (mga#26178) - fscrypt: don't evict dirty inodes after removing key

References

- https://bugs.mageia.org/show_bug.cgi?id=26331

- https://bugs.mageia.org/show_bug.cgi?id=26178

- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.7

- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.8

- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.9

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19768

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8647

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8648

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8649

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9383

- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9391

Resolution

MGASA-2020-0140 - Updated kernel packages fix security vulnerabilities

SRPMS

- 7/core/kernel-5.5.9-1.mga7

- 7/core/kmod-virtualbox-6.0.18-5.mga7

- 7/core/kmod-xtables-addons-3.8-5.mga7

Severity
Publication date: 13 Mar 2020
URL: https://advisories.mageia.org/MGASA-2020-0140.html
Type: security
CVE: CVE-2019-19768, CVE-2020-8647, CVE-2020-8648, CVE-2020-8649, CVE-2020-9383, CVE-2020-9391

Related News