Skip to content
Fencer Vulns
high 7.8

CVE-2008-4618 json

The Stream Control Transmission Protocol (sctp) implementation in the Linux kernel before 2.6.27 does not properly handle a protocol violat…

published 2008-10-20 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4598

cvss
7.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

The Stream Control Transmission Protocol (sctp) implementation in the Linux kernel before 2.6.27 does not properly handle a protocol violation in which a parameter has an invalid length, which allows attackers to cause a denial of service (panic) via unspecified vectors, related to sctp_sf_violation_paramlen, sctp_sf_abort_violation, sctp_make_abort_violation, and incorrect data types in function calls.

Patch / fix

  • kernel-rt enterprise mrg 1 2.6.24.7-93.el5rt
  • kernel-rt-trace enterprise mrg 1 2.6.24.7-93.el5rt
  • kernel-rt-vanilla enterprise mrg 1 2.6.24.7-93.el5rt
  • kernel-rt-debuginfo-common enterprise mrg 1 2.6.24.7-93.el5rt

red hat advisories RHSA-2009:0009

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2008-4618 updated

kernel: sctp: Fix kernel panic while process protocol violation parameter

  • Red Hat MRG Realtime for RHEL 5 Server kernel-rt 2.6.24.7-93.el5rt, kernel-rt-trace 2.6.24.7-93.el5rt, kernel-rt-vanilla 2.6.24.7-93.el5rt, kernel-rt-debuginfo-common 2.6.24.7-93.el5rt
    fixed: vendor fix RHSA-2009:0009

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.66% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.