RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 609333 - out-of-bounds memory access for valuators > MAX_VALUATORS
Summary: out-of-bounds memory access for valuators > MAX_VALUATORS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-evdev
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-30 01:24 UTC by Peter Hutterer
Modified: 2010-11-15 13:46 UTC (History)
1 user (show)

Fixed In Version: xorg-x11-drv-evdev-2.3.2-7.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 13:46:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter Hutterer 2010-06-30 01:24:02 UTC
Description of problem:
An evdev device with more than 36 axes overruns internal array boundaries. This can currently only happen with absolute devices since the kernel does not provide for > 36 relative axes.

Version-Release number of selected component (if applicable):
xorg-x11-drv-evdev-2.3.2-6.el6

How reproducible:
Plug in a device with more than 36 absolute axes (uinput may be used). 
EvdevAddAbsClass will overwrite memory when resetting pEvdev->vals. There's no visible output because the structs overwritten are internal to evdev. Verification by inspection or with gdb.
  
Additional info:
https://bugs.freedesktop.org/show_bug.cgi?id=28809

Example uinput device to reproduce this behaviour is here:
http://cgit.freedesktop.org/~whot/testdevices/commit/?id=e6a09f8caa8617aa6efb4af133f560be5aa670c4

Comment 1 RHEL Program Management 2010-06-30 01:43:06 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Peter Hutterer 2010-06-30 04:10:12 UTC
MODIFIED

xorg-x11-drv-evdev-2.3.2-7.el6 is available in brew.

Comment 4 Vladimir Benes 2010-11-15 12:29:09 UTC
using in comment #0 mentioned test device w/ 63 axes I can see warning in /var/log/Xorg.0.log:

(II) XINPUT: Adding extended input device "allaxes test device" (type: TOUCHPAD)
(WW) allaxes test device: found 63 axes, limiting to 36.
(WW) Device 'allaxes test device' has 36 axes, only using first 36.

which is correct behaviour
-> VERIFIED

Comment 5 releng-rhel@redhat.com 2010-11-15 13:46:28 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. 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.