[service] [request]: Roadmap for AMI patches addressing Dirty Frag (Copy.Fail V2)

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

According to [this](https://juliet.sh/blog/we-tested-dirty-frag-in-kubernetes-eks-gke-talos-seccomp) investigation latest EKS nodes are vulnerable to dirty-frag aka copy-fail v2.

[AWS related security bulletin](https://aws.amazon.com/security/security-bulletins/rss/2026-027-aws/)

Is the fix under your radar?

Thanks

cc @younsl

Review the linked Dirty Frag investigation and AWS security bulletin first, then determine whether EKS nodes are affected and what AMI patching work is needed. Done means documenting the maintainer’s status and a roadmap for addressing vulnerable EKS node AMIs.

Written by the indexing model from the issue text.