dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-49180

HIGH · 7.8 CVSS v3.1 Published 2025-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
A flaw was found in the RandR extension, where the RRChangeProviderProperty function does not properly validate input. This issue leads to an integer overflow when computing the total size to allocate.

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 · moderate confidence

A vulnerability exists in the X Window System's RandR extension where the RRChangeProviderProperty function fails to properly validate input parameters. This flaw enables an integer overflow when calculating memory allocation size, potentially resulting in an undersized buffer allocation that could lead to heap-based buffer overflows or memory corruption when data is written.

MitigationApply the vendor-supplied patch for CVE-2025-49180 to the X.org X server or update to a patched version of the X Window System distribution packages. Until a patch is available, consider restricting RandR protocol access through X server configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify X server version
    Run 'Xorg -version' or 'xdpyinfo | grep XFree86' to determine the installed X.org server version
    Affected if The installed version is older than the patched version for CVE-2025-49180 (version information should be compared against vendor security advisories)
  2. Check RandR extension availability
    Run 'xdpyinfo | grep -i RANDR' or check /var/log/Xorg.0.log for 'RRChangeProviderProperty' references to confirm the RandR extension is loaded
    Affected if RandR extension is present and the X server version is unpatched for this CVE
  3. Verify RandR protocol access configuration
    Examine /etc/X11/xorg.conf or /etc/X11/xorg.conf.d/ for any 'DisableRandR' or access control settings, and check if clients can access the RandR extension via 'xrandr --verbose'
    Affected if RandR extension is accessible to untrusted clients and the X server lacks the CVE-2025-49180 patch
  4. Confirm vulnerable code path presence
    Search X server logs or extension modules for 'RRChangeProviderProperty' function usage by examining the RandR module files in /usr/lib/xorg/modules/extensions/
    Affected if The RandR extension module is loaded and the function handles user-supplied property data without the patch applied

A user is affected if they are running an unpatched X.org X server with the RandR extension enabled and accessible, where the RRChangeProviderProperty function can process potentially malicious input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch for CVE-2025-49180 to the X.org X server or update to a patched version of the X Window System distribution packages. Until a patch is available, consider restricting RandR protocol access through X server configuration.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49180 — 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-49180 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