Comparison Overview
Performance Mortgage LLC

Performance Mortgage LLC
1000 E Judge Perez Dr, Chalmette, Louisiana, 70043, US
Last Update: 12/12/2025
Performance Mortgage LLC wants to be your FIRST CHOICE in delivering the American dream of homeownership. We want to inspire hope in our customers that they can fulfil their dream of being a homeowner. As your local New Orleans and Chalmette mortgage lender, ware 100% ...

LPL Financial
4707 Executive Drive, San Diego, CA, US, 92121-1968
Last Update: 02/06/2026
LPL Financial Holdings Inc. (Nasdaq: LPLA) is among the fastest growing wealth management firms in the U.S. As a leader in the financial advisor-mediated marketplace, LPL supports over 29,000 financial advisors and the wealth management practices of approximately 1,100 ...
Compliance Ranges Comparison

Performance Mortgage LLC







LPL Financial






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

Performance Mortgage LLC

LPL Financial
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.