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

A) I don’t have Discord to join their public dev channel.

B) Yes I did search their github issue and pr with the term CVE-2026-43284 and 43284, but their was no search result. You can check out for yourself.

https://github.com/secureblue/secureblue/pulls?q=is%3Apr+43284

Issues · secureblue/secureblue · GitHub

C) I also searched “copy fail” in both pr and issues which shows,

[FEAT] Remove access to AF_ALG by default · Issue #2180 · secureblue/secureblue · GitHub ,

which is related to copy fail and not copy fail 2 and dirty frag.

D) I also searched for “dirty frag” which again shows no results.

Pull requests · secureblue/secureblue · GitHub

Issues · secureblue/secureblue · GitHub

E) I also checked their Mastodon which redirects to Bluesky and it also doesn’t mention anything. I assumed for such a popular topic they would post something, like GrapheneOS but their was nothing.

@secureblue.dev on Bluesky

F) Yes, the source doesn’t mention secureblue but that’s because secureblue is a very niche distro but since it’s based on Fedora and Fedora hasn’t released any patch, it would make sense to assume secureblue also haven’t been patched.