CVE-2025-37803VulnerabilityPublished 8 Sep 2025Updated 11 Oct 2026

SUSE · security update for kernel

Affects SUSESource GCVE Database

Not known to be exploited : upgrade to 9.8 or 9.6 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.8, 9.6

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redhat/kernel to 9.8 or 9.6.

Affected software

Product	Affected	Fixed in
Red Hatredhat/kernel`pkg:rpm/redhat/kernel`Other threats	Affected >=9.0.0 <9.6 >=9.6.0 <9.8	Fixed in 9.6 9.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update is available from Red Hat and SUSE that addresses this vulnerability. Systems running affected kernel versions should apply the update promptly. The update requires a system reboot to take effect. Refer to the Red Hat advisory RHSA-2025:15429 and SUSE vendor advisories for detailed patching instructions. No additional mitigation steps are indicated by the vendor.

Description

A buffer size overflow vulnerability in the Linux kernel's udmabuf component has been fixed by casting the size_limit_mb to a 64-bit unsigned integer during pglimit calculation. This issue affects certain versions of the Linux kernel used in Red Hat Enterprise Linux 9 and SUSE products. The vulnerability has been assigned CVE-2025-37803 and is rated with high severity. A security update is available and should be applied, requiring a system reboot for the fix to take effect.

Impact

The vulnerability could allow an attacker to trigger a buffer size overflow during udmabuf creation, which may lead to memory corruption or other unintended behavior within the kernel. This could potentially impact system stability or security. The issue is rated as high severity by the vendor. No known exploits in the wild have been reported at this time.

Summary

CVE-2025-37803 addresses a buffer size overflow issue in the Linux kernel's udmabuf creation process. The flaw occurs due to improper handling of the size_limit_mb variable, which was not correctly cast to a 64-bit unsigned integer (u64) when calculating pglimit, potentially leading to an overflow. This vulnerability affects kernel versions prior to the patched releases in Red Hat Enterprise Linux 9 and SUSE kernel packages. The issue has been resolved by correcting the type casting during the calculation. The Red Hat advisory RHSA-2025:15429 confirms the fix and provides instructions for applying the update.

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #11
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.1 (opens in a new tab)
V14.1.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-767Access to Critical Private Variable via Public Method (opens in a new tab)
Base weakness
The product defines a public method that reads or modifies a private variable.
Implementation
Use class accessor and mutator methods appropriately. Perform validation when accepting data from a public method that is intended to modify a critical private variable. Also be sure that appropriate access controls are being applied when a public method interfaces with critical data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-366Race Condition within a Thread (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.
Architecture and Design
Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.
Architecture and Design
Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:23 UTC

WeaknessesCWE-120, CWE-767, CWE-366

Technical details

References

Community reviews

Related threats