CVE-2005-3274

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory (severity: LOW) published 2022-05-01. NVD baseline CVSS 4.7; sources differ by 0.0.

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

A fix is available — apply it.

Race condition in ip_vs_conn_flush in Linux 2.6 before 2.6.13 and 2.4 before 2.4.32-pre2, when running on SMP systems, allows local users to cause a denial of service (null dereference) by causing a connection timer to expire while the connection table is being flushed before the appropriate lock is acquired.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

October 21, 2005

Last Modified

April 16, 2026

Advisory Details (7)

Auto-updated May 31, 2026
No patch confirmed yet.
generic

[SECURITY] [DSA 922-1] New Linux 2.6.8 packages fix several vulnerabilities

http://www.debian.org/security/2005/dsa-922
generic

About Secunia Research | Flexera

http://secunia.com/advisories/18977
generic

About Secunia Research | Flexera

http://secunia.com/advisories/18684
generic

About Secunia Research | Flexera

http://secunia.com/advisories/18056
generic

About Secunia Research | Flexera

http://secunia.com/advisories/17826
generic

LKML: Neil Horman: Re: [Patch] ipvs: close race conditions on ip_vs_conn_tab list modification

http://lkml.org/lkml/2005/6/24/173
generic

LKML: Neil Horman: [Patch] ipvs: close race conditions on ip_vs_conn_tab list modification

http://lkml.org/lkml/2005/6/23/249

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2006-02-01redhat
redhatkernel-0:2.6.9-22.EL2005-10-05redhat
redhatkernel-0:2.4.21-37.EL2005-09-28redhat

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

(10 across 1 ecosystem)
Debian:3.1(10)
PackageVulnerable rangeFixed inDependents
kernel-image-2.6.8-alpha2.6.8-162.6.8-16sarge1—
kernel-image-2.6.8-amd642.6.8-142.6.8-16sarge1—
kernel-image-2.6.8-hppa2.6.8-62.6.8-6sarge1—
kernel-image-2.6.8-i3862.6.8-162.6.8-16sarge1—
kernel-image-2.6.8-ia642.6.8-142.6.8-14sarge1—
kernel-image-2.6.8-m68k2.6.8-42.6.8-4sarge1—
kernel-image-2.6.8-s3902.6.8-52.6.8-5sarge1—
kernel-image-2.6.8-sparc2.6.8-152.6.8-15sarge1—
kernel-patch-powerpc-2.6.82.6.8-122.6.8-12sarge1—
kernel-source-2.6.82.6.8-162.6.8-16sarge1—

Weakness Classification(1)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2005-3274?
CVE-2005-3274 is a medium vulnerability published on October 21, 2005. Race condition in ipvsconn_flush in Linux 2.6 before 2.6.13 and 2.4 before 2.4.32-pre2, when running on SMP systems, allows local users to cause a denial of service (null dereference) by causing a connection timer to expire while the connection table is being flushed before the appropriate lock is…
When was CVE-2005-3274 disclosed?
CVE-2005-3274 was first published in the National Vulnerability Database on October 21, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-3274 actively exploited?
CVE-2005-3274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.2% of all scored CVEs.
What is the CVSS score of CVE-2005-3274?
CVE-2005-3274 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2005-3274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-3274, 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-2005-3274

Explore →

Is Your Infrastructure Affected by CVE-2005-3274?

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

Start Free Scan →Browse All CVEs