CVE-2007-2172

MEDIUMCVSS v2 · 4.74.7—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.7 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:M/Au:N/C:N/I:N/A:C. 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 0.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS v2: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A typo in Linux kernel 2.6 before 2.6.21-rc6 and 2.4 before 2.4.35 causes RTA_MAX to be used as an array size instead of RTN_MAX, which leads to an "out of bound access" by the (1) dn_fib_props (dn_fib.c, DECNet) and (2) fib_props (fib_semantics.c, IPv4) functions.

CVSS v2.0 (legacy)
4.7MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.7MEDIUMlow confidence
EG Risk
26
EG Risk 26/100

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 (value × EchelonGraph’s weight)
Severity47% × 45%
The EG Score, 4.7 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

April 22, 2007

Last Modified

April 23, 2026

References (32)

15 of 32 shown · show the other 17

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-2.6.15-28-sparc64 (2.6.15-28.55) @ dapper2026-05-31ubuntu
redhatkernel-0:2.4.9-e.742009-01-08redhat
redhatkernel-0:2.4.18-e.672009-01-05redhat
redhatkernel-0:2.4.21-53.EL2007-12-03redhat
redhatkernel-0:2.6.9-55.0.2.EL2007-06-25redhat
redhatkernel-0:2.6.18-8.1.4.el52007-05-16redhat

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

(32 across 2 ecosystems)
Debian:3.1(31)
PackageVulnerable rangeFix by version rangeDependents
fai-kernels1.9.1 ... 1.9.1sarge7.1 (9 versions)
  • every version up to 1.9.1sarge8: fixed in 1.9.1sarge8
—
hostap-modules-i3861:0.3.7-1, 1:0.3.7-1sarge1, 1:0.3.7-1sarge2
  • every version up to 1:0.3.7-1sarge3: fixed in 1:0.3.7-1sarge3
—
i2c1:2.9.1-1, 1:2.9.1-1sarge1
  • every version up to 1:2.9.1-1sarge2: fixed in 1:2.9.1-1sarge2
—
kernel-image-2.4.27-alpha2.4.27-10 ... 2.4.27-10sarge5 (6 versions)
  • every version up to 2.4.27-10sarge6: fixed in 2.4.27-10sarge6
—
kernel-image-2.4.27-arm2.4.27-2 ... 2.4.27-2sarge5 (6 versions)
  • every version up to 2.4.27-2sarge6: fixed in 2.4.27-2sarge6
—
kernel-image-2.4.27-i3862.4.27-10 ... 2.4.27-10sarge5 (6 versions)
  • every version up to 2.4.27-10sarge6: fixed in 2.4.27-10sarge6
—
kernel-image-2.4.27-ia642.4.27-10 ... 2.4.27-10sarge5 (6 versions)
  • every version up to 2.4.27-10sarge6: fixed in 2.4.27-10sarge6
—
kernel-image-2.4.27-m68k2.4.27-3 ... 2.4.27-3sarge5 (6 versions)
  • every version up to 2.4.27-3sarge6: fixed in 2.4.27-3sarge6
—
kernel-image-2.4.27-s3902.4.27-2 ... 2.4.27-2sarge5 (6 versions)
  • every version up to 2.4.27-2sarge6: fixed in 2.4.27-2sarge6
—
kernel-image-2.4.27-sparc2.4.27-9 ... 2.4.27-9sarge5 (6 versions)
  • every version up to 2.4.27-9sarge6: fixed in 2.4.27-9sarge6
—
kernel-image-2.6.8-alpha2.6.8-16 ... 2.6.8-17 (9 versions)
  • every version up to 2.6.8-17sarge1: fixed in 2.6.8-17sarge1
—
kernel-image-2.6.8-amd642.6.8-14 ... 2.6.8-17 (8 versions)
  • every version up to 2.6.8-17sarge1: fixed in 2.6.8-17sarge1
—
kernel-image-2.6.8-hppa2.6.8-6 ... 2.6.8-7 (9 versions)
  • every version up to 2.6.8-7sarge1: fixed in 2.6.8-7sarge1
—
kernel-image-2.6.8-i3862.6.8-16 ... 2.6.8-17 (9 versions)
  • every version up to 2.6.8-17sarge1: fixed in 2.6.8-17sarge1
—
kernel-image-2.6.8-ia642.6.8-14 ... 2.6.8-15 (9 versions)
  • every version up to 2.6.8-15sarge1: fixed in 2.6.8-15sarge1
—
kernel-image-2.6.8-m68k2.6.8-4 ... 2.6.8-5 (9 versions)
  • every version up to 2.6.8-5sarge1: fixed in 2.6.8-5sarge1
