Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-43914md/raid5: avoid BUG_ON() while continue reshape after reassembling

Description

In the Linux kernel, the following vulnerability has been resolved: md/raid5: avoid BUG_ON() while continue reshape after reassembling Currently, mdadm support --revert-reshape to abort the reshape while reassembling, as the test 07revert-grow. However, following BUG_ON() can be triggerred by the test: kernel BUG at drivers/md/raid5.c:6278! invalid opcode: 0000 [#1] PREEMPT SMP PTI irq event stamp: 158985 CPU: 6 PID: 891 Comm: md0_reshape Not tainted 6.9.0-03335-g7592a0b0049a #94 RIP: 0010:reshape_request+0x3f1/0xe60 Call Trace: <TASK> raid5_sync_request+0x43d/0x550 md_do_sync+0xb7a/0x2110 md_thread+0x294/0x2b0 kthread+0x147/0x1c0 ret_from_fork+0x59/0x70 ret_from_fork_asm+0x1a/0x30 </TASK> Root cause is that --revert-reshape update the raid_disks from 5 to 4, while reshape position is still set, and after reassembling the array, reshape position will be read from super block, then during reshape the checking of 'writepos' that is caculated by old reshape position will fail. Fix this panic the easy way first, by converting the BUG_ON() to WARN_ON(), and stop the reshape if checkings fail. Noted that mdadm must fix --revert-shape as well, and probably md/raid should enhance metadata validation as well, however this means reassemble will fail and there must be user tools to fix the wrong metadata.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-43914, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < 2c92f8c1c456d556f15cbf51667b385026b2e6a0
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < 6b33c468d543f6a83de2d61f09fec74b27e19fd2
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < c384dd4f1fb3b14a2fd199360701cc163ea88705
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < bf0ff69a42a3d2d46876d0514ecf13dffc516666
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < 3b33740c1750a39e046339ff9240e954f0156707
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < 775a9ba16c9ffe98fe54ebf14e55d5660f2bf600
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < 4811d6e5d9f4090c3e0ff9890eb24077108046ab
    • affected ec32a2bd35bd6b933a5db6542c48210ce069a376 – < 305a5170dc5cf3d395bb4c4e9239bca6d0b54b49
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.19.320 – ≤ 4.19.*
    • unaffected 5.4.282 – ≤ 5.4.*
    • unaffected 5.10.224 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.105 – ≤ 6.1.*
    • unaffected 6.6.46 – ≤ 6.6.*
    • unaffected 6.10.5 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-43914 badge
[![CVE-2024-43914](https://cveledger.app/badge/CVE-2024-43914.svg)](https://cveledger.app/cve/CVE-2024-43914)

Record last updated .