Comparison Overview
AVL Fuel Cell Canada Inc.

AVL Fuel Cell Canada Inc.
#125 - 8339 Eastlake Drive, Burnaby, V5A 4W2, CA
Last Update: 14/03/2026
AVL Fuel Cell Canada Inc.: AVL Fuel Cell Canada (“AVL FCC”) develops cutting-edge fuel cell and electrolyzer stack technologies for a wide range of applications, including power generation, aerospace, heavy-duty, and marine. We work with leading OEMs in these industrie...

ALTEN
221 bis boulevard Jean jaurès, Boulogne-Billancourt Cedex, Ile-de-France, FR, 92514
Last Update: 02/04/2026
𝐀 𝐰𝐨𝐫𝐥𝐝 𝐥𝐞𝐚𝐝𝐞𝐫 𝐢𝐧 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠 𝐚𝐧𝐝 𝐈𝐓 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬 ALTEN is committed to meeting the expectations of its stakeholders and anticipating their requirements in the fields of innovation, R&D, and technological information systems. Founded...
Compliance Ranges Comparison

AVL Fuel Cell Canada Inc.







ALTEN






Benchmark & Cyber Underwriting Signals
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for AVL Fuel Cell Canada Inc. in 2026.
Incidents vs Engineering Services Industry Avg (This Year)
No incidents recorded for ALTEN in 2026.
Incident History - AVL Fuel Cell Canada Inc. (X = Date, Y = Severity)
AVL Fuel Cell Canada Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ALTEN (X = Date, Y = Severity)
ALTEN cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AVL Fuel Cell Canada Inc.

ALTEN
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.