This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looks like a dupe of  Issue 725973 

Assigning to rsleevi since this looks a lot like  issue 719633 , and adding ccs from  issue 725973 . Seems like this is still happening in ClusterFuzz, so may be worth taking another look.

I'm a bit confused - 

 Issue 719633  was not a //net bug - it was a //net consumer bug.
 Issue 725973  - I don't have access to this bug, but it sounds like that as well was a //net consumer bug.
Do you have further symbols for the NSS stacktrace?

It sounds like there's nothing for //net team here, but I'm trying to understand if I've misunderstood something.

Removed access restrictions in  issue 725973  (Which was an incompatibility issue in the fuzzer infrastructure, as this presumably is, too)

ClusterFuzz has detected this issue as fixed in range 477433:477527.

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

Fuzzer: libFuzzer_net_host_resolver_impl_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  libnss3.so
  NSS_InitReadWrite
  crypto::NSSInitSingleton::NSSInitSingleton
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=476541:476588
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=477433:477527

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 4943906340077568 is verified as fixed, so closing issue.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot