Comparison Overview
Prince William County Public Schools

Prince William County Public Schools
14715 Bristow Rd., Manassas, Virginia, US, 20112
Last Update: 09/03/2026
Prince William County Public Schools (PWCS) launches thriving futures for more than 90,000 students in 100 schools and centers in Northern Virginia, just 25 miles southwest of Washington, D.C. Students and staff benefit from innovative instructional and professional lea...

Cobb County School District
514 Glover Street, Marietta, 30060, US
Last Update: 01/04/2026
The COBB COUNTY SCHOOL DISTRICT is a public school system with administrative offices based at 514 Glover St., Marietta, GA 30060. Cobb County School District (CCSD) is the second largest school system in Georgia. CCSD is responsible for educating more than 112,000 stud...
Compliance Ranges Comparison

Prince William County Public Schools







Cobb County School District






Benchmark & Cyber Underwriting Signals
Incidents vs Primary and Secondary Education Industry Avg (This Year)
No incidents recorded for Prince William County Public Schools in 2026.
Incidents vs Primary and Secondary Education Industry Avg (This Year)
No incidents recorded for Cobb County School District in 2026.
Incident History - Prince William County Public Schools (X = Date, Y = Severity)
Prince William County Public Schools cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cobb County School District (X = Date, Y = Severity)
Cobb County School District cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Prince William County Public Schools

Cobb County School District
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.