Linux Kernel mwifiex Driver mwifiex_uap_parse_tail_ies() Function Heap Overflow Vulnerability [CVE-2019-10126]

CVE Number – CVE-2019-10126

A vulnerability in the mwifiex driver component of the Linux Kernel could allow an unauthenticated, remote attacker to execute arbitrary code on a targeted system.

The vulnerability exists in the mwifiex_uap_parse_tail_ies() function, as defined in the drivers/net/wireless/marvell/mwifiex/ie.c source code file of the affected software, and is due to improper memory operations by the Linux Kernel. The vulnerability manifests as a heap overflow memory error condition. An attacker could exploit this vulnerability by sending requests that submit malicious input to the targeted system. A successful exploit could allow the attacker to cause a heap overflow that could be used to execute arbitrary code. 

Kernel.org has confirmed the vulnerability and released software updates.

Analysis

• To exploit this vulnerability, the attacker must send malicious requests to the targeted system, making exploitation more difficult in environments that restrict network access from untrusted sources.

Safeguards

• Administrators are advised to apply the appropriate updates.
  
  Administrators are advised to allow only trusted users to have network access.
  
  Administrators are advised to run both firewall and antivirus applications to minimize the potential of inbound and outbound threats.
  
  Administrators may consider using IP-based access control lists (ACLs) to allow only trusted systems to access the affected systems.
  
  Administrators can help protect affected systems from external attacks by using a solid firewall strategy.
  
  Administrators are advised to monitor affected systems.

Vendor Announcements

• Kernel.org has confirmed the vulnerability in a mailing list post at the following link: Re: [PATCH] mwifiex: Fix heap overflow in mwifiex_uap_parse_tail_ies()

Fixed Software

• Kernel.org has committed a source code patch to the linux-next kernel at the following link; however, at the time this alert was first published, the update had not yet been backported to the stable kernel or included in a stable release: linux-next: Tree for Jun 18