SUMMARY
Valgrind does not support seccomp and suggested I open a bug about it. Log:
--2531113-- WARNING: unhandled amd64-linux syscall: 317
--2531113-- You may be able to write your own handler.
--2531113-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2531113-- Nevertheless we consider this a bug.  Please report
--2531113-- it at http://valgrind.org/support/bug_reports.html.
--2531174-- Valgrind options:
--2531174--    --tool=memcheck
--2531174--    --xml=yes
--2531174--    --xml-file=/tmp/clion-valgrindde70abeb-c129-4cb2-924c-728d66614e74/valgrind_output_%p
--2531174--    --gen-suppressions=all
--2531174--    --leak-check=full
--2531174--    --leak-resolution=med
--2531174--    --track-origins=yes
--2531174--    -v
--2531174--    --vgdb=no
--2531174--    --trace-children=yes
--2531174-- Contents of /proc/version:
--2531174--   Linux version 6.8.0-1013-gcp (buildd@lcy02-amd64-094) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #14-Ubuntu SMP Thu Aug  8 23:18:23 UTC 2024
--2531174-- 
--2531174-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand-rdseed
--2531174-- Page sizes: currently 4096, max supported 4096
--2531174-- Valgrind library directory: /usr/libexec/valgrind


STEPS TO REPRODUCE
1.  Compile a program and use the seccomp syscall. Nothing else is needed
2.  use memcheck on the compiled binary
3.  profit?

OBSERVED RESULT
A warning will be generated and the seccomp syscall will be ignore

EXPECTED RESULT
The seccomp call should work as intended