Because of when _Py_ClearAuditHooks is called during finalization, it is possible that __del__ destructors will be called after hooks have been cleared. Audit events that would be raised here are dropped.

We should ensure these events are received by any known hooks for the interpreter (Python) or the runtime (C).

(Thanks to Frank Li for the report.)

Patch attached below works well, but with less functionality for users' audit hook.
Pure Python audit hook implement looks safe enough.
Should we need call _PySys_ClearAuditHooks earlier for more functionality?

PR 21222 (with test updates) is a good fix, though we know there can still be arbitrary code executed afterwards. But it's not in a place where we can reliably hook.

Probably the best thing to do is to make sure that events are raised for anything that would be required to add code there. Though that may not be feasible either, but since nobody should be doing that kind of thing deliberately, detection is just as valuable as prevention.

New changeset daa0fe03a517d335d48e65ace8e5da636e265a8f by Konge in branch 'master':
bpo-41162: Clear audit hooks later during finalization (GH-21222)
https://github.com/python/cpython/commit/daa0fe03a517d335d48e65ace8e5da636e265a8f

New changeset e1d4fdc53347617bea1aff0d7112471453f65003 by Steve Dower in branch '3.9':
bpo-41162: Clear audit hooks later during finalization (GH-21222)
https://github.com/python/cpython/commit/e1d4fdc53347617bea1aff0d7112471453f65003

New changeset b9e288cc1bfd583e887f784e38d9c511b43c0c3a by Steve Dower in branch '3.8':
bpo-41162: Clear audit hooks later during finalization (GH-21222)
https://github.com/python/cpython/commit/b9e288cc1bfd583e887f784e38d9c511b43c0c3a

Merged the initial fix, but we now need to find any exploitable paths that remain.

Considering how late in finalization they now run, they're very unlikely to succeed at doing anything interesting. However, they'd also qualify as bugs (potentially crashes), so we'll want to find ways to make them run earlier anyway.