dbcve.org
Linux KernelOperating system · Linux

CVE-2025-38200

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to 5.4.295 / 5.10.239 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: i40e: fix MMIO write access to an invalid page in i40e_clear_hw When the device sends a specific input, an integer underflow can occur, leading to MMIO write access to an invalid page. Prevent the integer underflow by changing the type of related variables.

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.12, < 5.4.295>= 5.5, < 5.10.239>= 5.11, < 5.15.186>= 5.16, < 6.1.142>= 6.2, < 6.6.95>= 6.7, < 6.12.35>= 6.13, < 6.15.4
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.295 / 5.10.239 / 5.15.186 or later
Fixed in 5.4.2955.10.2395.15.186
Vendor patch git.kernel.org →
Recommended fix High confidence

Kernel 5.4.295+ / 5.10.239+ / 5.15.186+ / 6.1.142+ (depending on kernel branch in use)

  1. 1. Check the current running kernel version with `uname -r`
  2. 2. For systems running kernel 5.4.x: upgrade to kernel version 5.4.295 or later
  3. 3. For systems running kernel 5.10.x: upgrade to kernel version 5.10.239 or later
  4. 4. For systems running kernel 5.15.x: upgrade to kernel version 5.15.186 or later
  5. 5. For systems running kernel 6.1.x: upgrade to kernel version 6.1.142 or later
  6. 6. For Debian 11 (bullseye): apply vendor security updates or upgrade to a newer Debian release that includes the fixed kernel
  7. 7. After kernel upgrade, reboot the system to load the fixed kernel
  8. 8. Verify the new kernel version with `uname -r` to confirm the fix is applied
Caveat Kernel upgrade may require rebooting services; ensure compatibility with userspace tools and drivers

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-38200 — 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-38200 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