Boot-time kernel panic via unterminated MIDR arrays
Published May 20, 2025 · Updated May 23, 2026
Out-of-bounds access in affected Linux kernel versions causes an arm64 boot-time kernel panic when UBSAN detects the invalid read. The Spectre-BHB MIDR arrays in arch/arm64/kernel/proton-pack.c omit sentinel entries, causing is_midr_in_range_list() to read past an array when no CPU match is found. Reachability requires an affected arm64 kernel, an unmatched CPU design, and UBSAN with the function inlined; no remote trigger is documented.
Summary
What happened
Out-of-bounds access in affected Linux kernel versions causes an arm64 boot-time kernel panic when UBSAN detects the invalid read. The Spectre-BHB MIDR arrays in arch/arm64/kernel/proton-pack.c omit sentinel entries, causing is_midr_in_range_list() to read past an array when no CPU match is found. Reachability requires an affected arm64 kernel, an unmatched CPU design, and UBSAN with the function inlined; no remote trigger is documented.
The record
- CVE
- CVE-2025-37929
- Published
- May 20, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=4117975672c4743cffaf32b6fd018cfacd1b420e <3821cae9bd5a99a42d3d0be1b58e41f072cd4c4c
- Affected versionversion=46e22de65eb45a67a68ddfe9301f79b0c3821ca8 <6266b3509b2c6ebf2f9daf2239ff8eb60c5f5bd3
- Affected versionversion=4a2f3d8260a996bc43dcc1ce49ac594db54f4b3e <e68da90ac00d8b681561aeb8f5d6c47af3a04861
- Affected versionversion=5.15.181 <5.15.182
- Affected versionversion=6.1.135 <6.1.138
- Affected versionversion=6.12.24 <6.12.28
- Affected versionversion=6.13.12 <6.14
- Affected versionversion=6.14.3 <6.14.6
- Affected versionversion=6.6.88 <6.6.90
- Affected versionversion=9ca4fe357464bbdad0db67985275f2694df8dab5 <090c8714efe1c3c470301cc2f794c1ee2a57746c
- Affected versionversion=a53b3599d9bf9375f9033f2aa1fa92714fb1d0f0 <446289b8b36b2ee98dabf6388acbddcc33ed41be
- Affected versionversion=a5951389e58d2e816eed3dbec5877de9327fd881 <fee4d171451c1ad9e8aaf65fc0ab7d143a33bd72
- Affected versionversion=e060dbb7393ed7bdfba6b5ea7566f9ef87381cfb <333579202f09e260e8116321df4c55f80a19b160
- Affected versionversion=ed681e90fb244aa883b918c4d8be2614e816c6df
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