Advisory
USN-4227-1
Also known as: CVE-2019-14895, CVE-2019-14896, CVE-2019-14897, CVE-2019-14901, CVE-2019-16231, CVE-2019-16233, CVE-2019-18660, CVE-2019-19045, CVE-2019-19052, CVE-2019-19083, CVE-2019-19524, CVE-2019-19529, CVE-2019-19534, CVE-2019-19807
Summary
linux, linux-aws, linux-aws-hwe, linux-azure, linux-gcp, linux-gke-4.15, linux-hwe, linux-kvm, linux-oem, linux-oracle, linux-raspi2, linux-snapdragon vulnerabilities
Details
It was discovered that a heap-based buffer overflow existed in the Marvell
WiFi-Ex 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-2019-14895, CVE-2019-14901)
It was discovered that a heap-based buffer overflow existed in the Marvell
Libertas WLAN 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-2019-14896, CVE-2019-14897)
It was discovered that the Fujitsu ES network device driver for the Linux
kernel did not properly check for errors in some situations, leading to a
NULL pointer dereference. A local attacker could use this to cause a denial
of service. (CVE-2019-16231)
It was discovered that the QLogic Fibre Channel driver in the Linux kernel
did not properly check for error, leading to a NULL pointer dereference. A
local attacker could possibly use this to cause a denial of service (system
crash). (CVE-2019-16233)
Anthony Steinhauser discovered that the Linux kernel did not properly
perform Spectre_RSB mitigations to all processors for PowerPC architecture
systems in some situations. A local attacker could use this to expose
sensitive information. (CVE-2019-18660)
It was discovered that the Mellanox Technologies Innova driver in the Linux
kernel did not properly deallocate memory in certain failure conditions. A
local attacker could use this to cause a denial of service (kernel memory
exhaustion). (CVE-2019-19045)
It was discovered that Geschwister Schneider USB CAN interface driver in
the Linux kernel did not properly deallocate memory in certain failure
conditions. A physically proximate attacker could use this to cause a
denial of service (kernel memory exhaustion). (CVE-2019-19052)
It was discovered that the AMD Display Engine Driver in the Linux kernel
did not properly deallocate memory in certain error conditions. A local
attack could use this to cause a denial of service (memory exhaustion).
(CVE-2019-19083)
It was discovered that the driver for memoryless force-feedback input
devices in the Linux kernel contained a use-after-free vulnerability. A
physically proximate attacker could possibly use this to cause a denial of
service (system crash) or execute arbitrary code. (CVE-2019-19524)
It was discovered that the Microchip CAN BUS Analyzer driver in the Linux
kernel contained a use-after-free vulnerability on device disconnect. A
physically proximate attacker could use this to cause a denial of service
(system crash) or possibly execute arbitrary code. (CVE-2019-19529)
It was discovered that the PEAK-System Technik USB driver in the Linux
kernel did not properly sanitize memory before sending it to the device. A
physically proximate attacker could use this to expose sensitive
information (kernel memory). (CVE-2019-19534)
Tristan Madani discovered that the ALSA timer implementation 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-2019-19807)
Severity
Not rated by the source.
Dates
- Published
- 2020-01-07 02:24 UTC
- Modified
- 2026-06-03 14:03 UTC
Affected packages and fixes
| Package | System | Fix |
|---|---|---|
| linux-aws-hwe | Debian packages (deb) · Ubuntu 16.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-azure | Debian packages (deb) · Ubuntu 16.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-gcp | Debian packages (deb) · Ubuntu 16.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-hwe | Debian packages (deb) · Ubuntu 16.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-oracle | Debian packages (deb) · Ubuntu 16.04 | sudo apt-get update && sudo apt-get upgrade |
| linux | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-aws | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-gke-4.15 | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-kvm | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-oem | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-oracle | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-raspi2 | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
| linux-snapdragon | Debian packages (deb) · Ubuntu 18.04 | sudo apt-get update && sudo apt-get upgrade |
Some commands upgrade the distribution's packages. Compare the fixed version with the version you have installed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Links
- https://ubuntu.com/security/notices/USN-4227-1
- https://ubuntu.com/security/CVE-2019-14895
- https://ubuntu.com/security/CVE-2019-14896
- https://ubuntu.com/security/CVE-2019-14897
- https://ubuntu.com/security/CVE-2019-14901
- https://ubuntu.com/security/CVE-2019-16231
- https://ubuntu.com/security/CVE-2019-16233
- https://ubuntu.com/security/CVE-2019-18660
- https://ubuntu.com/security/CVE-2019-19045
- https://ubuntu.com/security/CVE-2019-19052
- https://ubuntu.com/security/CVE-2019-19083
- https://ubuntu.com/security/CVE-2019-19524
- https://ubuntu.com/security/CVE-2019-19529
- https://ubuntu.com/security/CVE-2019-19534
- https://ubuntu.com/security/CVE-2019-19807
Source
Source: Ubuntu Security Notices · CC BY-SA 4.0