Comparison Overview
WDF 2025

WDF 2025
Vienna, AT
Last Update: 20/01/2026
The Wayside Digitalisation Forum (WDF) is a leading global platform dedicated to advancing digital signalling, object control, and monitoring in the railway industry. Evolving from the renowned Wheel Detection Forum, the WDF explores innovative field elements, their sea...

Amtrak
1 Massachusetts Ave NW, Washington, 20002, US
Last Update: 17/04/2026
Moving America Where it wants to go. We are not just a railroad; we are a company that moves people. With 21,000 route miles in 46 states, the District of Columbia and three Canadian provinces, Amtrak operates more than 300 trains each day – at speeds up to 150 mph – t...
Compliance Ranges Comparison

WDF 2025







Amtrak






Benchmark & Cyber Underwriting Signals
Incidents vs Rail Transportation Industry Avg (This Year)
No incidents recorded for WDF 2025 in 2026.
Incidents vs Rail Transportation Industry Avg (This Year)
Amtrak has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - WDF 2025 (X = Date, Y = Severity)
WDF 2025 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amtrak (X = Date, Y = Severity)
Amtrak cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

WDF 2025

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