CVE-2014-0100: Race Condition

Published Feb 27, 2014
·
Updated

Description of the problem:

A very subtle race condition between inetfragevictor, inetfragintern and the IPv4/6 fragqueue and expire functions (basically the users of inetfragkill/inetfragput) was found.

What happens is that after a fragment has been added to the hash chain but before it's been added to the lrulist (inetfraglruadd), it may get deleted (either by an expired timer if the system load is high or the timer sufficiently low, or by the fraqqueue function for different reasons) before it's added to the lrulist, then after it gets added it's a matter of time for the evictor to get to a piece of memory which has been freed leading to a number of different bugs depending on what's left there.

Introduced by: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3ef0eb0d

Acknowledgements:

This issue was discovered by Nikolay Aleksandrov of Red Hat.

Other sources

Race condition in the inetfragintern function in net/ipv4/inetfragment.c in the Linux kernel through 3.13.6 allows remote attackers to cause a denial of service (use-after-free error) or possibly have unspecified other impact via a large series of fragmented ICMP Echo Request packets to a system with a heavy CPU load.

Launchpad

Affected Software

4 affected componentsFixes available
Linux Linux kernel>=3.9<3.10.37
Linux Linux kernel>=3.11<3.12.18
Linux Linux kernel>=3.13<3.13.10
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-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 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1

Event History

Feb 27, 2014
Data Sourced
via Red Hat·09:22 AM
DescriptionSeverityAffected Software
Mar 11, 2014
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Jan 11, 2024
Data Sourced
via Launchpad·10:03 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:03 AM
RemedyDescriptionSeverityAffected Software
Apr 24, 2025
Data Sourced
via Debian·02:08 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2014-0100?

CVE-2014-0100 is rated as high severity due to its potential impact on the system's stability and security.

2

How do I fix CVE-2014-0100?

To fix CVE-2014-0100, update to a patched version of the Linux kernel that includes the appropriate vulnerability fixes.

3

Which versions of the Linux kernel are affected by CVE-2014-0100?

CVE-2014-0100 affects Linux kernel versions between 3.9 and 3.10.37, as well as certain other versions up to 3.13.10.

4

Is CVE-2014-0100 related to network security?

Yes, CVE-2014-0100 involves a race condition affecting the IPv4/IPv6 fragment handling in the Linux kernel, directly impacting network security.

5

Are there any recommended versions to upgrade for CVE-2014-0100?

It's advisable to upgrade to kernel versions such as 5.10.223-1, 6.1.123-1, or later to mitigate CVE-2014-0100.

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