Validation Layers modify incorrect configurations resulting in a successful render

[SimonBorghese]

Environment:

• OS: Windows 10 & Arch Linux
• GPU and driver version: NVIDIA RTX 3070, 566.14 (Windows) 565.57.01 (Linux)
• SDK: 1.3.296.0 (Windows) 1.3.290 (Linux)
• Options enabled (synchronization, best practices, etc.): Handle Wrapping (Windows) (Options not narrowed down on Linux, using defaults)

Describe the Issue

Consider a Vulkan application using dynamic rendering on Vulkan 1.3.29X

The programmer sets the vkRenderInfo struct as the p_next to their pipeline creation info. Within the vkRenderInfo, colorAttachmentCount is set to zero HOWEVER the actual pointer to the color attachments formats is set to point to the format of the color attachment used in dynamic rendering. This happens the programmer forgot to set the color attachment format count.

When validation layers are completely disabled, this results in the expected behavior (i.e. undefined behavior).

HOWEVER, when validation layers are enabled, the pipeline correctly outputs to color attachments despite to no color attachment formats technically being specified,

Expected behavior

Undefined behavior, specifically on my driver, the fragment shader output is NOT written to the color attachment

A validation error SHOULD be raised in this configuration however none is but that is not the scope of this issue.