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-2025-37929arm64: errata: Add missing sentinels to Spectre-BHB MIDR arrays

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.

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 12 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-2025-37929, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.20% · top 90% of all CVEs (17 Nov 2026)
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 4a2f3d8260a996bc43dcc1ce49ac594db54f4b3e – < e68da90ac00d8b681561aeb8f5d6c47af3a04861
    • affected 46e22de65eb45a67a68ddfe9301f79b0c3821ca8 – < 6266b3509b2c6ebf2f9daf2239ff8eb60c5f5bd3
    • affected a53b3599d9bf9375f9033f2aa1fa92714fb1d0f0 – < 446289b8b36b2ee98dabf6388acbddcc33ed41be
    • affected 4117975672c4743cffaf32b6fd018cfacd1b420e – < 3821cae9bd5a99a42d3d0be1b58e41f072cd4c4c
    • affected 9ca4fe357464bbdad0db67985275f2694df8dab5 – < 090c8714efe1c3c470301cc2f794c1ee2a57746c
    • affected e060dbb7393ed7bdfba6b5ea7566f9ef87381cfb – < 333579202f09e260e8116321df4c55f80a19b160
    • affected a5951389e58d2e816eed3dbec5877de9327fd881 – < fee4d171451c1ad9e8aaf65fc0ab7d143a33bd72
    • affected ed681e90fb244aa883b918c4d8be2614e816c6df
    • affected 6.13.12 – < 6.14
  • Linux · Linux

    • affected 5.15.181 – < 5.15.182
    • affected 6.1.135 – < 6.1.138
    • affected 6.6.88 – < 6.6.90
    • affected 6.12.24 – < 6.12.28
    • affected 6.14.3 – < 6.14.6

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .