https://seclists.org/oss-sec/2026/q2/447: Copy Fail 2 / Dirty Frag — n-day from public commit, not embargo bak

Published May 8, 2026
·
Updated

Affected Software

1 affected component
Linux Foundation Linux Kernel
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-XXXX?

CVE-2026-XXXX has been assessed with a high severity level due to its potential to exploit memory fragmentation vulnerabilities.

2

How do I fix CVE-2026-XXXX?

To fix CVE-2026-XXXX, apply the latest patch provided in the Linux Kernel updates.

3

What does CVE-2026-XXXX affect?

CVE-2026-XXXX affects the Linux Kernel, particularly impacting systems utilizing specific memory management features.

4

When was CVE-2026-XXXX first published?

CVE-2026-XXXX was first published on May 8, 2026.

5

Who disclosed CVE-2026-XXXX?

CVE-2026-XXXX was disclosed by security researcher Hyunwoo Kim following a prior public discussion on ‘Dirty Frag’.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203