Is secureblue linux [ secureblue.dev ] also vulnerable by these three recent linux vulnerabilities - Copy Fail, Copy Fail 2 and Dirty Frag?

I have marked it as the solution. I would however still very much appreciate, if @RoyalOughtness provides his thoughts on this topic. Like was this something that could have been prevented for secureblue in particular by pre-hardening some features or things as preventive measure, similar to how secureblue pre-hardens other things as mentioned on their website. Features | secureblue