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/dxvk-1.7.2+ds1/include/openvr/openvr.hpp Examining data/dxvk-1.7.2+ds1/include/spirv/GLSL.std.450.h Examining data/dxvk-1.7.2+ds1/include/spirv/GLSL.std.450.hpp Examining data/dxvk-1.7.2+ds1/include/spirv/spirv.hpp Examining data/dxvk-1.7.2+ds1/include/vulkan/vk_platform.h Examining data/dxvk-1.7.2+ds1/include/vulkan/vulkan.h Examining data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h Examining data/dxvk-1.7.2+ds1/include/vulkan/vulkan_win32.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_blend.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_blend.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_buffer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_buffer.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_core.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_depth_stencil.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_depth_stencil.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_device.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_device.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_include.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_input_layout.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_input_layout.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_interfaces.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_main.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_multithread.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_multithread.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_query.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_query.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_rasterizer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_rasterizer.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_reflection.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_reflection.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_sampler.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_sampler.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_shader.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_state_block.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_state_block.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_texture.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_texture.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_util.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_util.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_view_dsv.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_view_dsv.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_view_rtv.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_view_rtv.h Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_view_srv.cpp Examining data/dxvk-1.7.2+ds1/src/d3d10/d3d10_view_srv.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_annotation.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_annotation.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_blend.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_blend.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_class_linkage.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_class_linkage.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_cmd.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_cmdlist.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_cmdlist.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_def.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_def.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_ext.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_ext.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_imm.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_imm.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_state.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_depth_stencil.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_depth_stencil.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_device.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_device.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_device_child.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_enums.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_enums.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_gdi.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_gdi.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_include.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_initializer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_initializer.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_input_layout.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_input_layout.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_interfaces.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_interop.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_interop.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_main.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_options.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_options.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_query.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_query.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_rasterizer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_rasterizer.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_resource.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_resource.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_sampler.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_sampler.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_shader.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_shader.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_state.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_state.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_state_object.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_state_object.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_swapchain.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_swapchain.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_util.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_util.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_dsv.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_dsv.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_rtv.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_rtv.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_srv.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_srv.h Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_uav.cpp Examining data/dxvk-1.7.2+ds1/src/d3d11/d3d11_view_uav.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_adapter.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_adapter.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_buffer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_buffer.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_caps.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_texture.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_texture.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_constant_layout.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_constant_set.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_cursor.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_cursor.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device_child.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_fixed_function.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_fixed_function.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_format.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_format.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_format_helpers.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_format_helpers.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_hud.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_hud.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_include.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_initializer.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_initializer.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_interface.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_interface.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_main.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_monitor.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_monitor.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_multithread.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_multithread.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_names.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_names.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_options.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_options.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_query.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_query.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_resource.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_sampler.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_sampler.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader_permutations.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader_validator.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_spec_constants.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_state.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_state.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_stateblock.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_stateblock.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_subresource.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_surface.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_surface.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_swapchain.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_swapchain.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_swvp_emu.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_swvp_emu.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_texture.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_texture.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_util.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_util.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_vertex_declaration.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_vertex_declaration.h Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_volume.cpp Examining data/dxvk-1.7.2+ds1/src/d3d9/d3d9_volume.h Examining data/dxvk-1.7.2+ds1/src/d3d9/shaders/d3d9_convert_common.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_analysis.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_analysis.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_chunk_isgn.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_chunk_isgn.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_chunk_shex.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_chunk_shex.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_common.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_common.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_compiler.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_compiler.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_defs.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_defs.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_enums.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_header.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_header.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_include.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_modinfo.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_module.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_module.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_names.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_names.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_options.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_options.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_tag.h Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_util.cpp Examining data/dxvk-1.7.2+ds1/src/dxbc/dxbc_util.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_adapter.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_adapter.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_enums.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_enums.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_factory.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_factory.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_format.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_format.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_include.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_interfaces.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_main.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_monitor.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_monitor.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_object.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_options.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_options.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_output.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_output.h Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_swapchain.cpp Examining data/dxvk-1.7.2+ds1/src/dxgi/dxgi_swapchain.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_analysis.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_analysis.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_code.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_code.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_common.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_common.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_compiler.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_compiler.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_ctab.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_ctab.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_enums.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_enums.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_header.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_header.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_helpers.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_include.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_isgn.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_modinfo.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_module.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_module.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_options.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_options.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_tables.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_tables.h Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_util.cpp Examining data/dxvk-1.7.2+ds1/src/dxso/dxso_util.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_adapter.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_adapter.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_bind_mask.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_buffer.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_buffer.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_cmdlist.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_cmdlist.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_compute.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_compute.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_constant_state.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context_state.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_cs.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_cs.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_data.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_data.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_descriptor.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_descriptor.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_device.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_device.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_device_filter.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_device_filter.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_device_info.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_extension_provider.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_extensions.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_extensions.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_format.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_format.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_framebuffer.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_framebuffer.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_gpu_event.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_gpu_event.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_gpu_query.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_gpu_query.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics_state.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_hash.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_image.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_image.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_include.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_instance.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_instance.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_lifetime.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_lifetime.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_limits.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_main.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_main.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_memory.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_memory.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_blit.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_blit.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_clear.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_clear.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_copy.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_copy.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_mipgen.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_mipgen.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_pack.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_pack.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_resolve.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_resolve.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_objects.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_openvr.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_openvr.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_options.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_options.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipecache.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipecache.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipemanager.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipemanager.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_platform_exts.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_queue.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_queue.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_recycler.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_renderpass.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_renderpass.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_sampler.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_sampler.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_shader.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_shader.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_shader_key.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_shader_key.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_signal.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_signal.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_spec_const.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_spec_const.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_staging.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_staging.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache_types.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_stats.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_stats.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_unbound.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_unbound.h Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_util.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/dxvk_util.h Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud.h Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud_font.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud_font.h Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud_item.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud_item.h Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud_renderer.cpp Examining data/dxvk-1.7.2+ds1/src/dxvk/hud/dxvk_hud_renderer.h Examining data/dxvk-1.7.2+ds1/src/dxvk/platform/dxvk_win32_exts.cpp Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.h Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_compression.cpp Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_compression.h Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_include.h Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_instruction.h Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp Examining data/dxvk-1.7.2+ds1/src/spirv/spirv_module.h Examining data/dxvk-1.7.2+ds1/src/util/com/com_guid.cpp Examining data/dxvk-1.7.2+ds1/src/util/com/com_guid.h Examining data/dxvk-1.7.2+ds1/src/util/com/com_include.h Examining data/dxvk-1.7.2+ds1/src/util/com/com_object.h Examining data/dxvk-1.7.2+ds1/src/util/com/com_pointer.h Examining data/dxvk-1.7.2+ds1/src/util/com/com_private_data.cpp Examining data/dxvk-1.7.2+ds1/src/util/com/com_private_data.h Examining data/dxvk-1.7.2+ds1/src/util/config/config.cpp Examining data/dxvk-1.7.2+ds1/src/util/config/config.h Examining data/dxvk-1.7.2+ds1/src/util/log/log.cpp Examining data/dxvk-1.7.2+ds1/src/util/log/log.h Examining data/dxvk-1.7.2+ds1/src/util/log/log_debug.cpp Examining data/dxvk-1.7.2+ds1/src/util/log/log_debug.h Examining data/dxvk-1.7.2+ds1/src/util/rc/util_rc.h Examining data/dxvk-1.7.2+ds1/src/util/rc/util_rc_ptr.h Examining data/dxvk-1.7.2+ds1/src/util/sha1/sha1.c Examining data/dxvk-1.7.2+ds1/src/util/sha1/sha1.h Examining data/dxvk-1.7.2+ds1/src/util/sha1/sha1_util.cpp Examining data/dxvk-1.7.2+ds1/src/util/sha1/sha1_util.h Examining data/dxvk-1.7.2+ds1/src/util/sync/sync_recursive.cpp Examining data/dxvk-1.7.2+ds1/src/util/sync/sync_recursive.h Examining data/dxvk-1.7.2+ds1/src/util/sync/sync_signal.h Examining data/dxvk-1.7.2+ds1/src/util/sync/sync_signal_win32.h Examining data/dxvk-1.7.2+ds1/src/util/sync/sync_spinlock.h Examining data/dxvk-1.7.2+ds1/src/util/sync/sync_ticketlock.h Examining data/dxvk-1.7.2+ds1/src/util/thread.h Examining data/dxvk-1.7.2+ds1/src/util/util_bit.h Examining data/dxvk-1.7.2+ds1/src/util/util_enum.h Examining data/dxvk-1.7.2+ds1/src/util/util_env.cpp Examining data/dxvk-1.7.2+ds1/src/util/util_env.h Examining data/dxvk-1.7.2+ds1/src/util/util_error.h Examining data/dxvk-1.7.2+ds1/src/util/util_flags.h Examining data/dxvk-1.7.2+ds1/src/util/util_gdi.cpp Examining data/dxvk-1.7.2+ds1/src/util/util_gdi.h Examining data/dxvk-1.7.2+ds1/src/util/util_lazy.h Examining data/dxvk-1.7.2+ds1/src/util/util_likely.h Examining data/dxvk-1.7.2+ds1/src/util/util_luid.cpp Examining data/dxvk-1.7.2+ds1/src/util/util_luid.h Examining data/dxvk-1.7.2+ds1/src/util/util_math.h Examining data/dxvk-1.7.2+ds1/src/util/util_matrix.cpp Examining data/dxvk-1.7.2+ds1/src/util/util_matrix.h Examining data/dxvk-1.7.2+ds1/src/util/util_misc.h Examining data/dxvk-1.7.2+ds1/src/util/util_monitor.cpp Examining data/dxvk-1.7.2+ds1/src/util/util_monitor.h Examining data/dxvk-1.7.2+ds1/src/util/util_ratio.h Examining data/dxvk-1.7.2+ds1/src/util/util_small_vector.h Examining data/dxvk-1.7.2+ds1/src/util/util_string.cpp Examining data/dxvk-1.7.2+ds1/src/util/util_string.h Examining data/dxvk-1.7.2+ds1/src/util/util_time.h Examining data/dxvk-1.7.2+ds1/src/util/util_vector.h Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_loader.cpp Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_loader.h Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_names.cpp Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_names.h Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_presenter.cpp Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_presenter.h Examining data/dxvk-1.7.2+ds1/src/vulkan/vulkan_util.h Examining data/dxvk-1.7.2+ds1/tests/d3d11/test_d3d11_compute.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d11/test_d3d11_formats.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d11/test_d3d11_map_read.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d11/test_d3d11_streamout.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d11/test_d3d11_triangle.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_buffer.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_clear.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_l6v5u5.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_nv12.cpp Examining data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_nv12.yuv.h Examining data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_triangle.cpp Examining data/dxvk-1.7.2+ds1/tests/dxbc/test_dxbc_compiler.cpp Examining data/dxvk-1.7.2+ds1/tests/dxbc/test_dxbc_disasm.cpp Examining data/dxvk-1.7.2+ds1/tests/dxbc/test_hlsl_compiler.cpp Examining data/dxvk-1.7.2+ds1/tests/dxgi/test_dxgi_factory.cpp Examining data/dxvk-1.7.2+ds1/tests/test_utils.h FINAL RESULTS: data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:27:12: [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. info.access |= VK_ACCESS_VERTEX_ATTRIBUTE_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:33:12: [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. info.access |= VK_ACCESS_INDEX_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:39:12: [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. info.access |= VK_ACCESS_UNIFORM_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:49:12: [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. info.access |= VK_ACCESS_SHADER_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:55:12: [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. info.access |= VK_ACCESS_TRANSFORM_FEEDBACK_WRITE_BIT_EXT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:62:12: [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. info.access |= VK_ACCESS_SHADER_READ_BIT data/dxvk-1.7.2+ds1/src/d3d11/d3d11_buffer.cpp:69:12: [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. info.access |= VK_ACCESS_INDIRECT_COMMAND_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_imm.cpp:603:28: [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 (!Resource->isInUse(access)) data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_imm.cpp:606:27: [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 (Resource->isInUse(access)) { data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_imm.cpp:619:28: [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. Resource->waitIdle(access); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.cpp:80:17: [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. imageInfo.access |= VK_ACCESS_SHADER_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.cpp:86:17: [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. imageInfo.access |= VK_ACCESS_COLOR_ATTACHMENT_READ_BIT data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.cpp:94:17: [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. imageInfo.access |= VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_READ_BIT data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.cpp:101:17: [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. imageInfo.access |= VK_ACCESS_SHADER_READ_BIT data/dxvk-1.7.2+ds1/src/d3d11/d3d11_texture.cpp:109:17: [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. imageInfo.access |= VK_ACCESS_SHADER_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:75:12: [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. info.access |= VK_ACCESS_VERTEX_ATTRIBUTE_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:80:14: [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. info.access |= VK_ACCESS_SHADER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:86:12: [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. info.access |= VK_ACCESS_INDEX_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:91:12: [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. info.access |= VK_ACCESS_HOST_WRITE_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:94:14: [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. info.access |= VK_ACCESS_HOST_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:105:12: [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. info.access |= VK_ACCESS_TRANSFER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_buffer.cpp:126:12: [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. info.access |= VK_ACCESS_HOST_READ_BIT; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_texture.cpp:250:17: [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. imageInfo.access |= VK_ACCESS_COLOR_ATTACHMENT_READ_BIT data/dxvk-1.7.2+ds1/src/d3d9/d3d9_common_texture.cpp:258:17: [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. imageInfo.access |= VK_ACCESS_DEPTH_STENCIL_ATTACHMENT_READ_BIT data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:3845:28: [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 (!Resource->isInUse(access)) data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:3848:27: [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 (Resource->isInUse(access)) { data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:3862:28: [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. Resource->waitIdle(access); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_compiler.cpp:1065:16: [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. resource.access |= VK_ACCESS_SHADER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/dxbc/dxbc_compiler.cpp:1212:16: [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. resource.access |= VK_ACCESS_SHADER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:26:7: [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.set(DxvkAccess::Write); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:34:39: [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. m_bufSlices.push_back({ bufSlice, access }); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:52:7: [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.set(DxvkAccess::Write); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:76:56: [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. m_imgSlices.push_back({ image.ptr(), subresources, access }); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:110:21: [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. DxvkAccessFlags access(DxvkAccess::Read, DxvkAccess::Write); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:111:47: [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. release.m_bufSlices.push_back({ bufSlice, access }); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:112:47: [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. acquire.m_bufSlices.push_back({ bufSlice, access }); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:154:21: [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. DxvkAccessFlags access(DxvkAccess::Read, DxvkAccess::Write); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:155:64: [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. release.m_imgSlices.push_back({ image.ptr(), subresources, access }); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:156:64: [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. acquire.m_imgSlices.push_back({ image.ptr(), subresources, access }); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:168:84: [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. result = (bufSlice.handle == dstSlice.handle) && (bufAccess | m_bufSlices[i].access).test(DxvkAccess::Write) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:186:79: [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. result = (image == m_imgSlices[i].image) && (imgAccess | m_imgSlices[i].access).test(DxvkAccess::Write) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:199:21: [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. DxvkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:207:18: [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 = access | m_bufSlices[i].access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:207:42: [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 = access | m_bufSlices[i].access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:210:12: [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. return access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:217:21: [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. DxvkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:227:18: [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 = access | m_imgSlices[i].access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:227:42: [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 = access | m_imgSlices[i].access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.cpp:230:12: [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. return access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.h:92:31: [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. DxvkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_barrier.h:98:31: [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. DxvkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_buffer.h:32:19: [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. VkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:317:23: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:347:22: [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. buffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:421:32: [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. bufferView->bufferInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:452:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:485:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:538:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:625:25: [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. srcBuffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:631:25: [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. dstBuffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:729:24: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:735:25: [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. srcBuffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:895:24: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:901:25: [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. dstBuffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1002:24: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1009:25: [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. dstBuffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1135:25: [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. srcBuffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1150:24: [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. dstImage->info().access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1183:24: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1214:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1269:43: [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. m_state.id.argBuffer.bufferInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1423:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1688:26: [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. dstImage->info().access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1691:26: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1765:54: [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. ops.barrier.dstAccess = imageView->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1913:22: [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. buffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2000:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2069:22: [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. buffer->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2134:21: [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. image->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2540:24: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2549:24: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2607:24: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2615:24: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2683:54: [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. ops.barrier.dstAccess = imageView->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2798:30: [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. imageView->imageInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2869:24: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2878:24: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3087:26: [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. srcImage->info().access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3090:26: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3161:24: [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. dstImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3169:24: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3379:26: [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. srcImage->info().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3538:80: [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. renderPassOps.barrier.dstAccess |= renderTargets.depth.view->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:3552:85: [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. renderPassOps.barrier.dstAccess |= renderTargets.color[i].view->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4349:25: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4360:25: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4370:25: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4417:25: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4418:15: [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 |= VK_ACCESS_SHADER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4425:23: [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. stages, access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4427:45: [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. slot.bufferSlice.bufferInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4431:25: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4432:15: [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 |= VK_ACCESS_SHADER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4438:23: [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. stages, access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4440:45: [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. slot.bufferView->bufferInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4444:25: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4445:15: [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 |= VK_ACCESS_SHADER_WRITE_BIT; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4454:23: [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. stages, access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4457:43: [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. slot.imageView->imageInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4486:38: [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. && (slices[i]->bufferInfo().access & storageBufferAccess)) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4500:42: [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. && (indexBufferSlice.bufferInfo().access & storageBufferAccess)) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4516:45: [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. && (vertexBufferSlice.bufferInfo().access & storageBufferAccess)) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4549:23: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4556:46: [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. && (slot.bufferSlice.bufferInfo().access & storageBufferAccess)) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4558:39: [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. binding.stages, binding.access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4563:23: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4569:46: [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. && (slot.bufferView->bufferInfo().access & storageBufferAccess)) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4571:39: [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. binding.stages, binding.access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4576:23: [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 (binding.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4583:44: [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. && (slot.imageView->imageInfo().access & storageImageAccess)) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4585:39: [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. binding.stages, binding.access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4617:37: [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. VkAccessFlags access) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4621:17: [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. stages, access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4623:28: [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. slice.bufferInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4635:37: [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. VkAccessFlags access) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4641:17: [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. stages, access, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4644:32: [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. imageView->imageInfo().access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4660:7: [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.set(m_execBarriers.getImageAccess( data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:4665:12: [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. return access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.h:1211:39: [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. VkAccessFlags access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.h:1217:39: [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. VkAccessFlags access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_image.h:49:19: [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. VkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_copy.cpp:106:66: [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. VkAccessFlags extAccess = m_dstImageView->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_mipgen.cpp:58:29: [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. m_view->imageInfo().access, 0 }, data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_resolve.cpp:111:66: [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. VkAccessFlags extAccess = m_dstImageView->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_meta_resolve.cpp:209:59: [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. VkAccessFlags extAccess = m_dstImageView->imageInfo().access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.cpp:20:36: [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. m_descriptorSlots[bindingId].access |= desc.access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.cpp:20:51: [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. m_descriptorSlots[bindingId].access |= desc.access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.cpp:27:30: [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. slotInfo.access = desc.access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.h:19:24: [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. VkAccessFlags access; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.h:34:24: [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. VkAccessFlags access; ///< Access flags data/dxvk-1.7.2+ds1/src/dxvk/dxvk_pipelayout.h:258:18: [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 (slot.access & VK_ACCESS_SHADER_WRITE_BIT) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h:51:29: [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. void acquire(DxvkAccess access) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h:52:11: [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 != DxvkAccess::None) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h:65:29: [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. void release(DxvkAccess access) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h:66:11: [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 != DxvkAccess::None) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h:81:32: [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. sync::spin(50000, [this, access] { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_resource.h:82:25: [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. return !isInUse(access); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_openvr.cpp:205:18: [3] (misc) LoadLibrary: Ensure that the full path to the library is specified, or current directory may be used (CWE-829, CWE-20). Use registry entry or GetWindowsDirectory to find library path, if you aren't already. handle = ::LoadLibrary("openvr_api_dxvk.dll"); data/dxvk-1.7.2+ds1/include/openvr/openvr.hpp:842:2: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char cNewInput[8]; // Up to 11 bytes of new input data/dxvk-1.7.2+ds1/include/openvr/openvr.hpp:3828:3: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char rchRenderModelComponentName[128]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:2335:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char deviceName[VK_MAX_PHYSICAL_DEVICE_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:2371:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char extensionName[VK_MAX_EXTENSION_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:2376:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char layerName[VK_MAX_EXTENSION_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:2379:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char description[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:5079:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char driverName[VK_MAX_DRIVER_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:5080:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char driverInfo[VK_MAX_DRIVER_INFO_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:5227:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char driverName[VK_MAX_DRIVER_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:5228:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char driverInfo[VK_MAX_DRIVER_INFO_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:6699:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char name[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:6700:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char category[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:6701:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char description[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:7274:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char name[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:7275:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char description[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:7296:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char name[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:7297:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char description[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:7305:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char name[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:7306:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char description[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:10163:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char name[VK_MAX_EXTENSION_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:10164:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char version[VK_MAX_EXTENSION_NAME_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:10166:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char description[VK_MAX_DESCRIPTION_SIZE]; data/dxvk-1.7.2+ds1/include/vulkan/vulkan_core.h:10167:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char layer[VK_MAX_EXTENSION_NAME_SIZE]; data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context.cpp:1174:16: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(reinterpret_cast<char*>(mappedSr.pData) + offset, pSrcData, size); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context.cpp:1181:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dataSlice.ptr(), pSrcData, size); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context.cpp:2856:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(BlendFactor, m_state.om.blendFactor, sizeof(FLOAT) * 4); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context_def.cpp:302:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(slice.mapPtr, cDataSlice.ptr(), cDataSlice.length()); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_device.cpp:2274:16: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy( data/dxvk-1.7.2+ds1/src/d3d11/d3d11_device.cpp:2290:16: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy( data/dxvk-1.7.2+ds1/src/d3d11/d3d11_gdi.cpp:88:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(rowData + rowLength * i, data/dxvk-1.7.2+ds1/src/d3d11/d3d11_initializer.cpp:106:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy( data/dxvk-1.7.2+ds1/src/d3d11/d3d11_initializer.cpp:244:20: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst, src, size); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_shader.cpp:67:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(m_buffer->mapPtr(0), data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:223:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&bitmap[h * HardwareCursorPitch], &data[h * lockedBox.RowPitch], copyPitch); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:2342:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(upSlice.mapPtr, pVertexStreamZeroData, upSize); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:2395:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data, pVertexStreamZeroData, vertexSize); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:2396:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data + vertexSize, pIndexData, indicesSize); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4013:16: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(physSlice.mapPtr, oldSlice.mapPtr, oldSlice.length); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4359:18: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(physSlice.mapPtr, oldSlice.mapPtr, oldSlice.length); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4639:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst->fConsts, Src.fConsts, constSet.meta.maxConstIndexF * sizeof(Vector4)); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4641:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst->iConsts, Src.iConsts, constSet.meta.maxConstIndexI * sizeof(Vector4i)); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4652:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst + Layout.floatOffset(), Src.fConsts, constSet.meta.maxConstIndexF * sizeof(Vector4)); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4654:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst + Layout.intOffset(), Src.iConsts, constSet.meta.maxConstIndexI * sizeof(Vector4i)); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_device.cpp:4656:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst + Layout.bitmaskOffset(), Src.bConsts, Layout.bitmaskSize()); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_initializer.cpp:138:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy( data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader.cpp:20:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(m_bytecode.data(), pShaderBytecode, bytecodeLength); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader.cpp:36:7: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char comment[2048]; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_shader.h:122:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(pOut, bytecode.data(), copyAmount); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.cpp:28:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst, m_data + m_pos, n); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_tag.h:43:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char m_chars[4]; data/dxvk-1.7.2+ds1/src/dxgi/dxgi_adapter.cpp:308:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&pDesc->AdapterLuid, deviceId.deviceLUID, VK_LUID_SIZE); data/dxvk-1.7.2+ds1/src/dxgi/dxgi_output.cpp:233:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(pDesc->DeviceName, monInfo.szDevice, std::size(pDesc->DeviceName)); data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.cpp:14:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst, m_data + m_pos, n); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1585:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&m_state.pc.data[offset], data, size); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:1891:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(stagingHandle.mapPtr, data, size); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context.cpp:2052:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(stagingHandle.mapPtr, data, bufferSlice.length); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_context_state.h:114:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char data[MaxPushConstantSize]; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_cs.h:245:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char m_data[MaxBlockSize]; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics_state.h:635:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(this, &other, sizeof(*this)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics_state.h:639:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(this, &other, sizeof(*this)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics_state.h:703:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(this, &other, sizeof(*this)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_graphics_state.h:707:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(this, &other, sizeof(*this)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:66:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&m_data[m_size], &data, sizeof(T)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:87:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char m_data[MaxSize]; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:94:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&data, &m_data[m_read], sizeof(T)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache_types.h:54:5: [2] (buffer) char: Statically-sized arrays can be improperly restricted, leading to potential overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use functions that limit length, or ensure that the size is larger than the maximum possible length. char magic[4] = { 'D', 'X', 'V', 'K' }; data/dxvk-1.7.2+ds1/src/dxvk/dxvk_util.cpp:59:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dstData, srcData, bytesTotal); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_util.cpp:63:16: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy( data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:21:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(m_code.data(), data, size * sizeof(uint32_t)); data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:36:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(reinterpret_cast<char*>(m_code.data()), data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:61:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst + size, src, other.size()); data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:94:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&tmp, &value, sizeof(value)); data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:102:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&tmp, &value, sizeof(value)); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:192:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data.data(), &v, sizeof(v)); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:205:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data.data(), &v, sizeof(v)); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:218:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data.data(), &v, sizeof(v)); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:231:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data.data(), &v, sizeof(v)); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:244:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data.data(), &v, sizeof(v)); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:257:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data.data(), &v, sizeof(v)); data/dxvk-1.7.2+ds1/src/util/com/com_private_data.cpp:18:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(m_data, data, size); data/dxvk-1.7.2+ds1/src/util/com/com_private_data.cpp:88:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data, &m_iface, minSize); data/dxvk-1.7.2+ds1/src/util/com/com_private_data.cpp:90:14: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data, m_data, minSize); data/dxvk-1.7.2+ds1/src/util/sha1/sha1.c:57:8: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. (void)memcpy(block, buffer, SHA1_BLOCK_LENGTH); data/dxvk-1.7.2+ds1/src/util/sha1/sha1.c:128:9: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. (void)memcpy(&context->buffer[j], data, (i = 64-j)); data/dxvk-1.7.2+ds1/src/util/sha1/sha1.c:136:8: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. (void)memcpy(&context->buffer[j], &data[i], len - i); data/dxvk-1.7.2+ds1/src/util/util_bit.h:30:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(&dst, &src, sizeof(T)); data/dxvk-1.7.2+ds1/src/util/util_string.cpp:22:7: [2] (buffer) MultiByteToWideChar: Requires maximum length in CHARACTERS, not bytes (CWE-120). ::MultiByteToWideChar( data/dxvk-1.7.2+ds1/src/util/util_string.cpp:28:20: [2] (buffer) MultiByteToWideChar: Requires maximum length in CHARACTERS, not bytes (CWE-120). size_t len = ::MultiByteToWideChar(CP_UTF8, data/dxvk-1.7.2+ds1/src/util/util_string.cpp:38:7: [2] (buffer) MultiByteToWideChar: Requires maximum length in CHARACTERS, not bytes (CWE-120). ::MultiByteToWideChar(CP_UTF8, 0, mbs, -1, data/dxvk-1.7.2+ds1/tests/d3d11/test_d3d11_streamout.cpp:278:8: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(normalData.data(), mapInfo.pData, normalDesc.ByteWidth); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_buffer.cpp:77:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(bufferMem, data, 512); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_l6v5u5.cpp:150:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data, vertices.data(), vbSize); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_nv12.cpp:164:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data, vertices.data(), vbSize); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_nv12.cpp:204:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst, src, imageSize); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_nv12.cpp:211:12: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(dst, src, imageSize); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_triangle.cpp:273:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(sysmemLock.pBits, offscreenLock.pBits, offscreenLock.Pitch * (64 / 4)); data/dxvk-1.7.2+ds1/tests/d3d9/test_d3d9_triangle.cpp:330:10: [2] (buffer) memcpy: Does not check for buffer overflows when copying to destination (CWE-120). Make sure destination can always hold the source data. std::memcpy(data, vertices.data(), vbSize); data/dxvk-1.7.2+ds1/src/d3d11/d3d11_context.cpp:1634:12: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. if (!equal) data/dxvk-1.7.2+ds1/src/d3d11/d3d11_device.cpp:839:43: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). chunks.push_back({ semantic, std::strlen(semantic) }); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_adapter.cpp:72:10: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). std::strncpy(pIdentifier->Description, desc, countof(pIdentifier->Description)); data/dxvk-1.7.2+ds1/src/d3d9/d3d9_adapter.cpp:73:10: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). std::strncpy(pIdentifier->DeviceName, device.DeviceName, countof(pIdentifier->DeviceName)); // The GDI device name. Not the actual device name. data/dxvk-1.7.2+ds1/src/d3d9/d3d9_adapter.cpp:74:10: [1] (buffer) strncpy: Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120). std::strncpy(pIdentifier->Driver, driver, countof(pIdentifier->Driver)); // This is the driver's dll. data/dxvk-1.7.2+ds1/src/d3d9/d3d9_swvp_emu.cpp:37:7: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. equal &= std::memcmp(&a[i], &b[i], sizeof(a[0])) == 0; data/dxvk-1.7.2+ds1/src/d3d9/d3d9_swvp_emu.cpp:39:12: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. return equal; data/dxvk-1.7.2+ds1/src/dxbc/dxbc_chunk_shex.cpp:16:12: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reader.read(m_code.data(), codeLength * sizeof(uint32_t)); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:19:27: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t DxbcCodeSlice::read() { data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:102:27: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t token = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:114:20: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). token = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:224:20: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). token = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:253:32: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.imm.u32_1 = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:258:35: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.imm.u32_4[0] = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:259:35: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.imm.u32_4[1] = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:260:35: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.imm.u32_4[2] = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:261:35: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.imm.u32_4[3] = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:282:57: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.idx[i].offset = static_cast<int32_t>(code.read()); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:296:57: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). reg.idx[i].offset = static_cast<int32_t>(code.read()); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:314:33: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). const uint32_t token = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.cpp:334:20: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). imm.u32 = code.read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_decoder.h:425:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t read(); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.cpp:9:11: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). this->read(&tag, 4); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.cpp:25:20: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). void DxbcReader::read(void* dst, size_t n) { data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.h:46:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). void read(void* dst, size_t n); data/dxvk-1.7.2+ds1/src/dxbc/dxbc_reader.h:72:13: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). this->read(&result, sizeof(result)); data/dxvk-1.7.2+ds1/src/dxso/dxso_code.cpp:20:26: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t DxsoCodeIter::read() { data/dxvk-1.7.2+ds1/src/dxso/dxso_code.h:28:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:65:30: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t dclToken = iter.read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:76:34: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). m_ctx.def.uint32[i] = iter.read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:113:27: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t token = iter.read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:129:61: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). this->decodeRelativeRegister(m_ctx.dst.relative, iter.read()); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:140:27: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t token = iter.read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:154:64: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). this->decodeRelativeRegister(m_ctx.src[i].relative, iter.read()); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:163:27: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t token = iter.read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_decoder.cpp:176:27: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). uint32_t token = iter.read(); data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.cpp:9:11: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). this->read(&tag, 4); data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.cpp:13:20: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). void DxsoReader::read(void* dst, size_t n) { data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.h:33:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). void read(void* dst, size_t n); data/dxvk-1.7.2+ds1/src/dxso/dxso_reader.h:54:13: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). this->read(&result, sizeof(result)); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:43:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). bool read(T& data, uint32_t version) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:44:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). return read(data); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:47:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). bool read(DxvkBindingMask& data, uint32_t version) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:51:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!read(v8)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:58:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). return read(data); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:75:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!stream.read(m_data, size)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:90:10: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). bool read(T& data) { data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:107:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!stream.read(data, size)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:464:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!stream.read(data, size)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:526:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!stream.read(reinterpret_cast<char*>(&header), sizeof(header)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:527:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !stream.read(reinterpret_cast<char*>(&hash), sizeof(hash)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:541:14: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). data.read(keys[i], version); data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:547:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(entry.cpState.bsBindingMask, version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:555:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(sampleCount, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:556:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(imageFormat, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:557:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(imageLayout, version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:565:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(imageFormat, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:566:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(imageLayout, version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:577:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(entry.gpState.bsBindingMask, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:578:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.ia, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:579:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.il, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:580:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.rs, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:581:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.ms, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:582:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.ds, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:583:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.om, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:584:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.dsFront, version) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:585:17: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). || !data.read(entry.gpState.dsBack, version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:594:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(entry.gpState.omSwizzle[i], version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:600:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(entry.gpState.omBlend[i], version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:606:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(entry.gpState.ilAttributes[i], version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:612:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(entry.gpState.ilBindings[i], version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:624:15: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(specConstantMask, version)) data/dxvk-1.7.2+ds1/src/dxvk/dxvk_state_cache.cpp:629:19: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). if (!data.read(sc.specConstants[i], version)) data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:32:12: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). stream.read(buffer.data(), length); data/dxvk-1.7.2+ds1/src/spirv/spirv_code_buffer.cpp:144:18: [1] (buffer) strlen: Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126). return (std::strlen(str) + 4) / 4; data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:1036:35: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. uint32_t equal, data/dxvk-1.7.2+ds1/src/spirv/spirv_module.cpp:1047:20: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. m_code.putWord(equal); data/dxvk-1.7.2+ds1/src/spirv/spirv_module.h:405:37: [1] (buffer) equal: Function does not check the second iterator for over-read conditions (CWE-126). This function is often discouraged by most C++ coding standards in favor of its safer alternatives provided since C++14. Consider using a form of this function that checks the second iterator before potentially overflowing it. uint32_t equal, data/dxvk-1.7.2+ds1/tests/dxbc/test_dxbc_compiler.cpp:39:11: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). ifile.read(dxbcCode.data(), length); data/dxvk-1.7.2+ds1/tests/dxbc/test_hlsl_compiler.cpp:48:9: [1] (buffer) read: Check buffer boundaries if used in a loop including recursive loops (CWE-120, CWE-20). ifile.read(hlslCode.data(), length); ANALYSIS SUMMARY: Hits = 326 Lines analyzed = 151611 in approximately 4.34 seconds (34928 lines/second) Physical Source Lines of Code (SLOC) = 110369 Hits@level = [0] 3 [1] 80 [2] 97 [3] 1 [4] 148 [5] 0 Hits@level+ = [0+] 329 [1+] 326 [2+] 246 [3+] 149 [4+] 148 [5+] 0 Hits/KSLOC@level+ = [0+] 2.98091 [1+] 2.95373 [2+] 2.22889 [3+] 1.35002 [4+] 1.34096 [5+] 0 Dot directories skipped = 2 (--followdotdir overrides) 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.