Bug 113103 - CAN-2003-0984 minor /dev/rtc leak
CAN-2003-0984 minor /dev/rtc leak
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ernie Petrides
Brian Brock
: Security
Depends On:
Blocks: 107562
  Show dependency treegraph
Reported: 2004-01-08 10:34 EST by Mark J. Cox
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: 2004-05-11 21:08:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2004:188 normal SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 2 2004-05-11 00:00:00 EDT

  None (edit)
Description Mark J. Cox 2004-01-08 10:34:07 EST
CAN-2003-0984: /dev/rtc leak

An uninitialised buffer leaks a few bytes to user space.  Made public
by SuSE Dec04 although was not fixed upstream (at least as far as
2.4.22).  This issue is fixed in our other distributions.

The security implications are minor however at least one publication
(ZDNet) decided to call this a critical security vulnerability,
raising its profile out of all proportion.
Comment 1 Mark J. Cox 2004-01-08 10:50:35 EST
actually fixed in 2.4.23, see

Comment 2 Ernie Petrides 2004-02-19 01:58:55 EST
The RHEL 3 fix for this problem was committed to the U2 patch
pool tonight and will be available internally in kernel version
Comment 3 John Flanagan 2004-05-11 21:08:16 EDT
An errata 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.