Heimdall Security Logo

CVE-2024-42137

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 908d1742b6e694e84ead5c62e4b7c1bfbb8b46a3, <=6.1.*, e84ec6e25df9bb0968599e92eacedaf3a0a5b587, 6.10, 0, <5.10.222, 6.1.98, 6.1.8, <977b9dc65e14fb80de4763d949c7dec2ecb15b9b, <=5.10.*, <=6.6.*, <6.1.98, <=6.9.*, 272970be3dabd24cbe50e393ffee8f04aec3b9a8, ea3ebda47dd56f6e1c62f2e0e1b6e1b0a973e447, 5.10.222, <e2d8aa4c763593704ac21e7591aed4f13e32f3b5, 6.9.9, <6.2, <e6e200b264271f62a3fadb51ada9423015ece37b, <215a26c2404fa34625c725d446967fa328a703eb, 5.10.165, <=*, <88e72239ead9814b886db54fc4ee39ef3c2b8f26, <5.15.163, <=5.15.*, 5.15.90, 5.15.163, <4ca6013cd18e58ac1044908c40d4006a92093a11, 6.6.39, 6.2

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot Commit 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed serdev") will cause below regression issue: BT can't be enabled after below steps: cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure if property enable-gpios is not configured within DT|ACPI for QCA6390. The commit is to fix a use-after-free issue within qca_serdev_shutdown() by adding condition to avoid the serdev is flushed or wrote after closed but also introduces this regression issue regarding above steps since the VSC is not sent to reset controller during warm reboot. Fixed by sending the VSC to reset controller within qca_serdev_shutdown() once BT was ever enabled, and the use-after-free issue is also fixed by this change since the serdev is still opened before it is flushed or wrote. Verified by the reported machine Dell XPS 13 9310 laptop over below two kernel commits: commit e00fc2700a3f ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of bluetooth-next tree. commit b23d98d46d28 ("Bluetooth: btusb: Fix triggering coredump implementation for QCA") of linus mainline tree.

Gravité et risque d'exploitation

CVE-2024-42137 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 13.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 908d1742b6e694e84ead5c62e4b7c1bfbb8b46a3, <=6.1.*, e84ec6e25df9bb0968599e92eacedaf3a0a5b587, 6.10, 0, <5.10.222, 6.1.98, 6.1.8, <977b9dc65e14fb80de4763d949c7dec2ecb15b9b, <=5.10.*, <=6.6.*, <6.1.98, <=6.9.*, 272970be3dabd24cbe50e393ffee8f04aec3b9a8, ea3ebda47dd56f6e1c62f2e0e1b6e1b0a973e447, 5.10.222, <e2d8aa4c763593704ac21e7591aed4f13e32f3b5, 6.9.9, <6.2, <e6e200b264271f62a3fadb51ada9423015ece37b, <215a26c2404fa34625c725d446967fa328a703eb, 5.10.165, <=*, <88e72239ead9814b886db54fc4ee39ef3c2b8f26, <5.15.163, <=5.15.*, 5.15.90, 5.15.163, <4ca6013cd18e58ac1044908c40d4006a92093a11, 6.6.39, 6.2) 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

Rechercher une autre CVE