CVE-2026-53175: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush

Published Jun 25, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

Affected Software

20 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=6.18.3<6.18.36
Linux Linux kernel>=6.19.1<7.0.13
Linux Linux kernel=6.12.93
Linux Linux kernel=6.19
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6
Linux Linux kernel=6.19-rc7
Linux Linux kernel=6.19-rc8
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6
Linux Linux kernel=7.1-rc7
debian/linux
6.1.176-16.1.187-16.12.107-17.1.13-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.187-1Fixed in 6.12.107-1Fixed in 7.1.13-1
  2. Upgrade

    Upgrade Linux kernel inet: frags to a version that resolves this vulnerability.

    Fixed in 10 September 2026
  3. Configuration

    Ensure inet_frag_queue_flush() resets rb_fragments, fragments_tail, and last_run_head so that a flushed queue no longer points at freed skbs (fixes UAF after fqdir_pre_exit() flush on netns teardown).

    Linux kernel inet frag reassembly / fqdir_pre_exit() Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() = applied
  4. Configuration

    Drop the now-duplicate reset code in inet_frag_queue_flush() since ip_frag_reinit() already performs the required reset after its own flush.

    Linux kernel ip frag reinit() Duplicate reset logic in inet_frag_queue_flush() = remove duplicate

Event History

Jun 25, 2026
CVE Published
via MITRE·08:38 AM
Data Sourced
via MITRE·08:38 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·10:08 AM
DescriptionSeverityAffected Software
Sep 10, 2026
Data Sourced
via Launchpad·04:41 PM
Description
Sep 11, 2026
Data Sourced
via Ubuntu·04:41 PM
RemedyDescriptionSeverityAffected Software
Sep 12, 2026
Data Sourced
via Debian·04:44 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53175?

CVE-2026-53175 has a risk score of 47, indicating a moderate level of severity.

2

How do I fix CVE-2026-53175?

Fixing CVE-2026-53175 involves updating the Linux kernel to the latest patched version that addresses this use-after-free vulnerability.

3

What types of systems are affected by CVE-2026-53175?

CVE-2026-53175 affects systems running certain versions of the Linux kernel that are utilizing the inet fragment handling mechanism.

4

Can CVE-2026-53175 be exploited remotely?

Yes, CVE-2026-53175 can potentially be exploited remotely if an attacker can manipulate network traffic to trigger the vulnerability.

5

What is the primary cause of CVE-2026-53175?

The primary cause of CVE-2026-53175 is a use-after-free error related to the fqdir_pre_exit() function during network namespace teardown.

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