CVE-2019-10126 / CVE-2019-14895 / CVE-2019-17133 / CVE-2019-14901 / CVE-2019-16746: WiFi Driver Vulnerabilities
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Low
|
Jim Somerville |
Bug Description
The following CVEs are related to WiFi Drivers
CVE-2019-10126
status: fixed
cvss2Score: 7.5
Vector: (AV:N/AC:
Description: A flaw was found in the Linux kernel. A heap based buffer overflow in mwifiex_
https:/
CVE-2019-14895
status: fixed
cvss2Score: 7.5
Vector: (AV:N/AC:
Description: 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 WiFi chip driver. The flaw could occur when the station attempts a connection negotiation during the handling of the remote devices country settings. This could allow the remote device to cause a denial of service (system crash) or possibly execute arbitrary code.
https:/
CVE-2019-17133
status: fixed
cvss2Score: 7.5
Vector: (AV:N/AC:
Description: In the Linux kernel through 5.3.2, cfg80211_
https:/
CVE-2019-14901
status: fixed
cvss2Score: 10.0
Vector: (AV:N/AC:
Description: 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 driver. The vulnerability allows a remote attacker to cause a system crash, resulting in a denial of service, or execute arbitrary code. The highest threat with this vulnerability is with the availability of the system. If code execution occurs, the code will run with the permissions of root. This will affect both confidentiality and integrity of files on the system.
https:/
CVE-2019-16746
status: fixed
cvss2Score: 7.5
Vector: (AV:N/AC:
Description: An issue was discovered in net/wireless/
https:/
CVE References
Changed in starlingx: | |
assignee: | nobody → Ghada Khalil (gkhalil) |
information type: | Public → Public Security |
tags: | added: stx.security |
Changed in starlingx: | |
status: | New → Triaged |
importance: | Undecided → Low |
CVE-2019-10126:
Based on Jim Somerville's investigation, the wireless driver in question requires the config option CONFIG_MWIFIEX which is not set in stx. Therefore, we’re not vulnerable to this CVE.