Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/xserver-xorg-video-vesa-2.5.0/src/compat-api.h
Examining data/xserver-xorg-video-vesa-2.5.0/src/vesa.c
Examining data/xserver-xorg-video-vesa-2.5.0/src/vesa.h

FINAL RESULTS:

data/xserver-xorg-video-vesa-2.5.0/src/vesa.c:455:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
    if (access("/sys/devices/platform/efi-framebuffer.0", F_OK) == 0 ||
data/xserver-xorg-video-vesa-2.5.0/src/vesa.c:456:9:  [4] (race) access:
  This usually indicates a security flaw. If an attacker can change anything
  along the path between the call to access() and the file's actual use
  (e.g., by moving files), the attacker can exploit the race condition
  (CWE-362/CWE-367!). Set up the correct permissions (e.g., using setuid())
  and try to open the file directly.
        access("/sys/devices/platform/efifb.0", F_OK) == 0) {
data/xserver-xorg-video-vesa-2.5.0/src/vesa.c:854:5:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
    memcpy(pVesa->Options, VESAOptions, sizeof(VESAOptions));
data/xserver-xorg-video-vesa-2.5.0/src/vesa.c:1722:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(pVesa->state, pVesa->pstate, pVesa->stateSize);
data/xserver-xorg-video-vesa-2.5.0/src/vesa.c:1731:3:  [2] (buffer) memcpy:
  Does not check for buffer overflows when copying to destination (CWE-120).
  Make sure destination can always hold the source data.
		memcpy(pVesa->pstate, pVesa->state, pVesa->stateSize);

ANALYSIS SUMMARY:

Hits = 5
Lines analyzed = 2119 in approximately 0.06 seconds (35018 lines/second)
Physical Source Lines of Code (SLOC) = 1547
Hits@level = [0]   0 [1]   0 [2]   3 [3]   0 [4]   2 [5]   0
Hits@level+ = [0+]   5 [1+]   5 [2+]   5 [3+]   2 [4+]   2 [5+]   0
Hits/KSLOC@level+ = [0+] 3.23206 [1+] 3.23206 [2+] 3.23206 [3+] 1.29282 [4+] 1.29282 [5+]   0
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.