Comparison Overview
flydubai

flydubai
PO Box 353, Dubai, AE
Last Update: 14/03/2026
From its home in Dubai, flydubai has created a network of more than 135 destinations served by a fleet of 95 aircraft. Since commencing operations in June 2009, flydubai has been committed to removing barriers to travel, creating free flows of trade and tourism and enha...

IndiGo (InterGlobe Aviation Ltd)
Level 1, Tower C, Global Business Park,, Gurgaon, 122 002, IN
Last Update: 12/06/2026
IndiGo is India’s largest passenger airline. We operate with focus on our three pillars – offering low fares, being on-time and delivering a courteous and hassle-free experience. IndiGo has become synonymous with being on-time. Since our inception in August 2006, we ha...
Compliance Ranges Comparison

flydubai







IndiGo (InterGlobe Aviation Ltd)






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for flydubai in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for IndiGo (InterGlobe Aviation Ltd) in 2026.
Incident History - flydubai (X = Date, Y = Severity)
flydubai cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IndiGo (InterGlobe Aviation Ltd) (X = Date, Y = Severity)
IndiGo (InterGlobe Aviation Ltd) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

flydubai

IndiGo (InterGlobe Aviation Ltd)
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.