CVE-2025-37929

arm64: errata: Add missing sentinels to Spectre-BHB MIDR arrays

MEDIUM

5.5

CVSS Score

Published: May 20, 2025 at 03:21 PM UTC

Updated: June 17, 2026 at 09:15 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: errata: Add missing sentinels to Spectre-BHB MIDR arrays Commit a5951389e58d ("arm64: errata: Add newer ARM cores to the spectre_bhb_loop_affected() lists") added some additional CPUs to the Spectre-BHB workaround, including some new arrays for designs that require new 'k' values for the workaround to be effective. Unfortunately, the new arrays omitted the sentinel entry and so is_midr_in_range_list() will walk off the end when it doesn't find a match. With UBSAN enabled, this leads to a crash during boot when is_midr_in_range_list() is inlined (which was more common prior to c8c2647e69be ("arm64: Make _midr_in_range_list() an exported function")): | Internal error: aarch64 BRK: 00000000f2000001 [#1] PREEMPT SMP | pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) | pc : spectre_bhb_loop_affected+0x28/0x30 | lr : is_spectre_bhb_affected+0x170/0x190 | [...] | Call trace: | spectre_bhb_loop_affected+0x28/0x30 | update_cpu_capabilities+0xc0/0x184 | init_cpu_features+0x188/0x1a4 | cpuinfo_store_boot_cpu+0x4c/0x60 | smp_prepare_boot_cpu+0x38/0x54 | start_kernel+0x8c/0x478 | __primary_switched+0xc8/0xd4 | Code: 6b09011f 54000061 52801080 d65f03c0 (d4200020) | ---[ end trace 0000000000000000 ]--- | Kernel panic - not syncing: aarch64 BRK: Fatal exception Add the missing sentinel entries.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

11.0

Linux Kernel · Linux

95%

v ≥ 6.13.125.15.181 ≤ v < 5.15.1826.1.135 ≤ v < 6.1.1386.12.24 ≤ v < 6.12.286.13.12 ≤ v < 6.146.14.3 ≤ v < 6.14.66.6.88 ≤ v < 6.6.904117975672c4743cffaf32b6fd018cfacd1b420e46e22de65eb45a67a68ddfe9301f79b0c3821ca84a2f3d8260a996bc43dcc1ce49ac594db54f4b3e5.15.181 6.1.135 6.12.24 6.13.12 6.14.3 6.15 rc1 6.15 rc2 6.15 rc3 6.15 rc4 6.6.889ca4fe357464bbdad0db67985275f2694df8dab5a53b3599d9bf9375f9033f2aa1fa92714fb1d0f0a5951389e58d2e816eed3dbec5877de9327fd881e060dbb7393ed7bdfba6b5ea7566f9ef87381cfbed681e90fb244aa883b918c4d8be2614e816c6df

Vendor states this is fixed in 090c8714efe1c3c470301cc2f794c1ee2a57746c (fixed)

Vendor states this is fixed in 333579202f09e260e8116321df4c55f80a19b160 (fixed)

Vendor states this is fixed in 3821cae9bd5a99a42d3d0be1b58e41f072cd4c4c (fixed)

Vendor states this is fixed in 446289b8b36b2ee98dabf6388acbddcc33ed41be (fixed)

Vendor states this is fixed in 6266b3509b2c6ebf2f9daf2239ff8eb60c5f5bd3 (fixed)

Vendor states this is fixed in e68da90ac00d8b681561aeb8f5d6c47af3a04861 (fixed)

Vendor states this is fixed in fee4d171451c1ad9e8aaf65fc0ab7d143a33bd72 (fixed)

Affected range stops below 5.15.182, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.138, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.12.28, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.14, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.14.6, so it looks safe — our inference, not a vendor statement