CVE-2021-47436

Description

In the Linux kernel, the following vulnerability has been resolved: usb: musb: dsps: Fix the probe error path Commit 7c75bde329d7 ("usb: musb: musb_dsps: request_irq() after initializing musb") has inverted the calls to dsps_setup_optional_vbus_irq() and dsps_create_musb_pdev() without updating correctly the error path. dsps_create_musb_pdev() allocates and registers a new platform device which must be unregistered and freed with platform_device_unregister(), and this is missing upon dsps_setup_optional_vbus_irq() error. While on the master branch it seems not to trigger any issue, I observed a kernel crash because of a NULL pointer dereference with a v5.10.70 stable kernel where the patch mentioned above was backported. With this kernel version, -EPROBE_DEFER is returned the first time dsps_setup_optional_vbus_irq() is called which triggers the probe to error out without unregistering the platform device. Unfortunately, on the Beagle Bone Black Wireless, the platform device still living in the system is being used by the USB Ethernet gadget driver, which during the boot phase triggers the crash. My limited knowledge of the musb world prevents me to revert this commit which was sent to silence a robot warning which, as far as I understand, does not make sense. The goal of this patch was to prevent an IRQ to fire before the platform device being registered. I think this cannot ever happen due to the fact that enabling the interrupts is done by the ->enable() callback of the platform musb device, and this platform device must be already registered in order for the core or any other user to use this callback. Hence, I decided to fix the error path, which might prevent future errors on mainline kernels while also fixing older ones.

Gravité et risque d'exploitation

CVE-2021-47436 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.23 %, ce qui la place devant 12.5 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions 5.10.67, <5.4.155, 7c75bde329d7e2a93cf86a5c15c61f96f1446cdc, <5.14, <9d89e287116796bf987cc48f5c8632ef3048f8eb, <4.14.252, 5.4.148, <4.19.213, <5ed60a430fb5f3d93e7fef66264daef466b4d10c, <5.10.75, <5.14.14, <c2115b2b16421d93d4993f3fe4c520e91d6fe801, 5.14.6, 4.19.207, <ff9249aab39820be11b6975a10d94253b7d426fc, ffc825049ed2e8c849d318e987fd5073e0be462f, f5b4df24b4209cc3b9ccc768897415be18807e46, <9ab5d539bc975b8dcde86eca1b58d836b657732e, 9a4a6805294fa7d2653e82972bdaf9e3e1f3d3c9, 5269937d1483d3159d5b51907346e4f4b13ef079, 4.14.247, <e923bce31ffefe4f60edfc6b84f62d4a858f3676, 5.13.19, 72bb3eafcfdd156713a3ea0c9c95d536bd6e6e55, 8de01a896c1bc14b6b65b8d26013626597a45eda) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/5ed60a430fb5f3d93e7fef66264daef466b4d10c
• https://git.kernel.org/stable/c/e923bce31ffefe4f60edfc6b84f62d4a858f3676
• https://git.kernel.org/stable/c/9ab5d539bc975b8dcde86eca1b58d836b657732e
• https://git.kernel.org/stable/c/9d89e287116796bf987cc48f5c8632ef3048f8eb
• https://git.kernel.org/stable/c/ff9249aab39820be11b6975a10d94253b7d426fc
• https://git.kernel.org/stable/c/c2115b2b16421d93d4993f3fe4c520e91d6fe801