We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2024-39476

md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING



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.

Reserved 2024-06-25 | Published 2024-07-05 | Updated 2024-12-19 | Assigner Linux

Product status

Default status
unaffected

f3d55bd5b7b928ad82f8075d89c908702f3593ab before b32aa95843cac6b12c2c014d40fca18aef24a347
affected

1c00bb624cd084e2006520ad0edacaff0fb941c4 before 634ba3c97ec413cb10681c7b196db43ee461ecf4
affected

782b3e71c957991ac8ae53318bc369049d49bb53 before aa64464c8f4d2ab92f6d0b959a1e0767b829d787
affected

9e86dffd0b02594d2e7c60c6db9e889c0395414b before 098d54934814dd876963abfe751c3b1cf7fbe56a
affected

5e2cf333b7bd5d3e62595a44d598a254c697cd74 before 3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b
affected

5e2cf333b7bd5d3e62595a44d598a254c697cd74 before cd2538e5af495b3c747e503db346470fc1ffc447
affected

5e2cf333b7bd5d3e62595a44d598a254c697cd74 before e332a12f65d8fed8cf63bedb4e9317bb872b9ac7
affected

5e2cf333b7bd5d3e62595a44d598a254c697cd74 before 151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa
affected

Default status
affected

6.1
affected

Any version before 6.1
unaffected

4.19.316
unaffected

5.4.278
unaffected

5.10.219
unaffected

5.15.161
unaffected

6.1.94
unaffected

6.6.34
unaffected

6.9.5
unaffected

6.10
unaffected

References

git.kernel.org/...c/b32aa95843cac6b12c2c014d40fca18aef24a347

git.kernel.org/...c/634ba3c97ec413cb10681c7b196db43ee461ecf4

git.kernel.org/...c/aa64464c8f4d2ab92f6d0b959a1e0767b829d787

git.kernel.org/...c/098d54934814dd876963abfe751c3b1cf7fbe56a

git.kernel.org/...c/3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b

git.kernel.org/...c/cd2538e5af495b3c747e503db346470fc1ffc447

git.kernel.org/...c/e332a12f65d8fed8cf63bedb4e9317bb872b9ac7

git.kernel.org/...c/151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa

cve.org (CVE-2024-39476)

nvd.nist.gov (CVE-2024-39476)

Download JSON

Share this page
https://cve.threatint.com/CVE/CVE-2024-39476

Support options

Helpdesk Chat, Email, Knowledgebase
Subscribe to our newsletter to learn more about our work.