REDHAT-BUG-646725
First published: Tue Oct 26 2010(Updated: )
Description of problem: Calling ETHTOOL_GRXCLSRLALL with a large rule_cnt will allocate kernel heap without clearing it. For the one driver (niu) that implements it, it will leave the unused portion of heap unchanged and copy the full contents back to userspace. This is different from <a href="https://access.redhat.com/security/cve/CVE-2010-2478">CVE-2010-2478</a>, but was introduced at the same time (0853ad66, 2.6.27-rc1). Upstream commit: <a href="http://git.kernel.org/linus/ae6df5f96a51818d6376da5307d773baeece4014">http://git.kernel.org/linus/ae6df5f96a51818d6376da5307d773baeece4014</a> Acknowledgements: Red Hat would like to thank Kees Cook for reporting this issue.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Linux | >=2.6.27-rc1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://access.redhat.com/security/cve/CVE-2010-2478
- http://git.kernel.org/linus/ae6df5f96a51818d6376da5307d773baeece4014
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=608950#c2
- https://rhn.redhat.com/errata/RHSA-2010-0958.html
- https://rhn.redhat.com/errata/RHSA-2011-0007.html
- https://bugzilla.redhat.com/show_bug.cgi?id=646725
Frequently Asked Questions
What is the severity of REDHAT-BUG-646725?
The severity of REDHAT-BUG-646725 is considered high due to potential exposure of sensitive information.
How do I fix REDHAT-BUG-646725?
To fix REDHAT-BUG-646725, you should update the affected Linux kernel to the latest version that addresses this vulnerability.
Which versions of Red Hat Linux are affected by REDHAT-BUG-646725?
Red Hat Linux kernel versions from 2.6.27-rc1 and later are affected by REDHAT-BUG-646725.
What type of vulnerability is REDHAT-BUG-646725?
REDHAT-BUG-646725 is a heap memory allocation vulnerability that can lead to information disclosure.
Is there a workaround for REDHAT-BUG-646725?
Currently, the recommended action is to apply the available kernel updates since there are no effective workarounds to mitigate REDHAT-BUG-646725.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2010-3861
- agent/source
- agent/severity
- agent/description
- agent/event
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/red hat linux