Linux Kernel up to 5.3.11 drivers/spi/spi-gpio.c spi_gpio_probe resource consumption ⚔ [Disputed]

Summaryinfo

A vulnerability was found in Linux Kernel up to 5.3.11. It has been rated as problematic. Impacted is the function spi_gpio_probe of the file drivers/spi/spi-gpio.c. Performing a manipulation results in resource consumption. This vulnerability is reported as CVE-2019-19070. The attack is possible to be carried out remotely. No exploit exists. It is still unclear if this vulnerability genuinely exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.3.11 (Operating System). It has been classified as problematic. This affects the function spi_gpio_probe of the file drivers/spi/spi-gpio.c. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:

A memory leak in the spi_gpio_probe() function in drivers/spi/spi-gpio.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering devm_add_action_or_reset() failures, aka CID-d3b0ffa1d75d.

The weakness was disclosed 11/18/2019. This vulnerability is uniquely identified as CVE-2019-19070 since 11/18/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 250001 (Linux Distros Unpatched Vulnerability : CVE-2019-19070), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (250001). The entries VDB-145891, VDB-145890, VDB-145889 and VDB-145888 are pretty similar. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.3.0
• 5.3.1
• 5.3.2
• 5.3.3
• 5.3.4
• 5.3.5
• 5.3.6
• 5.3.7
• 5.3.8
• 5.3.9
• 5.3.10
• 5.3.11

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion