Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2010-5321

kernel: v4l: videobuf: hotfix a bug on multiple calls to mmap()

Overview

Published
24 Apr 2017
Modified
13 May 2026
Medium CVE
0 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

Memory leak in drivers/media/video/videobuf-core.c in the videobuf subsystem in the Linux kernel 2.6.x through 4.x allows local users to cause a denial of service (memory consumption) by leveraging /dev/video access for a series of mmap calls that require new allocations, a different vulnerability than CVE-2007-6761. NOTE: as of 2016-06-18, this affects only 11 drivers that have not been updated to use videobuf2 instead of videobuf.

Source: OX vulnerability database

Severity

4.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Physical
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-772

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 4 releases · 1 package

affected 4
linux
debian fixes for CVE-2010-5321
ReleasePackageFixed in
11 linux affected
12 linux affected
13 linux affected
14 linux affected

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2010-5321
ReleasePackageFixed in
linux 1

root.io debian 3 releases · 2 packages

affected 1 fixed 2
rootio-linux linux
root.io debian fixes for CVE-2010-5321
ReleasePackageFixed in
11 rootio-linux affected
12 linux +1 6.1.172-1.root.io.132
13 linux +1 6.12.90-1.root.io.129

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.