Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 090c8714efe1c3c470301cc2f794c1ee2a57746c, 333579202f09e260e8116321df4c55f80a19b160, 3821cae9bd5a99a42d3d0be1b58e41f072cd4c4c.

Low priority for now. Upgrade to Linux Linux 090c8714efe1c3c470301cc2f794c1ee2a57746c, 333579202f09e260e8116321df4c55f80a19b160, 3821cae9bd5a99a42d3d0be1b58e41f072cd4c4c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 20, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-37929

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel6.6.88 and later · before 6.6.90
  • linux linux kernel6.12.24 and later · before 6.12.28
  • linux linux kernel6.13.12 and later · before 6.14
  • linux linux kernel6.1.135 and later · before 6.1.138
  • linux linux kernel6.14.3 and later · before 6.14.6
  • linux linux kernel5.15.181
  • linux linux kernel6.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • ed681e90fb244aa883b918c4d8be2614e816c6dfaffected
    • 4a2f3d8260a996bc43dcc1ce49ac594db54f4b3e and later · before e68da90ac00d8b681561aeb8f5d6c47af3a04861affected · git
    • 46e22de65eb45a67a68ddfe9301f79b0c3821ca8 and later · before 6266b3509b2c6ebf2f9daf2239ff8eb60c5f5bd3affected · git
    • a53b3599d9bf9375f9033f2aa1fa92714fb1d0f0 and later · before 446289b8b36b2ee98dabf6388acbddcc33ed41beaffected · git
    • 4117975672c4743cffaf32b6fd018cfacd1b420e and later · before 3821cae9bd5a99a42d3d0be1b58e41f072cd4c4caffected · git
    • 9ca4fe357464bbdad0db67985275f2694df8dab5 and later · before 090c8714efe1c3c470301cc2f794c1ee2a57746caffected · git
    • e060dbb7393ed7bdfba6b5ea7566f9ef87381cfb and later · before 333579202f09e260e8116321df4c55f80a19b160affected · git
    • a5951389e58d2e816eed3dbec5877de9327fd881 and later · before fee4d171451c1ad9e8aaf65fc0ab7d143a33bd72affected · git
    • 6.13.12 and later · before 6.14affected · semver
    • 5.15.181 and later · before 5.15.182affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.140-16.1.140-1
Debian:13linuxbefore 6.12.29-16.12.29-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-37926May 20, 2025 · ksmbd: fix use-after-free in ksmbd_session_rpc_open
    31Monitor
  • ← EarlierCVE-2025-37927May 20, 2025 · iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid
    31Monitor
  • Later →CVE-2025-37930May 20, 2025 · drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux090c8714efe1c3c470301cc2f794c1ee2a57746cVendor (CNA)
Linux Linux333579202f09e260e8116321df4c55f80a19b160Vendor (CNA)
Linux Linux3821cae9bd5a99a42d3d0be1b58e41f072cd4c4cVendor (CNA)
Linux Linux446289b8b36b2ee98dabf6388acbddcc33ed41beVendor (CNA)
Linux Linux5.15.182Vendor (CNA)
Linux Linux6.1.138Vendor (CNA)
Linux Linux6.12.28Vendor (CNA)
Linux Linux6.14Vendor (CNA)
Linux Linux6.14.6Vendor (CNA)
Linux Linux6.6.90Vendor (CNA)
Linux Linux6266b3509b2c6ebf2f9daf2239ff8eb60c5f5bd3Vendor (CNA)
Linux Linuxe68da90ac00d8b681561aeb8f5d6c47af3a04861Vendor (CNA)
Linux Linuxfee4d171451c1ad9e8aaf65fc0ab7d143a33bd72Vendor (CNA)
debian:linux6.1.140-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records