Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Calls to XFixesGetCursorImage can cause the X server to access released
memory resulting in a crash. The code in the CursorDisplayCursor function
in xfixes/cursor.c stores a pointer to the cursor as follows
CursorCurrent[pDev->id] = pCursor;
The cursor pointer can get accessed by calling XFixesGetCursorImage even
if the cursor has been released. A suggested fix is to increase the cursor
reference count when storing the pointer. Any currently stored pointer
would need to be released prior to storing the reference
if (CursorCurrent[pDev->id])
FreeCursor(CursorCurrent[pDev->id], (Cursor)0);
CursorCurrent[pDev->id] = RefCursor(pCursor);
Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.17.2-10.el7.x86_64
How reproducible:
Problem was discovered running Google Chrome with VNC.
Steps to Reproduce:
1. start x0vncserver
2. start Google Chrome
3. Move the Google Chrome window using a remove viewer
Actual results:
X server crashes
Expected results:
No crash
Additional info:
FWIW, the suggested fix works for me (fedora 27, same issue : chromium-browser over x11vnc)
Comment 6Erling G. M. Kristiansen
2018-08-14 07:16:26 UTC
This fix works, and is essential for VMWare Horizon 7 on Linux (Ubuntu16.04), as it causes session shutdown for active users.(In reply to Alan Hourihane from comment #3)
> Any news when this would be fixed ?
Comment 8RHEL Program Management
2020-12-15 07:43:04 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: Calls to XFixesGetCursorImage can cause the X server to access released memory resulting in a crash. The code in the CursorDisplayCursor function in xfixes/cursor.c stores a pointer to the cursor as follows CursorCurrent[pDev->id] = pCursor; The cursor pointer can get accessed by calling XFixesGetCursorImage even if the cursor has been released. A suggested fix is to increase the cursor reference count when storing the pointer. Any currently stored pointer would need to be released prior to storing the reference if (CursorCurrent[pDev->id]) FreeCursor(CursorCurrent[pDev->id], (Cursor)0); CursorCurrent[pDev->id] = RefCursor(pCursor); Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.17.2-10.el7.x86_64 How reproducible: Problem was discovered running Google Chrome with VNC. Steps to Reproduce: 1. start x0vncserver 2. start Google Chrome 3. Move the Google Chrome window using a remove viewer Actual results: X server crashes Expected results: No crash Additional info: