Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/399128954
Changed status: New → Verified assignee: <none> → cl...@appspot.gserviceaccount.com verifier: <none> → cl...@appspot.gserviceaccount.com 87...@developer.gserviceaccount.com added comment #2: ClusterFuzz testcase 4848121649627136 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_binutils&range=202505050620:202505070647 If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new _______________________________ Reference Info: 399128954 binutils:fuzz_as: Direct-leak in xmalloc component: Public Trackers > 1362134 > OSS Fuzz status: Verified reporter: 87...@developer.gserviceaccount.com assignee: cl...@appspot.gserviceaccount.com verifier: cl...@appspot.gserviceaccount.com cc: am...@gmail.com, bug-binutils@gnu.org, da...@adalogics.com, and 2 more collaborators: co...@oss-fuzz.com type: Bug access level: Limited visibility priority: P2 severity: S4 hotlist: Reproducible, Stability-LibFuzzer, Stability-Memory-AddressSanitizer, Stability-Memory-LeakSanitizer retention: Component default Disclosure: May 27, 2025 Project: binutils Reported: Feb 26, 2025 Generated by Google IssueTracker notification system. You're receiving this email because you are subscribed to updates on Google IssueTracker issue 399128954 Unsubscribe from this issue.
