CVE-2010-5321
First published: Tue Aug 03 2010(Updated: )
Description of problem: Since videobuf allocates memory on mmap(), calling mmap enough times for the same buffer (offset) resulted in a new memory allocation by videobuf on each such call and losing the old allocation, resulting in a leak each time and the system running out of memory.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/linux | <=4.6.2-1<=3.2.41-2<=3.2.78-1 | |
| debian/linux | <=5.10.218-1<=5.10.223-1<=6.1.94-1<=6.1.99-1<=6.10.3-1<=6.10.4-1 | |
| Linux kernel | >=2.6.0<=4.20.15 | |
| Linux Kernel | >=2.6.0<=4.20.15 |
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
- http://linuxtv.org/irc/v4l/index.php?date=2010-07-29
- http://www.openwall.com/lists/oss-security/2015/02/08/4
- https://access.redhat.com/security/updates/classification/
- https://bugzilla.redhat.com/show_bug.cgi?id=620629
- https://bugzilla.kernel.org/show_bug.cgi?id=120571
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827340
- https://bugzilla.redhat.com/show_bug.cgi?id=620629#c0
- https://security-tracker.debian.org/tracker/CVE-2010-5321
- https://linuxtv.org/irc/v4l/index.php?date=2010-07-29
- https://bugzilla.kernel.org/
- http://www.gossamer-threads.com/lists/linux/kernel/852719?page=last
Frequently Asked Questions
What is the severity of CVE-2010-5321?
CVE-2010-5321 is considered a high severity vulnerability due to its potential to cause memory leaks.
How do I fix CVE-2010-5321?
To address CVE-2010-5321, it is recommended to upgrade the affected Linux kernel versions to a fixed release.
What is the impact of CVE-2010-5321?
The impact of CVE-2010-5321 includes excessive memory usage leading to the system potentially running out of memory.
Which software versions are affected by CVE-2010-5321?
CVE-2010-5321 affects specific versions of the Linux kernel, including those up to 4.0 and certain 5.x versions.
Is CVE-2010-5321 exploitably remote?
CVE-2010-5321 is not considered remotely exploitable as it generally requires local access to trigger the memory leak.
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/weakness
- agent/references
- agent/severity
- agent/description
- agent/event
- collector/debian-bugs
- source/Debian
- alias/CVE-2010-5321
- agent/software-canonical-lookup
- collector/redhat-bugzilla
- source/Red Hat
- collector/security-tracker-debian
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/2.6.0
- version/linux kernel/4.20.15