Heimdall Security Logo

CVE-2024-39476

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, 1c00bb624cd084e2006520ad0edacaff0fb941c4, 6.10, <151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa, 0, <aa64464c8f4d2ab92f6d0b959a1e0767b829d787, 4.19.262, 4.14.296, 5.4.220, f3d55bd5b7b928ad82f8075d89c908702f3593ab, 6.1.94, 6.9.5, <=5.10.*, <=6.6.*, <=6.9.*, 5.10.219, <b32aa95843cac6b12c2c014d40fca18aef24a347, 4.19.316, 9e86dffd0b02594d2e7c60c6db9e889c0395414b, <=5.4.*, <=4.19.*, 5.4.278, 5.15.161, <e332a12f65d8fed8cf63bedb4e9317bb872b9ac7, <5.15.161, <098d54934814dd876963abfe751c3b1cf7fbe56a, 5e2cf333b7bd5d3e62595a44d598a254c697cd74, <5.20, 782b3e71c957991ac8ae53318bc369049d49bb53, <3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b, 2cab058f2b147e0b7c01546ba00445e5701861f5, 5.19.17, 6.1, 7d808fe6af8409cf9f46ed2b10840e5788985e9b, <=*, <5.10.219, <=5.15.*, <5.4.278, 6.6.34, 6.0.3, <4.19.316, <cd2538e5af495b3c747e503db346470fc1ffc447, <4.15, <634ba3c97ec413cb10681c7b196db43ee461ecf4, 5.15.75, 91962e40ec3d26e291db230cd45b302da2aff200, <6.1, 5.10.150

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING Xiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with small possibility, the root cause is exactly the same as commit bed9e27baf52 ("Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"") However, Dan reported another hang after that, and junxiao investigated the problem and found out that this is caused by plugged bio can't issue from raid5d(). Current implementation in raid5d() has a weird dependence: 1) md_check_recovery() from raid5d() must hold 'reconfig_mutex' to clear MD_SB_CHANGE_PENDING; 2) raid5d() handles IO in a deadloop, until all IO are issued; 3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared; This behaviour is introduce before v2.6, and for consequence, if other context hold 'reconfig_mutex', and md_check_recovery() can't update super_block, then raid5d() will waste one cpu 100% by the deadloop, until 'reconfig_mutex' is released. Refer to the implementation from raid1 and raid10, fix this problem by skipping issue IO if MD_SB_CHANGE_PENDING is still set after md_check_recovery(), daemon thread will be woken up when 'reconfig_mutex' is released. Meanwhile, the hang problem will be fixed as well.

Gravité et risque d'exploitation

CVE-2024-39476 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.18 %, ce qui la place devant 6.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, 1c00bb624cd084e2006520ad0edacaff0fb941c4, 6.10, <151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa, 0, <aa64464c8f4d2ab92f6d0b959a1e0767b829d787, 4.19.262, 4.14.296, 5.4.220, f3d55bd5b7b928ad82f8075d89c908702f3593ab, 6.1.94, 6.9.5, <=5.10.*, <=6.6.*, <=6.9.*, 5.10.219, <b32aa95843cac6b12c2c014d40fca18aef24a347, 4.19.316, 9e86dffd0b02594d2e7c60c6db9e889c0395414b, <=5.4.*, <=4.19.*, 5.4.278, 5.15.161, <e332a12f65d8fed8cf63bedb4e9317bb872b9ac7, <5.15.161, <098d54934814dd876963abfe751c3b1cf7fbe56a, 5e2cf333b7bd5d3e62595a44d598a254c697cd74, <5.20, 782b3e71c957991ac8ae53318bc369049d49bb53, <3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b, 2cab058f2b147e0b7c01546ba00445e5701861f5, 5.19.17, 6.1, 7d808fe6af8409cf9f46ed2b10840e5788985e9b, <=*, <5.10.219, <=5.15.*, <5.4.278, 6.6.34, 6.0.3, <4.19.316, <cd2538e5af495b3c747e503db346470fc1ffc447, <4.15, <634ba3c97ec413cb10681c7b196db43ee461ecf4, 5.15.75, 91962e40ec3d26e291db230cd45b302da2aff200, <6.1, 5.10.150) 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