Comparison Overview
RFK Racing

RFK Racing
4600 Roush Place, Concord, 28027, US
Last Update: 04/05/2026
Roush Fenway Keselowski Racing is one of the most successful teams in NASCAR history, fielding multiple teams in NASCAR Cup Series. In its 34th season, RFK Racing is a leader in driver development, having launched the careers for many of the top drivers in the sport. Of...

Major League Baseball (MLB)
1271 Sixth Avenue, New York, New York, US, 10020
Last Update: 02/04/2026
Major League Baseball (MLB) is the most historic professional sports league in the United States and consists of 30 member clubs in the U.S. and Canada, representing the highest level of professional baseball. Led by Commissioner Robert D. Manfred, Jr., MLB remains com...
Compliance Ranges Comparison

RFK Racing







Major League Baseball (MLB)






Benchmark & Cyber Underwriting Signals
Incidents vs Spectator Sports Industry Avg (This Year)
RFK Racing has 37.89% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Spectator Sports Industry Avg (This Year)
No incidents recorded for Major League Baseball (MLB) in 2026.
Incident History - RFK Racing (X = Date, Y = Severity)
RFK Racing cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Major League Baseball (MLB) (X = Date, Y = Severity)
Major League Baseball (MLB) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

RFK Racing

Major League Baseball (MLB)
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.