CVE-2011-2918

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The Performance Events subsystem in the Linux kernel before 3.1 does not properly handle event overflows associated with PERF_COUNT_SW_CPU_CLOCK events, which allows local users to cause a denial of service (system hang) via a crafted application.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

May 24, 2012

Last Modified

April 29, 2026

Advisory Details (4)

Auto-updated May 29, 2026
Patch available. Sources: redhat, github_commit.
github_commit

commit a8b0ca17b80e (torvalds/linux)

Fix landed in torvalds/linux commit a8b0ca17b80e — awaiting tagged release

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

730706 – (CVE-2011-2918) CVE-2011-2918 kernel: perf: Fix software event overflow

Affected: Red Hat Enterprise Linux 4 and 5 as they did not include support for perf. This has been addressed in Red Hat Enterprise Linux

https://bugzilla.redhat.com/show_bug.cgi?id=730706
generic

oss-security - Re: CVE request -- kernel: perf: fix software event overflow

http://www.openwall.com/lists/oss-security/2011/08/16/1
generic
http://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.1

Vendor Advisories for CVE-2011-2918(1)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-2.6.32-418-dove (2.6.32-418.36) @ maverick2026-05-29ubuntu
ubuntulinux-image-2.6.35-30-virtual (2.6.35-30.60~lucid1) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.35-903-omap4 (2.6.35-903.24) @ maverick2026-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.32-218-dove (2.6.32-218.36) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.32-34-lpia (2.6.32-34.77) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.38-12-generic (2.6.38-12.51~lucid1) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.32-318-ec2 (2.6.32-318.38) @ lucid2026-05-29ubuntu
ubuntulinux-image-2.6.38-1209-omap4 (2.6.38-1209.15) @ natty2026-05-29ubuntu
ubuntulinux-image-2.6.31-610-imx51 (2.6.31-610.28) @ lucid2026-05-29ubuntu
redhatkernel-rt-0:3.0.18-rt34.53.el6rt2012-02-23redhat
redhatkernel-0:2.6.32-131.17.1.el62011-10-05redhat

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.

Affected Packages

(1 across 1 ecosystem)
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
linux-2.62.6.32-30 ... 2.6.32-35~bpo50+1 (10 versions)2.6.32-35squeeze1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

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 2× in last 7d / 11× 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.

Showing the most recent 100 of 118 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-17769
    First seen Sep 1, 2011

    Linux Kernel 3.0.0 - 'perf_count_sw_cpu_clock' event Denial of Service

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2011-2918?
CVE-2011-2918 is a medium vulnerability published on May 24, 2012. The Performance Events subsystem in the Linux kernel before 3.1 does not properly handle event overflows associated with PERFCOUNTSWCPUCLOCK events, which allows local users to cause a denial of service (system hang) via a crafted application.
When was CVE-2011-2918 disclosed?
CVE-2011-2918 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-2918 actively exploited?
CVE-2011-2918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.4% of all scored CVEs.
What is the CVSS score of CVE-2011-2918?
CVE-2011-2918 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2011-2918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-2918, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2011-2918

Explore →

Is Your Infrastructure Affected by CVE-2011-2918?

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

Start Free Scan →Browse All CVEs