dbcve.org
Linux KernelOperating system · Linux

CVE-2025-37937

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-20
Fix available
A fix is available. Upgrade to 5.4.292 / 5.10.236 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: objtool, media: dib8000: Prevent divide-by-zero in dib8000_set_dds() If dib8000_set_dds()'s call to dib8000_read32() returns zero, the result is a divide-by-zero. Prevent that from happening. Fixes the following warning with an UBSAN kernel: drivers/media/dvb-frontends/dib8000.o: warning: objtool: dib8000_tune() falls through to next function dib8096p_cfg_DibRx()

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 3.10, < 5.4.292>= 5.5, < 5.10.236>= 5.11, < 5.15.180>= 5.16, < 6.1.134>= 6.2, < 6.6.87>= 6.7, < 6.12.23>= 6.13, < 6.13.11>= 6.14, < 6.14.2
Debian LinuxOperating system
Affected:= 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.292 / 5.10.236 / 5.15.180 or later
Fixed in 5.4.2925.10.2365.15.180
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to Linux kernel 5.4.292+, 5.10.236+, 5.15.180+, or 6.1.134+ (or any later stable version)

  1. 1. Identify the current kernel version using 'uname -r' or 'cat /proc/version'
  2. 2. For Debian 11 (Bullseye), check the installed kernel version and compare against the vulnerable ranges
  3. 3. If running a vulnerable kernel version, update the package lists with 'apt update'
  4. 4. Upgrade the kernel package using 'apt-get dist-upgrade' or 'apt-get install linux-image-<version>'
  5. 5. For other distributions, obtain a kernel upgrade from your vendor that includes the fix for this CVE
  6. 6. The specific commit fixing this issue is: 536f7f3595ef8187cfa9ea50d7d24fcf4e84e166
  7. 7. Verify the fix by ensuring the kernel version is >= 5.4.292, >= 5.10.236, >= 5.15.180, or >= 6.1.134 depending on your kernel branch
  8. 8. Reboot the system to load the fixed kernel
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure compatibility with system hardware and critical applications before rebooting

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-37937 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-37937 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data