Skip to content

CVE-2013-2094

is CVE-2013-2094real, exploitable, or a false positive? Here's the community ground truth.

High · CVSS 8.4EPSS 47.7%CISA KEVCWE-189

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

The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows local users to gain privileges via a crafted perf_event_open system call.

Published

Embed this verdict
TruePositive verdict for CVE-2013-2094
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2013-2094/badge.svg)](https://www.truepositive.app/cve/CVE-2013-2094)
HTML
<a href="https://www.truepositive.app/cve/CVE-2013-2094"><img src="https://www.truepositive.app/cve/CVE-2013-2094/badge.svg" alt="TruePositive verdict for CVE-2013-2094"></a>

Live badge — updates automatically as the community verdict changes.

Community ground truth

Community verdict

2 verdicts
Not a real issue

Includes TruePositive's curated baseline from public sources — community verdicts accrue on top.

Pick your verdict — we'll save it right after a quick sign-in.

Community real-world severity: High (High 2) — CVSS base score 8.4

In line with its CVSS base score.

Field notes & remediation

Verdicts are the quick signal — notes are the evidence and fixes behind them.

  • 0
    Field note · Waleed AzizCurated

    Linux Kernel Privilege Escalation Vulnerability — Linux kernel fails to check all 64 bits of attr.config passed by user space, resulting to out-of-bounds access of the perf_swevent_enabled array in sw_perf_event_destroy(). Explotation allows for privilege escalation. Listed in the CISA KEV catalog (added 2022-09-15) — confirmed exploited in the wild, not theoretical. FIRST EPSS puts the chance of exploitation in the next 30 days at ~48%. Treat it as real and prioritize remediation over triage.

  • 0
    Remediation · Priya NairCurated

    Required action for Linux Kernel: Apply updates per vendor instructions. CISA set a federal remediation due date of 2022-10-06. After patching, verify the vulnerable path is no longer reachable before closing the finding.