CVE-2005-3275

LOWCVSS v2 · 2.62.6—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 2.6 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:H/Au:N/C:N/I:N/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 3.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
2.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS v2: 2.6Exploit: None knownExposed: 0

A fix is available — apply it.

The NAT code (1) ip_nat_proto_tcp.c and (2) ip_nat_proto_udp.c in Linux kernel 2.6 before 2.6.13 and 2.4 before 2.4.32-rc1 incorrectly declares a variable to be static, which allows remote attackers to cause a denial of service (memory corruption) by causing two packets for the same protocol to be NATed at the same time, which leads to memory corruption.

CVSS v2.0 (legacy)
2.6LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
2.6(low)
EG Risk
18(Track)
EG Risk 18/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
Severity26% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
88%
KEV
Not listed

Published

October 21, 2005

Last Modified

April 16, 2026

References (54)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2006-02-01redhat
redhatpatch2006-02-01redhat
redhatkernel-0:2.4.21-37.0.1.EL2006-01-19redhat
redhatkernel-0:2.6.9-22.EL2005-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

(21 across 1 ecosystem)
Debian:3.1(21)
PackageVulnerable rangeFixed inDependents
kernel-image-2.4.27-alpha2.4.27-102.4.27-10sarge1—
kernel-image-2.4.27-arm2.4.27-22.4.27-2sarge1—
kernel-image-2.4.27-i3862.4.27-102.4.27-10sarge1—
kernel-image-2.4.27-ia642.4.27-102.4.27-10sarge1—
kernel-image-2.4.27-m68k2.4.27-32.4.27-3sarge1—
kernel-image-2.4.27-s3902.4.27-22.4.27-2sarge1—
kernel-image-2.4.27-sparc2.4.27-92.4.27-9sarge1—
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-2.4.27-arm2.4.27-12.4.27-1sarge1—
kernel-patch-2.4.27-mips2.4.27-10.040815-12.4.27-10.sarge1.040815-1—
kernel-patch-powerpc-2.4.272.4.27-102.4.27-10sarge1—
kernel-patch-powerpc-2.6.82.6.8-122.6.8-12sarge1—
kernel-source-2.4.272.4.27-102.4.27-10sarge1—
kernel-source-2.6.82.6.8-162.6.8-16sarge1—

All Vendor Advisories

(5)

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

Frequently asked(4)

What is CVE-2005-3275?
CVE-2005-3275 is a low vulnerability published on October 21, 2005. The NAT code (1) ipnatprototcp.c and (2) ipnatprotoudp.c in Linux kernel 2.6 before 2.6.13 and 2.4 before 2.4.32-rc1 incorrectly declares a variable to be static, which allows remote attackers to cause a denial of service (memory corruption) by causing two packets for the same protocol to be NATed…
When was CVE-2005-3275 disclosed?
CVE-2005-3275 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-3275 actively exploited?
CVE-2005-3275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 12.1% of all scored CVEs.
How do I remediate CVE-2005-3275?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-3275, 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-3275

Explore →

Is Your Infrastructure Affected by CVE-2005-3275?

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

Start Free Scan →Browse All CVEs