CVE-2025-37837

Service interruption via duplicate LVCMDQ memory cleanup

Published May 9, 2025 · Updated May 11, 2026

Improper cleanup in Linux kernel 6.12 allows local users to interrupt service during a Tegra241 SMMU probe failure. The Tegra241 command-queue driver manually frees devres-managed LVCMDQ memory inside devm_action_release, causing duplicate cleanup warnings and leaving 128 pages allocated. Reaching the fault requires CAP_SYS_ADMIN to rebind the SMMU driver and an allocation failure the user cannot directly trigger, limiting exposure to privileged local activity.

CVSS severity5.5
Medium
EPSS probability0.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper cleanup in Linux kernel 6.12 allows local users to interrupt service during a Tegra241 SMMU probe failure. The Tegra241 command-queue driver manually frees devres-managed LVCMDQ memory inside devm_action_release, causing duplicate cleanup warnings and leaving 128 pages allocated. Reaching the fault requires CAP_SYS_ADMIN to rebind the SMMU driver and an allocation failure the user cannot directly trigger, limiting exposure to privileged local activity.

The record

CVE
CVE-2025-37837
Published
May 9, 2025
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. May 9, 2025CVE publishedPublication date reported by the CVE source.
  2. May 11, 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.

  1. Affected versionversion=483e0bd8883a40fd3dd3193997a4014337698d72 <5584dbf393df509159813645a487b1ef76557722
  2. Affected versionversion=483e0bd8883a40fd3dd3193997a4014337698d72 <767e22001dfce64cc03b7def1562338591ab6031
  3. Affected versionversion=483e0bd8883a40fd3dd3193997a4014337698d72 <e38ed6908080047d8fa1763d1da86b584f9eb55b
  4. Affected versionversion=483e0bd8883a40fd3dd3193997a4014337698d72 <e5dd974d6e00704553308ef1a88659f8dcfb39d4
  5. Affected versionversion=6.12

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=483e0bd8883a40fd3dd3193997a4014337698d72 <5584dbf393df509159813645a487b1ef76557722; version=483e0bd8883a40fd3dd3193997a4014337698d72 <767e22001dfce64cc03b7def1562338591ab6031; version=483e0bd8883a40fd3dd3193997a4014337698d72 <e38ed6908080047d8fa1763d1da86b584f9eb55b; version=483e0bd8883a40fd3dd3193997a4014337698d72 <e5dd974d6e00704553308ef1a88659f8dcfb39d4; version=6.12

Published CVSS scores

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

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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