Summary
Michael Hanselmann discovered that the CIFS implementation in the Linux
kernel did not sanitize paths returned by an SMB server. An attacker
controlling an SMB server could use this to overwrite arbitrary files.
(CVE-2019-10220)
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)
Nicolas Waisman discovered that the WiFi driver stack in the Linux kernel
did not properly validate SSID lengths. A physically proximate attacker
could use this to cause a denial of service (system crash).
(CVE-2019-17133)
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 the VirtualBox guest driver implementation in the
Linux kernel did not properly deallocate memory in certain error
conditions. A local attacker could use this to cause a denial of service
(memory exhaustion). (CVE-2019-19048)
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 netlink-based 802.11 configuration interface in
the Linux kernel did not deallocate memory in certain error conditions. A
local attacker could possibly use this to cause a denial of service (kernel
memory exhaustion). (CVE-2019-19055)
It was discovered that the ADIS16400 IIO IMU Driver for the Linux kernel
did not properly deallocate memory in certain error conditions. A local
attacker could use this to cause a denial of service (memory exhaustion).
(CVE-2019-19060)
It was discovered that the Intel OPA Gen1 Infiniband Driver for the Linux
kernel did not properly deallocate memory in certain error conditions. A
local attacker could use this to cause a denial of service (memory
exhaustion). (CVE-2019-19065)
It was discovered that the AMD Audio Coprocessor driver for the Linux
kernel did not properly deallocate memory in certain error conditions. A
local attacker with the ability to load modules could use this to cause a
denial of service (memory exhaustion). (CVE-2019-19067)
It was discovered that the event tracing subsystem of the Linux kernel did
not properly deallocate memory in certain error conditions. A local
attacker could use this to cause a denial of service (kernel memory
exhaustion). (CVE-2019-19072)
It was discovered that the Cascoda CA8210 SPI 802.15.4 wireless controller
driver for the Linux kernel did not properly deallocate memory in certain
error conditions. A local attacker could use this to cause a denial of
service (memory exhaustion). (CVE-2019-19075)
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 NXP PN533 NFC USB driver in the Linux kernel did
not properly free resources after a late probe error, leading to a use-
after-free vulnerability. A physically proximate attacker could use this to
cause a denial of service (system crash) or possibly execute arbitrary
code. (CVE-2019-19526)
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 multiple USB HID device drivers in the Linux kernel
did not properly validate device metadata on attachment, leading to out-of-
bounds writes. A physically proximate attacker could use this to cause a
denial of service (system crash) or possibly execute arbitrary code.
(CVE-2019-19532)
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)
It was discovered that in some situations the fair scheduler in the Linux
kernel did not permit a process to use its full quota time slice. A local
attacker could use this to cause a denial of service. (CVE-2019-19922)
It
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · 18.04 LTS 18.04:LTS | linux-aws-5.0 | 5.0.0-1023.26~18.04.1 |
| Ubuntu · 18.04 LTS 18.04:LTS | linux-azure | 5.0.0-1028.30~18.04.1 |
| Ubuntu · 18.04 LTS 18.04:LTS | linux-gke-5.0 | 5.0.0-1027.28~18.04.1 |
| Ubuntu · 18.04 LTS 18.04:LTS | linux-oem-osp1 | 5.0.0-1033.38 |
| Ubuntu · 18.04 LTS 18.04:LTS | linux-oracle-5.0 | 5.0.0-1009.14~18.04.1 |
Vulnerabilities 28
-
High 8.8CVE-2019-14901 EPSS 16%
A heap overflow flaw was found in the Linux kernel, all versions 3.x.x and 4.x.x before 4.18.0, in Marvell WiFi chip dr…
-
High 8.0CVE-2019-10220 Public exploit
Linux kernel CIFS implementation, version 4.9.0 is vulnerable to a relative paths injection in directory entry lists.
-
High 8.0
A heap-based buffer overflow was discovered in the Linux kernel, all versions 3.x.x and 4.x.x before 4.18.0, in Marvell…
-
High 7.8
A heap-based buffer overflow vulnerability was found in the Linux kernel, version kernel-2.6.32, in Marvell WiFi chip d…
-
Medium 6.6
A stack-based buffer overflow was found in the Linux kernel, version kernel-2.6.32, in Marvell WiFi chip driver. An att…
-
Unscored —
drivers/net/fjes/fjes_main.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a N…
-
Unscored —
drivers/scsi/qla2xxx/qla_os.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a …
-
Unscored —
An issue was discovered in write_tpt_entry in drivers/infiniband/hw/cxgb4/mem.c in the Linux kernel through 5.3.2. The …
-
Unscored —
In the Linux kernel through 5.3.2, cfg80211_mgd_wext_giwessid in net/wireless/wext-sme.c does not reject a long SSID IE…
-
Unscored —
The Linux kernel before 5.4.1 on powerpc allows Information Exposure because the Spectre-RSB mitigation is not in place…
-
Unscored —
A memory leak in the dwc3_pci_probe() function in drivers/usb/dwc3/dwc3-pci.c in the Linux kernel through 5.3.9 allows …
-
Unscored —
A memory leak in the mlx5_fpga_conn_create_cq() function in drivers/net/ethernet/mellanox/mlx5/core/fpga/conn.c in the …
-
Unscored —
A memory leak in the crypto_reportstat() function in drivers/virt/vboxguest/vboxguest_utils.c in the Linux kernel befor…
-
Unscored —
A memory leak in the gs_can_open() function in drivers/net/can/usb/gs_usb.c in the Linux kernel before 5.3.11 allows at…
-
Unscored —
A memory leak in the nl80211_get_ftm_responder_stats() function in net/wireless/nl80211.c in the Linux kernel through 5…
-
Unscored —
A memory leak in the adis_update_scan_mode() function in drivers/iio/imu/adis_buffer.c in the Linux kernel before 5.3.9…
-
Unscored —
A memory leak in the sdma_init() function in drivers/infiniband/hw/hfi1/sdma.c in the Linux kernel before 5.3.9 allows …
-
Unscored —
Four memory leaks in the acp_hw_init() function in drivers/gpu/drm/amd/amdgpu/amdgpu_acp.c in the Linux kernel before 5…
-
Unscored —
A memory leak in the predicate_parse() function in kernel/trace/trace_events_filter.c in the Linux kernel through 5.3.1…
-
Unscored —
A memory leak in the ca8210_probe() function in drivers/net/ieee802154/ca8210.c in the Linux kernel before 5.3.8 allows…
-
Unscored —
Memory leaks in *clock_source_create() functions under drivers/gpu/drm/amd/display/dc in the Linux kernel before 5.3.8 …
-
Unscored —
In the Linux kernel before 5.3.12, there is a use-after-free bug that can be caused by a malicious USB device in the dr…
-
Unscored —
In the Linux kernel before 5.3.9, there is a use-after-free bug that can be caused by a malicious USB device in the dri…
-
Unscored —
In the Linux kernel before 5.3.11, there is a use-after-free bug that can be caused by a malicious USB device in the dr…
-
Unscored —
In the Linux kernel before 5.3.9, there are multiple out-of-bounds write bugs that can be caused by a malicious USB dev…
-
Unscored —
In the Linux kernel before 5.3.11, there is an info-leak bug that can be caused by a malicious USB device in the driver…
-
Unscored —
kernel/sched/fair.c in the Linux kernel before 5.3.9, when cpu.cfs_quota_us is used (e.g., with Kubernetes), allows att…
-
Unscored —
In binder_transaction of binder.c, there is a possible out of bounds write due to a missing bounds check. This could le…
References
-
report
https://ubuntu.com/security/CVE-2019-2214
-
report
https://ubuntu.com/security/CVE-2019-10220
-
report
https://ubuntu.com/security/CVE-2019-14895
-
report
https://ubuntu.com/security/CVE-2019-14896
-
report
https://ubuntu.com/security/CVE-2019-14897
-
report
https://ubuntu.com/security/CVE-2019-14901
-
report
https://ubuntu.com/security/CVE-2019-16231
-
report
https://ubuntu.com/security/CVE-2019-16233
-
report
https://ubuntu.com/security/CVE-2019-17075
-
report
https://ubuntu.com/security/CVE-2019-17133
-
report
https://ubuntu.com/security/CVE-2019-18660
-
report
https://ubuntu.com/security/CVE-2019-18813
-
report
https://ubuntu.com/security/CVE-2019-19045
-
report
https://ubuntu.com/security/CVE-2019-19048
-
report
https://ubuntu.com/security/CVE-2019-19052
-
report
https://ubuntu.com/security/CVE-2019-19055
-
report
https://ubuntu.com/security/CVE-2019-19060
-
report
https://ubuntu.com/security/CVE-2019-19065
-
report
https://ubuntu.com/security/CVE-2019-19067
-
report
https://ubuntu.com/security/CVE-2019-19072
-
report
https://ubuntu.com/security/CVE-2019-19075
-
report
https://ubuntu.com/security/CVE-2019-19083
-
report
https://ubuntu.com/security/CVE-2019-19524
-
report
https://ubuntu.com/security/CVE-2019-19526
-
report
https://ubuntu.com/security/CVE-2019-19529
-
report
https://ubuntu.com/security/CVE-2019-19532
-
report
https://ubuntu.com/security/CVE-2019-19534
-
report
https://ubuntu.com/security/CVE-2019-19922