Find it and CL did not provide any possible suspect.
Using Code Search for the file, "canvas_capture_handler.cc" assigning to the concern onwer --

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/13c54891fd3cda8eb736c19290c5611855d10d3b

@sakal -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Since I am OOO, magjed, could you kindly take a look if this possibly could have been caused by my CL?

This issue is not caused by the CL pointed out in #1 since it does not touch anything in content::VideoCapturerSource::GetCurrentSupportedFormats. I don't really understand where the Float-cast-overflow takes place in that function though.

emircan - You touched content::VideoCapturerSource::GetCurrentSupportedFormats most recently in https://codereview.chromium.org/1737253002/. Maybe you know what the problem is?

I submitted https://codereview.chromium.org/2590823004/ as a fix. It looks like commitbot is lagging.

ClusterFuzz has detected this issue as fixed in range 440205:440242.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4783462893748224

Fuzzer: inferno_twister
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  content::VideoCapturerSource::GetCurrentSupportedFormats
  content::MediaStreamVideoSource::AddTrack
  content::MediaStreamVideoTrack::MediaStreamVideoTrack
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=440205:440242

Minimized Testcase (2.54 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97SIEaxtkfq6lyma03zxG67hGlSSM5yXD9Ys2r48m5fuPefWB-vqYcMN-1sXK_Xj58tj3TwCG4AVfq11JU34UwnpUQsA8gC95-QBK6TnP22iK9eIRunzb5vp4aMEasdBh0_T9ZQO2v2v2En5yDYGMLEQ0fe5w?testcase_id=4783462893748224

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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