CVE-2011-2699

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

The IPv6 implementation in the Linux kernel before 3.1 does not generate Fragment Identification values separately for each destination, which makes it easier for remote attackers to cause a denial of service (disrupted networking) by predicting these values and sending crafted packets.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
91.9%
KEV
Not listed

Published

May 24, 2012

Last Modified

April 29, 2026

Advisory Details (5)

Auto-updated May 29, 2026
Patch available. Sources: redhat, github_commit.
generic
http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.1
github_commit

commit 87c48fa3b463 (torvalds/linux)

Fix landed in torvalds/linux commit 87c48fa3b463 — awaiting tagged release

https://github.com/torvalds/linux/commit/87c48fa3b4630905f98268dde838ee43626a060c
redhat Patch Available

723429 – (CVE-2011-2699) CVE-2011-2699 kernel: ipv6: make fragment identifications less predictable

Affected: Red Hat Enterprise Linux 4 is now in Production 3 of the maintenance life-cycle,

https://bugzilla.redhat.com/show_bug.cgi?id=723429
generic
http://www.securitytracker.com/id?1027274
generic

oss-security - Re: CVE request: kernel: ipv6: make fragment identifications less predictable

http://www.openwall.com/lists/oss-security/2011/07/20/5

Vendor Advisories for CVE-2011-2699(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-2.6.35-903-omap4 (2.6.35-903.24) @ maverick2026-05-29ubuntu
ubuntulinux-image-2.6.32-319-ec2 (2.6.32-319.39) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.38-11-server (2.6.38-11.50) @ natty2026-05-29ubuntu
ubuntulinux-image-2.6.35-30-powerpc (2.6.35-30.60) @ maverick2026-05-29ubuntu
ubuntulinux-image-2.6.38-1209-omap4 (2.6.38-1209.15) @ natty2026-05-29ubuntu
ubuntulinux-image-2.6.32-219-dove (2.6.32-219.37) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.31-610-imx51 (2.6.31-610.28) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.38-12-generic (2.6.38-12.51~lucid1) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.32-419-dove (2.6.32-419.37) @ maverick2026-05-29ubuntu
ubuntulinux-image-2.6.24-29-lpiacompat (2.6.24-29.94) @ hardy2026-05-29ubuntu
ubuntulinux-image-2.6.35-30-virtual (2.6.35-30.60~lucid1) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.32-35-386 (2.6.32-35.78) @ lucid2026-05-29ubuntu
redhatkernel-0:2.6.18-238.35.1.el52012-03-06redhat
redhatkernel-0:2.6.32-131.21.1.el62011-11-22redhat
redhatkernel-0:2.6.18-274.7.1.el52011-10-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:23 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-07-02 14:01 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 14:03 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-28 04:52 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-27 03:05 UTCEPSS rescore
  17. 2026-06-25 13:46 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-23 21:30 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-22 14:22 UTCEPSS rescore
  24. 2026-06-21 01:56 UTCEPSS rescore
  25. 2026-06-21 01:56 UTCEPSS rescore
Show 59 more
  1. 2026-06-19 19:22 UTCEPSS rescore
  2. 2026-06-19 19:22 UTCEPSS rescore
  3. 2026-06-18 17:49 UTCEPSS rescore
  4. 2026-06-18 17:49 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-17 17:49 UTCEPSS rescore
  8. 2026-06-16 17:49 UTCEPSS rescore
  9. 2026-06-15 17:44 UTCEPSS rescore
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-14 23:14 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-12 23:08 UTCEPSS rescore
  15. 2026-06-11 13:56 UTCEPSS rescore
  16. 2026-06-10 22:14 UTCEPSS rescore
  17. 2026-06-10 13:17 UTCEPSS rescore
  18. 2026-06-08 14:14 UTCEPSS rescore
  19. 2026-06-08 14:14 UTCEPSS rescore
  20. 2026-06-07 15:22 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-06 13:45 UTCEPSS rescore
  23. 2026-06-06 13:44 UTCEPSS rescore
  24. 2026-06-05 22:44 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-05 06:07 UTCEPSS rescore
  27. 2026-06-04 13:09 UTCEPSS rescore
  28. 2026-06-04 13:09 UTCEPSS rescore
  29. 2026-06-02 20:10 UTCEPSS rescore
  30. 2026-06-02 20:10 UTCEPSS rescore
  31. 2026-06-01 13:49 UTCEPSS rescore
  32. 2026-06-01 13:49 UTCEPSS rescore
  33. 2026-05-31 22:28 UTCEPSS rescore
  34. 2026-05-31 22:28 UTCEPSS rescore
  35. 2026-05-31 00:14 UTCEPSS rescore
  36. 2026-05-31 00:14 UTCEPSS rescore
  37. 2026-05-29 13:41 UTCEPSS rescore
  38. 2026-05-29 13:40 UTCEPSS rescore
  39. 2026-05-29 04:29 UTCEG score recompute
  40. 2026-05-29 04:29 UTCVendor advisory
  41. 2026-05-29 04:29 UTCGHSA enrichment
  42. 2026-05-28 13:42 UTCEPSS rescore
  43. 2026-05-28 13:42 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-27 13:38 UTCEPSS rescore
  46. 2026-05-27 13:38 UTCEPSS rescore
  47. 2026-05-26 13:41 UTCEPSS rescore
  48. 2026-05-26 13:41 UTCEPSS rescore
  49. 2026-05-26 07:16 UTCEPSS rescore
  50. 2026-05-26 07:16 UTCEPSS rescore
  51. 2026-05-24 16:43 UTCEPSS rescore
  52. 2026-05-22 21:15 UTCEPSS rescore
  53. 2026-05-22 21:15 UTCEPSS rescore
  54. 2026-05-22 21:15 UTCEPSS rescore
  55. 2026-05-20 11:21 UTCEPSS rescore
  56. 2026-05-20 11:21 UTCEPSS rescore
  57. 2026-05-20 11:21 UTCEPSS rescore
  58. 2026-05-18 21:29 UTCEPSS rescore
  59. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2011-2699?
CVE-2011-2699 is a high vulnerability published on May 24, 2012. The IPv6 implementation in the Linux kernel before 3.1 does not generate Fragment Identification values separately for each destination, which makes it easier for remote attackers to cause a denial of service (disrupted networking) by predicting these values and sending crafted packets.
When was CVE-2011-2699 disclosed?
CVE-2011-2699 was first published in the National Vulnerability Database on May 24, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-2699 actively exploited?
CVE-2011-2699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2011-2699?
CVE-2011-2699 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2011-2699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-2699, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-2699

Explore →

Is Your Infrastructure Affected by CVE-2011-2699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs