CVE-2025-26597

March 10, 2025, 1:15 p.m.

7.8
High

Description

A buffer overflow flaw was found in X.Org and Xwayland. If XkbChangeTypesOfKey() is called with a 0 group, it will resize the key symbols table to 0 but leave the key actions unchanged. If the same function is later called with a non-zero value of groups, this will cause a buffer overflow because the key actions are of the wrong size.

Product(s) Impacted

Vendor Product Versions
Tigervnc
  • Tigervnc
  • -
X.org
  • X Server
  • Xwayland
  • -
  • -
Redhat
  • Enterprise Linux
  • 7.0, 8.0, 9.0

Weaknesses

CWE-119
Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.
CWE-122
Heap-based Buffer Overflow
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

*CPE(s)

Type Vendor Product Version Update Edition Language Software Edition Target Software Target Hardware Other Information
a tigervnc tigervnc - / / / / / / /
a x.org x_server - / / / / / / /
a x.org xwayland - / / / / / / /
o redhat enterprise_linux 7.0 / / / / / / /
o redhat enterprise_linux 8.0 / / / / / / /
o redhat enterprise_linux 9.0 / / / / / / /

CVSS Score

7.8 / 10

CVSS Data

  • Attack Vector: LOCAL
  • Attack Complexity: LOW
  • Privileges Required: LOW
  • Scope: UNCHANGED
  • Confidentiality Impact: HIGH
  • Integrity Impact: HIGH
  • Availability Impact: HIGH
  • View Vector String

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

Date

  • Published: Feb. 25, 2025, 4:15 p.m.
  • Last Modified: March 10, 2025, 1:15 p.m.

Status : Modified

CVE has been recently published to the CVE List and has been received by the NVD.

More info

Source

secalert@redhat.com

*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.