Bug 465730 (CVE-2008-4618) - CVE-2008-4618 kernel: sctp: Fix kernel panic while process protocol violation parameter
Summary: CVE-2008-4618 kernel: sctp: Fix kernel panic while process protocol violation...
Alias: CVE-2008-4618
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 465731
TreeView+ depends on / blocked
Reported: 2008-10-06 06:05 UTC by Eugene Teo (Security Response)
Modified: 2021-11-12 19:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-21 17:45:40 UTC

Attachments (Terms of Use)
Upstream patch for this issue (7.03 KB, patch)
2008-10-06 06:13 UTC, Eugene Teo (Security Response)
no flags Details | Diff

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:0009 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2009-01-22 10:43:54 UTC

Description Eugene Teo (Security Response) 2008-10-06 06:05:14 UTC
Description of problem:
Wei Yongjun reported that "Since call to function sctp_sf_abort_violation() need paramter 'arg' with 'struct sctp_chunk' type, it will read the chunk type and chunk length from the chunk_hdr member of chunk. But call to sctp_sf_violation_paramlen() always with 'struct sctp_paramhdr' type's parameter, it will be passed to sctp_sf_abort_violation(). This may cause kernel panic.

     |-- sctp_sf_abort_violation()
        |-- sctp_make_abort_violation()

This patch fixed this problem. This patch also fix two place which called sctp_sf_violation_paramlen() with wrong paramter type."

Comment 2 Eugene Teo (Security Response) 2008-10-06 06:13:47 UTC
Created attachment 319518 [details]
Upstream patch for this issue

Comment 5 Luis Claudio R. Goncalves 2008-10-06 18:16:06 UTC
MRG: Patch added to -85

Comment 6 Vincent Danen 2010-12-21 17:45:40 UTC
This was addressed via:

MRG Realtime for RHEL 5 Server (RHSA-2009:0009)

Note You need to log in before you can comment on or make changes to this bug.