Skip to main content
VulnerabilityPublished Updated

CVE-2025-37846: Linux kernel · Out-of-bounds Read

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-37846· Low

Not known to be exploited · CVSS 7.1 Low.

Data as of 13 Nov 2026, 19:21 UTC

CVSS 3.1 base score
7.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel source code (commit 2de451a329cf662b). Users and administrators should apply the official Linux kernel updates that include this commit to remediate the issue. Since this is a kernel-level vulnerability, upgrading to a patched kernel version is the recommended mitigation. No alternative workarounds or temporary fixes are indicated.

Description

CVE-2025-37846 is a high-severity vulnerability in the Linux kernel's arm64 architecture related to the MOPS (Memory Operations) handler. The flaw involves dereferencing a source register during a SET operation, which can cause an out-of-bounds array access error under certain conditions. Specifically, when the MOPS exception is triggered from a SET* sequence with the XZR register (register 31) as the source, the kernel code incorrectly reads this register, leading to undefined behavior. This issue was benign before a certain commit due to protective code, but the vulnerability has since been addressed.

References

Community reviews

Loading reviews…