Heimdall Security Logo

CVE-2023-52836

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

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, 2a0c11282881875dc44f166a20eedf0d866dd0ef, 4.19.300, 4.11, 0, <dcd85e3c929368076a7592b27f541e0da8b427f5, 6.1.64, 6.5.13, 5.10.202, 5.15.140, <e89d0ed45a419c485bae999426ecf92697cbdda3, 6.6.3, <d4d37c9e6a4dbcca958dabd99216550525c7e389, <=4.14.*, <=5.10.*, <e36407713163363e65566e7af0abe207d5f59a0c, <=6.6.*, <304a2c4aad0fff887ce493e4197bf9cbaf394479, <d8267cabbe1bed15ccf8b0e684c528bf8eeef715, <=5.4.*, <4.11, <=4.19.*, <=*, <=5.15.*, <=6.5.*, <c56df79d68677cf062da1b6e3b33e74299a92dfc, 5.4.262, 4.14.331, 6.7, <bccdd808902f8c677317cec47c306e42b93b849e, <9ed2d68b3925145f5f51c46559484881d6082f75

Description

In the Linux kernel, the following vulnerability has been resolved: locking/ww_mutex/test: Fix potential workqueue corruption In some cases running with the test-ww_mutex code, I was seeing odd behavior where sometimes it seemed flush_workqueue was returning before all the work threads were finished. Often this would cause strange crashes as the mutexes would be freed while they were being used. Looking at the code, there is a lifetime problem as the controlling thread that spawns the work allocates the "struct stress" structures that are passed to the workqueue threads. Then when the workqueue threads are finished, they free the stress struct that was passed to them. Unfortunately the workqueue work_struct node is in the stress struct. Which means the work_struct is freed before the work thread returns and while flush_workqueue is waiting. It seems like a better idea to have the controlling thread both allocate and free the stress structures, so that we can be sure we don't corrupt the workqueue by freeing the structure prematurely. So this patch reworks the test to do so, and with this change I no longer see the early flush_workqueue returns.

Gravité et risque d'exploitation

CVE-2023-52836 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.26 %, ce qui la place devant 16.0 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 2a0c11282881875dc44f166a20eedf0d866dd0ef, 4.19.300, 4.11, 0, <dcd85e3c929368076a7592b27f541e0da8b427f5, 6.1.64, 6.5.13, 5.10.202, 5.15.140, <e89d0ed45a419c485bae999426ecf92697cbdda3, 6.6.3, <d4d37c9e6a4dbcca958dabd99216550525c7e389, <=4.14.*, <=5.10.*, <e36407713163363e65566e7af0abe207d5f59a0c, <=6.6.*, <304a2c4aad0fff887ce493e4197bf9cbaf394479, <d8267cabbe1bed15ccf8b0e684c528bf8eeef715, <=5.4.*, <4.11, <=4.19.*, <=*, <=5.15.*, <=6.5.*, <c56df79d68677cf062da1b6e3b33e74299a92dfc, 5.4.262, 4.14.331, 6.7, <bccdd808902f8c677317cec47c306e42b93b849e, <9ed2d68b3925145f5f51c46559484881d6082f75) 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