FYI, a 2.4.3 SRU is in flight (by amurray), but looking at https://github.com/seccomp/libseccomp/pull/180 (the fix for the bug), https://github.com/seccomp/libseccomp/issues/187 (2.4.3 backports), and code inspection, the fix for the bug is not in 2.4.3 and will come in 2.5.
The security team is not currently working on this, but that could be changed (that should be discussed outside of this bug).
FYI, a 2.4.3 SRU is in flight (by amurray), but looking at https:/ /github. com/seccomp/ libseccomp/ pull/180 (the fix for the bug), https:/ /github. com/seccomp/ libseccomp/ issues/ 187 (2.4.3 backports), and code inspection, the fix for the bug is not in 2.4.3 and will come in 2.5.
The security team is not currently working on this, but that could be changed (that should be discussed outside of this bug).