CVE-2025-68768: inet: frags: flush pending skbs in fqdir_pre_exit()

Published Jan 13, 2026
·
Updated

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

inet: frags: flush pending skbs in fqdirpreexit()

We have been seeing occasional deadlocks on pernetopsrwsem since September in NIPA. The stuck task was usually modprobe (often loading a driver like ipvlan), trying to take the lock as a Writer. lockdep does not track readers for rwsems so the read wasn't obvious from the reports.

On closer inspection the Reader holding the lock was conntrack looping forever in nfconntrackcleanupnetlist(). Based on past experience with occasional NIPA crashes I looked thru the tests which run before the crash and noticed that the crash follows ipdefrag.sh. An immediate red flag. Scouring thru (de)fragmentation queues reveals skbs sitting around, holding conntrack references.

The problem is that since conntrack depends on nfdefragipv6, nfdefragipv6 will load first. Since nfdefragipv6 loads first its netns exit hooks run after conntrack's netns exit hook.

Flush all fragment queue SKBs during fqdirpreexit() to release conntrack references before conntrack cleanup runs. Also flush the queues in timer expiry handlers when they discover fqdir->dead is set, in case packet sneaks in while we're running the preexit flush.

The commit under Fixes is not exactly the culprit, but I think previously the timer firing would eventually unblock the spinning conntrack.

Affected Software

2 affected componentsFixes available
linux/kernel
Microsoft azl3 kernel 6.6.141.1-1<6.6.143.1-1
6.6.143.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.143.1-1

Event History

Jan 13, 2026
CVE Published
via MITRE·03:28 PM
Data Sourced
via MITRE·03:28 PM
Description
Data Sourced
via NVD·04:15 PM
Description
Jan 15, 2026
Data Sourced
via Microsoft·09:03 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·09:03 AM
Affected Software
Updated
via Microsoft·09:03 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2025-68768?

CVE-2025-68768 is categorized as a moderate severity vulnerability due to the potential for deadlocks in the Linux kernel.

2

How do I fix CVE-2025-68768?

To fix CVE-2025-68768, ensure you update your Linux kernel to the latest stable version that includes the patch addressing this vulnerability.

3

What does CVE-2025-68768 affect?

CVE-2025-68768 affects Linux kernel versions prior to the patch, specifically related to the handling of pending socket buffers.

4

What is the impact of CVE-2025-68768?

The impact of CVE-2025-68768 can lead to system deadlocks, potentially disrupting normal operations and affecting service availability.

5

When was CVE-2025-68768 discovered?

CVE-2025-68768 was discovered in September 2025 and was associated with issues related to deadlocks in the Linux kernel.

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