—
kernel-image-2.6.8-s3902.6.8-5 ... 2.6.8-6 (9 versions)
  • every version up to 2.6.8-6sarge1: fixed in 2.6.8-6sarge1
—
kernel-image-2.6.8-sparc2.6.8-15 ... 2.6.8-16 (9 versions)
  • every version up to 2.6.8-16sarge1: fixed in 2.6.8-16sarge1
—
kernel-image-speakup-i3862.4.27-1.1, 2.4.27-1.1sarge1, 2.4.27-1.1sarge2, 2.4.27-1.1sarge3, 2.4.27-1.1sarge4
  • every version up to 2.4.27-1.1sarge5: fixed in 2.4.27-1.1sarge5
—
kernel-latest-2.4-alpha101, 101sarge1
  • every version up to 101sarge3: fixed in 101sarge3
—
kernel-latest-2.4-i386101, 101sarge1
  • every version up to 101sarge2: fixed in 101sarge2
—
kernel-latest-2.4-s3902.4.27-1, 2.4.27-1sarge1
  • every version up to 2.4.27-1sarge2: fixed in 2.4.27-1sarge2
—
kernel-latest-2.4-sparc42, 42sarge1, 42sarge2
  • every version up to 42sarge3: fixed in 42sarge3
—
kernel-patch-2.4.27-mips2.4.27-10.040815-1 ... 2.4.27-10.sarge4.040815-2 (6 versions)
  • every version up to 2.4.27-10.sarge4.040815-3: fixed in 2.4.27-10.sarge4.040815-3
—
kernel-patch-powerpc-2.4.272.4.27-10 ... 2.4.27-10sarge5 (6 versions)
  • every version up to 2.4.27-10sarge6: fixed in 2.4.27-10sarge6
—
kernel-patch-powerpc-2.6.82.6.8-12 ... 2.6.8-13 (9 versions)
  • every version up to 2.6.8-13sarge1: fixed in 2.6.8-13sarge1
—
kernel-source-2.4.272.4.27-10 ... 2.4.27-10sarge6 (7 versions)
  • every version up to 2.4.27-10sarge6: fixed in 2.4.27-10sarge6
  • every version up to 2.4.27-10sarge7: fixed in 2.4.27-10sarge7
—
kernel-source-2.6.82.6.8-16 ... 2.6.8-17 (9 versions)
  • every version up to 2.6.8-17sarge1: fixed in 2.6.8-17sarge1
—
mindi-kernel2.4.27-2, 2.4.27-2sarge1, 2.4.27-2sarge2, 2.4.27-2sarge3, 2.4.27-2sarge4
  • every version up to 2.4.27-2sarge5: fixed in 2.4.27-2sarge5
—
pcmcia-modules-2.4.27-i3863.2.5+2, 3.2.5+2sarge1
  • every version up to 3.2.5+2sarge2: fixed in 3.2.5+2sarge2
—
systemimager3.2.3-6, 3.2.3-6sarge1, 3.2.3-6sarge2, 3.2.3-6sarge3, 3.2.3-6sarge4
  • every version up to 3.2.3-6sarge5: fixed in 3.2.3-6sarge5
—
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
linux-2.62.6.18.dfsg.1-12, 2.6.18.dfsg.1-12etch1, 2.6.18.dfsg.1-12etch2, 2.6.18.dfsg.1-13, 2.6.18.dfsg.1-13etch1
  • every version up to 2.6.18.dfsg.1-13etch1: fixed in 2.6.18.dfsg.1-13etch1
  • every version up to 2.6.18.dfsg.1-13etch2: fixed in 2.6.18.dfsg.1-13etch2
—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 8× in last 7d / 14× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 77 of 98 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 23 repeat rows among the latest 100 are merged into the row they repeat. The 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2007-2172?
CVE-2007-2172 is a medium-severity vulnerability; its CVE record was published on April 22, 2007. A typo in Linux kernel 2.6 before 2.6.21-rc6 and 2.4 before 2.4.35 causes RTAMAX to be used as an array size instead of RTNMAX, which leads to an "out of bound access" by the (1) dnfibprops (dnfib.c, DECNet) and (2) fibprops (fib_semantics.c, IPv4) functions.
When was the CVE record for CVE-2007-2172 published?
The CVE record for CVE-2007-2172 was published on April 22, 2007. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2007-2172 actively exploited?
CVE-2007-2172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-2172?
A fix for CVE-2007-2172 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2007-2172

Explore →

Is Your Infrastructure Affected by CVE-2007-2172?

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

Book a Demo →Browse All CVEs