Kernel panic via stale RAID1 wait pointer
Published Jul 25, 2025 · Updated May 11, 2026
Use-after-return in Linux kernel 4.18 and later before branch fixes allows local users to trigger a kernel panic through RAID1 I/O. raid1_reshape copies the stack-allocated newpool into conf->r1bio_pool without reinitializing its wait queue, leaving wait.head aimed at expired stack storage. Reachability requires a RAID1 reshape followed by the documented allocation-failure and wake path; the established consequence is a host crash.
Summary
What happened
Use-after-return in Linux kernel 4.18 and later before branch fixes allows local users to trigger a kernel panic through RAID1 I/O. raid1_reshape copies the stack-allocated newpool into conf->r1bio_pool without reinitializing its wait queue, leaving wait.head aimed at expired stack storage. Reachability requires a RAID1 reshape followed by the documented allocation-failure and wake path; the established consequence is a host crash.
The record
- CVE
- CVE-2025-38445
- Published
- Jul 25, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2025CVE 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=4.18
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <12b00ec99624f8da8c325f2dd6e807df26df0025
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <48da050b4f54ed639b66278d0ae6f4107b2c4e2d
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <5f35e48b76655e45522df338876dfef88dafcc71
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <61fd5e93006cf82ec8ee5c115ab5cf4bbd104bdb
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <776e6186dc9ecbdb8a1b706e989166c8a99bbf64
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <d67ed2ccd2d1dcfda9292c0ea8697a9d0f2f0d98
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <d8a6853d00fbaa810765c8ed2f452a5832273968
- Affected versionversion=afeee514ce7f4cab605beedd03be71ebaf0c5fc8 <df5894014a92ff0196dbc212a7764e97366fd2b7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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