The process aborts inside libnetsnmp.so.40 (which comes shipped with the site) and appears to be triggered during cleanup rather than during communication with the SNMP device itself.
Entries in cmc.log matching the time of the core dumps show error messages like:
One lead worth checking before anything else: Red Hat rebased OpenSSL to 3.5 in RHEL 9.7 (Oracle Linux 9 follows RHEL), and the site ships its own libcrypto.so.3. See Werk #18935. Net-SNMP links against libcrypto, so a mismatch there can produce exactly this picture — memory allocated by one library, freed by the other, aborting in snmp_free_varbind() / snmp_free_pdu() with the device itself being fine.
Also: do the crashing hosts use SNMPv3? If all crashes happen on v2c, it’s probably something else.
Just guessing: As an immediate workaround you can switch the affected hosts to the Classic SNMP backend (Setup > Agents > SNMP rules > Hosts using a specific SNMP Backend) — slower, but a crash there no longer takes the fetcher down.