The seccomp()
mechanism is notoriously difficult to use. It also turns out to be easy to
break unintentionally, as the development community discovered when a
timekeeping change meant to address the year-2038 problem created a regression for
seccomp() users in the 5.3 kernel. Work is underway to mitigate
the problem for now, but seccomp() users on 32-bit systems are
likely to have to change their configurations at some point.

Source: LWN.net – [$] vDSO, 32-bit time, and seccomp