CVE-2021-47542

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : 5.4.164, <15fa12c119f869173f9b710cbe6a4a14071d2105, 5.16, <e2dabc4f7e7b60299c20a36d6a7b24ed9bf8e572, 0, <3.9, 7f9664525f9cb507de9198a395a111371413f230, <=4.9.*, <57af54a56024435d83e44c78449513b414eb6edf, <=5.10.*, <=4.14.*, 5.10.84, <3a061d54e260b701b538873b43e399d9b8b83e03, 4.4.294, <b4f217d6fcc00c3fdc0921a7691f30be7490b073, <=5.4.*, <=4.19.*, <550658a2d61e4eaf522c8ebc7fad76dc376bfb45, 4.14.257, <c5ef33c1489b2cd74368057fa00b5d2183bb5853, <=4.4.*, 5.15.7, <=*, <=5.15.*, 4.9.292, 4.19.220, <bbeb0325a7460ebf1e03f5e0bfc5c652fba9519f, 3.9

Description

In the Linux kernel, the following vulnerability has been resolved: net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings() In qlcnic_83xx_add_rings(), the indirect function of ahw->hw_ops->alloc_mbx_args will be called to allocate memory for cmd.req.arg, and there is a dereference of it in qlcnic_83xx_add_rings(), which could lead to a NULL pointer dereference on failure of the indirect function like qlcnic_83xx_alloc_mbx_args(). Fix this bug by adding a check of alloc_mbx_args(), this patch imitates the logic of mbx_cmd()'s failure handling. This bug was found by a static analyzer. The analysis employs differential checking to identify inconsistent security operations (e.g., checks or kfrees) between two code paths and confirms that the inconsistent operations are not recovered in the current function or the callers, so they constitute bugs. Note that, as a bug found by static analysis, it can be a false positive or hard to trigger. Multiple researchers have cross-reviewed the bug. Builds with CONFIG_QLCNIC=m show no new warnings, and our static analyzer no longer warns about this code.

Gravité et risque d'exploitation

CVE-2021-47542 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.25 %, ce qui la place devant 15.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 5.4.164, <15fa12c119f869173f9b710cbe6a4a14071d2105, 5.16, <e2dabc4f7e7b60299c20a36d6a7b24ed9bf8e572, 0, <3.9, 7f9664525f9cb507de9198a395a111371413f230, <=4.9.*, <57af54a56024435d83e44c78449513b414eb6edf, <=5.10.*, <=4.14.*, 5.10.84, <3a061d54e260b701b538873b43e399d9b8b83e03, 4.4.294, <b4f217d6fcc00c3fdc0921a7691f30be7490b073, <=5.4.*, <=4.19.*, <550658a2d61e4eaf522c8ebc7fad76dc376bfb45, 4.14.257, <c5ef33c1489b2cd74368057fa00b5d2183bb5853, <=4.4.*, 5.15.7, <=*, <=5.15.*, 4.9.292, 4.19.220, <bbeb0325a7460ebf1e03f5e0bfc5c652fba9519f, 3.9) 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