After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768078 - window_remove_filters() removes references it does not own, leading to UaF
window_remove_filters() removes references it does not own, leading to UaF
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 637464
 
 
Reported: 2016-06-27 02:35 UTC by Karl Tomlinson
Modified: 2018-04-15 00:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Karl Tomlinson 2016-06-27 02:35:07 UTC
For https://bugzilla.gnome.org/show_bug.cgi?id=635380 removal of filter list links was tied to the lifetime of the filter, but the patch missed the removal of
the entire list of filters on window destruction in window_remove_filters(),
which was reported as https://bugzilla.gnome.org/show_bug.cgi?id=637464.

However, the replacement for window_remove_filters() added in bug 637464 keeps
calling _gdk_event_filter_unref() as long as window->filters remains, removing
references that the window does not own, including those owned by
gdk_event_apply_filters().

https://git.gnome.org/browse/gtk+/tree/gdk/gdkwindow.c?h=3.20.6#n1882

Originally reported in
https://bugzilla.mozilla.org/show_bug.cgi?id=1282281
Comment 1 Matthias Clasen 2018-02-10 05:23:37 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-15 00:30:34 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new