Comparison Overview
Siemens Financial Services

Siemens Financial Services
Otto-Hahn-Ring 6, Munich, 81739, DE
Last Update: 02/04/2026
We empower customers around the globe to unlock the next era of innovation and sustainable growth. Based on our unique combination of financing expertise, industry domain know how and our passion to innovate we provide a diverse set of financing solutions. Paving the wa...

TMF Group
Luna ArenA, Herikerbergweg 238, , Amsterdam , North Holland, NL, 1101 CM
Last Update: 01/04/2026
We provide employee, financial and legal administration so that firms can invest and operate safely around the world. TMF Group is a single global team with over 11,000 colleagues in more than 125 offices across 87 jurisdictions, covering 92% of world GDP and 95% of F...
Compliance Ranges Comparison

Siemens Financial Services







TMF Group






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Siemens Financial Services in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for TMF Group in 2026.
Incident History - Siemens Financial Services (X = Date, Y = Severity)
Siemens Financial Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TMF Group (X = Date, Y = Severity)
TMF Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Siemens Financial Services

TMF Group
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.