Severity: Unknown
Affected Package: kernel
Summary: callout(9) may corrupt another CPU's data structures
Callouts may be bound to a specific CPU. When a kernel thread attempts to stop a callout while it is actively executing, it sleeps until execution completes; in the meantime the callout may be rescheduled and re-executed on a different CPU. When the sleeping thread finally completed removal of the callout, it could modify the wrong CPU's data structures, leaving them in an invalid state.
No specific recommendations provided.
Aliases:
Published: December 02, 2020
Last Modified: December 02, 2020