Bug 2265269 (CVE-2023-52437)
Summary: | CVE-2023-52437 kernel: Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Avinash Hanwate <ahanwate> |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, pbonzini, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: |
A flaw was found in the Linux kernel's md/raid5 driver, specifically introduced by commit 5e2cf333b7bd. This commit triggers a race condition wherein the system hangs due to improper handling of MD_SB_CHANGE_PENDING flags. During the execution of md_write_start, if MD_SB_CHANGE_PENDING is set and concurrently cleared by raid5d, it can lead to a deadlock situation. This results in system unresponsiveness, potentially causing a denial of service (DoS).
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-02-25 10:51:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2265270 | ||
Bug Blocks: | 2265182 |
Description
Avinash Hanwate
2024-02-21 08:33:28 UTC
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2265270] This CVE is bogus. The revert was later reverted again on the stable branch because it themselves caused hangs. I'm preparing the popcorn. If it was an attempt at a fix, this means the CVE is not bogus, ie, it should not be disputed. Instead this is an incomplete fix, and another CVE needs to be generated. > If it was an attempt at a fix, this means the CVE is not bogus, ie, it should not be disputed. According to https://lore.kernel.org/all/626f3f93-7085-7bd4-2172-3f97fcf197c9@huaweicloud.com/T/, this commit is just an "attempt to undo a suboptimal fix" that, as it turned out, had to be reverted. The actual fix is in commit d6e035aad6c0 ("md: bypass block throttle for superblock update"). So there is a bug that is fixed by commit d6e035aad6c0. I am not sure if it should be considered an instance of this CVE, or a CVE at all. The fix is queued for 6.7.6, but yes, the revert landed in 6.6.13, and the revert was reverted in 6.6.14. I will mark 6.7.6 as fixing this for Fedora when it lands. |