Kernel panic via stale RAID reshape position
Published Aug 26, 2024 · Updated May 11, 2026
Reachable assertion in the Linux kernel from 2.6.30 before branch-specific fixes allows local users to trigger a panic during RAID5 reshape. The reshape_request path calculates writepos from an old reshape position retained in the superblock after raid_disks is reduced and then reaches BUG_ON when validation fails. The condition requires a reassembled RAID5 array left with inconsistent metadata by mdadm --revert-reshape, and reaching it interrupts the host.
Summary
What happened
Reachable assertion in the Linux kernel from 2.6.30 before branch-specific fixes allows local users to trigger a panic during RAID5 reshape. The reshape_request path calculates writepos from an old reshape position retained in the superblock after raid_disks is reduced and then reaches BUG_ON when validation fails. The condition requires a reassembled RAID5 array left with inconsistent metadata by mdadm --revert-reshape, and reaching it interrupts the host.
The record
- CVE
- CVE-2024-43914
- Published
- Aug 26, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.30
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <2c92f8c1c456d556f15cbf51667b385026b2e6a0
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <305a5170dc5cf3d395bb4c4e9239bca6d0b54b49
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <3b33740c1750a39e046339ff9240e954f0156707
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <4811d6e5d9f4090c3e0ff9890eb24077108046ab
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <6b33c468d543f6a83de2d61f09fec74b27e19fd2
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <775a9ba16c9ffe98fe54ebf14e55d5660f2bf600
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <bf0ff69a42a3d2d46876d0514ecf13dffc516666
- Affected versionversion=ec32a2bd35bd6b933a5db6542c48210ce069a376 <c384dd4f1fb3b14a2fd199360701cc163ea88705
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo