Unable to find actual suspect through code search and also observing no suspecting CL under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Thanks!

ClusterFuzz has detected this issue as fixed in range 565922:565923.

Detailed report: https://clusterfuzz.com/testcase?key=6635914500243456

Fuzzer: inferno_twister
Job Type: linux_asan_chrome_gpu
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffd5dcb7ca0
Crash State:
  swrast_dri.so
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_gpu&range=523898:523900
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_gpu&range=565922:565923

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6635914500243456

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6635914500243456 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.