Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 154551 - CAN-2005-1041 crash while reading /proc/net/route
CAN-2005-1041 crash while reading /proc/net/route
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Miller
Brian Brock
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-04-12 12:46 EDT by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-19 14:52:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fix for /proc/net/route OOPS (1.04 KB, patch)
2005-04-12 15:37 EDT, David Miller
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:366 high SHIPPED_LIVE Important: kernel security update 2005-04-19 00:00:00 EDT

  None (edit)
Description Josh Bressers 2005-04-12 12:46:34 EDT
The fib_seq_start function in fib_hash.c in Linux kernel allows local
users to cause a denial of service (system crash) via /proc/net/route.

Comment 1 David Miller 2005-04-12 15:36:08 EDT
I have already submitted the fix for this for RHEL4 inclusion.
I'll attach it here,  but can someone verify that it got put
into the RHEL4 tree already?
Comment 2 David Miller 2005-04-12 15:37:08 EDT
Created attachment 113048 [details]
Fix for /proc/net/route OOPS
Comment 3 Dave Jones 2005-04-12 15:40:57 EDT
Comment 4 Josh Bressers 2005-04-19 14:52:30 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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