Writing VEX statements by hand doesn't scale.
NixOS can generate them for you: the system config is code, so "not affected" can be code too, re-checked on every build.
I've open-sourced my approach as nixos-vex (early, feedback welcome!)
blog.kammel.dev/post/nixos_vex/
blog.kammel.dev The unreasonable effectiveness of VEX in NixOS We explore why NixOS is uniquely positioned to implement a scalable process for vulnerability management. NixOS can generate them for you: the system config is code, so "not affected" can be code too, re-checked on every build.
I've open-sourced my approach as nixos-vex (early, feedback welcome!)
blog.kammel.dev/post/nixos_vex/