Bug 155234 - CAN-2005-0137 ia64 syscall_table DoS
CAN-2005-0137 ia64 syscall_table DoS
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
ia64 Linux
medium Severity high
: ---
: ---
Assigned To: Jason Baron
Brian Brock
reported=20050208,embargo=20050311,im...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-18 08:03 EDT by Mark J. Cox (Product Security)
Modified: 2013-03-06 00:58 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-22 16:17:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox (Product Security) 2005-04-18 08:03:41 EDT
Jason Baron noted that this issue also affected RHEL3

+++ This bug was initially created as a clone of Bug #148860 +++

Mike O'Connor mentioned to vendor-sec on Feb08:

        The number of entries in the syscall_table is incorrect. The
        exception handling code assumes that there are 255 entries but
        there are only 254.  If any user issues syscall number
        1024+255 (1279), the exception handler jumps to garbage, and
        voila -- instead of ENOSYS, you get a DoS.

This looks valid, arch/ia64/kernel/entry.S only contains 255 entries
(see end of file) and is missing a "data8 ia64_ni_syscall" from the end.

DoS itself not verified but should be easily reproducable.

** Currently embargoed, no date yet set. **
Comment 1 Mark J. Cox (Product Security) 2005-04-18 08:05:05 EDT
"below is the tested rhel3 version of the patch. 

-Jason"

--- linux-2.4.21/arch/ia64/kernel/entry.S.bak
+++ linux-2.4.21/arch/ia64/kernel/entry.S
@@ -1305,3 +1305,4 @@ sys_call_table:
        data8 ia64_ni_syscall
        data8 ia64_ni_syscall
        data8 ia64_ni_syscall
+       data8 ia64_ni_syscall
Comment 2 Ernie Petrides 2005-04-18 13:28:14 EDT
A fix for this problem was committed to the RHEL3 E5 patch
pool on 13-Apr-2005 (in kernel version 2.4.21-27.0.3.EL).
Comment 3 Ernie Petrides 2005-04-18 13:28:54 EDT
A fix for this problem was also committed to the RHEL3 U5
patch pool on 15-Apr-2005 (in kernel version 2.4.21-32.EL).
Comment 4 Josh Bressers 2005-04-22 16:17:41 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.

http://rhn.redhat.com/errata/RHSA-2005-293.html
Comment 5 Tim Powers 2005-05-18 09:29:25 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.

http://rhn.redhat.com/errata/RHSA-2005-294.html

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