Comparison Overview
BestMed | Urgent Care | Primary Care
BestMed | Urgent Care | Primary Care
91302 Coburg Industrial Way, Coburg, Oregon, 97408, US
Last Update: 18/05/2026
Founded in 2008, BestMed formerly known as Nova Health, is a leading provider of Urgent Care and Primary Care services in the Western United States. BestMed is known primarily for its nationally recognized, award-winning customer service. With a focus on patient care an...
Geisinger
100 North Academy Avenue, Danville, Pa., US, 17822
Last Update: 01/04/2026
Geisinger is among the nation’s leading providers of value-based care, serving 1.2 million people in urban and rural communities across Pennsylvania. Founded in 1915 by philanthropist Abigail Geisinger, the nonprofit system generates $10 billion in annual revenues acros...
Compliance Ranges Comparison
BestMed | Urgent Care | Primary Care
Geisinger
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for BestMed | Urgent Care | Primary Care in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Geisinger has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BestMed | Urgent Care | Primary Care (X = Date, Y = Severity)
BestMed | Urgent Care | Primary Care cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Geisinger (X = Date, Y = Severity)
Geisinger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BestMed | Urgent Care | Primary Care
Geisinger
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.