Comparison Overview
Hyatt Regency Calgary

Hyatt Regency Calgary
700 Centre Street, SE, Calgary, Alberta, T2G 5P6, CA
Last Update: 21/04/2026
Be a part of something bigger. Enjoy life everyday. Make a difference in the lives of those around you. Love where you work. Join a company that values respect, integrity, humility, empathy, creativity and yes - fun! Our Purpose We care for people so they can be their...

Delaware North
250 Delaware Ave, Buffalo, 14202, US
Last Update: 08/06/2026
Delaware North is a global leader in the hospitality and entertainment industry. The company annually serves more than a half-billion guests across three continents, including at high-profile sports venues, airports, national and state parks, restaurants, resorts, hotel...
Compliance Ranges Comparison

Hyatt Regency Calgary







Delaware North






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Hyatt Regency Calgary in 2026.
Incidents vs Hospitality Industry Avg (This Year)
Delaware North has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Hyatt Regency Calgary (X = Date, Y = Severity)
Hyatt Regency Calgary cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Delaware North (X = Date, Y = Severity)
Delaware North cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hyatt Regency Calgary

Delaware North
FAQ
Latest Global CVEs
The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.
The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.
Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).
The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.
The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory. An unprivileged local user can exploit this use-after-free to escalate privileges.