diff options
| author | Brian J. Tarricone <brian@tarricone.org> | 2023-09-27 23:54:51 -0700 |
|---|---|---|
| committer | Brian J. Tarricone <brian@tarricone.org> | 2023-09-27 23:54:51 -0700 |
| commit | eacb4cf6d290ba197be1ce6070cba172213e1fc4 (patch) | |
| tree | e730b3cb58b67d3397664c25864dd03d1688beaf /xcursor/wlr_xcursor.c | |
| parent | 1a731596c5bcd252d8796cacb59af8b20ceb914f (diff) | |
Fix possible crash in server-decoration when surface destroyed
If the underlying surface is destroyed, but the client has not yet
destroyed the server decoration object, and then tries to call
request_mode() on it, the compositor will crash, because the
wlr_server_decoration struct has been freed, and the wl_resource's
user_data member has been NULLed out.
Yes, this is certainly an error for the client to do that, but I
shouldn't be able to write a buggy (or malicious) Wayland app that can
take down the entire compositor.
Diffstat (limited to 'xcursor/wlr_xcursor.c')
0 files changed, 0 insertions, 0 deletions