possible heap corruption reported in atcuf64.dll
I am a software developer with a broadly deployed application with built-in crash reporting. We've recently started seeing a large number of crashes in our app from users with BitDefender installed. The call stack makes it appear as though Windows is terminating the app due to heap corruption from atcuf64.dll, a binary that BitDefender injects into user-mode processes, including ours.
Of course, we don't have symbols for atcuf64.dll, so the debugger is unable to unwind the complete stack. It is unclear to us whether atcuf64.dll is merely wrapping calls to HeapFree, or whether it's actually freeing its own heap allocation here. In other words, it's unclear whether the bug is in BitDefender or in our product. Based on the number of crashes with atcuf64 on the stack, we're inclined to believe the bug is in BitDefender.
Is this a known issue in BitDefender software?
Would it be possible to get symbols for atcuf64.dll version 126.96.36.199 so we can debug further?
Is there an engineering/development contact we can be put in touch with to diagnose this issue?