CVE-2013-4513 json
Buffer overflow in the oz_cdev_write function in drivers/staging/ozwpan/ozcdev.c in the Linux kernel before 3.12 allows local users to caus…
published 12y ago modified 4mo ago also EUVD-2013-4373
- cvss
- 4.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
Buffer overflow in the oz_cdev_write function in drivers/staging/ozwpan/ozcdev.c in the Linux kernel before 3.12 allows local users to cause a denial of service or possibly have unspecified other impact via a crafted write operation.
Patch / fix
- linux Debian 14, Debian 13, Debian 12 3.12-1
debian advisories DEBIAN-CVE-2013-4513
Is CVE-2013-4513 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4513 updated cvss 6.6
Kernel: staging: ozwpan: buffer overflow in oz_cdev_write
-
Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, python-perf, kernel-kdump, kernel-tools, +3 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
github.com
/torvalds/linux/commit/c2c65cd2e14ada6de44cb527e7f1990bede24e15
patch
-
kernel.org
/pub/linux/kernel/v3.x/patch-3.12.bz2
patch
-
ubuntu.com
/usn/USN-2073-1
vendor-advisory
-
ubuntu.com
/usn/USN-2076-1
vendor-advisory
-
ubuntu.com
/usn/USN-2069-1
vendor-advisory
-
ubuntu.com
/usn/USN-2070-1
vendor-advisory
-
ubuntu.com
/usn/USN-2071-1
vendor-advisory
-
ubuntu.com
/usn/USN-2074-1
vendor-advisory
-
ubuntu.com
/usn/USN-2068-1
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-02/msg00002.html
vendor-advisory
-
ubuntu.com
/usn/USN-2072-1
vendor-advisory
-
ubuntu.com
/usn/USN-2075-1
vendor-advisory
- git.kernel.org /?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=c2c65cd2e14ada6de44cb527e7f1990bede24e15
-
openwall.com
/lists/oss-security/2013/11/04/22
mailing-list
-
securityfocus.com
/bid/63508
vdb-entry
Sources
- CVE List CVE-2013-4513
- NVD CVE-2013-4513
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.