I don’t think this is necessarily a Brave problem. I ran across this issue with Google Chrome on two different Windows computers at two different clients I support. One of my techs also experienced the problem a couple of weeks ago on his own Windows 10 laptop when using both Google Chrome and Brave. I suspect it’s probably really a Chromium issue.
Try the following work-around:
To the shortcut that launches Brave, add the --no-sandbox command line parameter and see if that allows Brave to start working again. You’ll probably see a message about using an unsupported command-line flag. But if you want to continue to use your Chromium-based browser until the issue gets fixed, then ignore the warning.
ref. https://www.techwalla.com/articles/how-to-disable-chrome-sandbox
HTH/YMMV
Chad