Threats / Linux / CVE-2022-2586
CVE-2022-2586
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Linux Kernel vulnerability
Linux Kernel use-after-free vulnerability in nft_object allows local attackers to escalate privileges.
Verdict
Today item — known-exploited.
A use-after-free flaw in the Linux Kernel's nft_object component enables local privilege escalation. The vulnerability has been exploited in the wild, posing active risk to systems where untrusted local users have access.
CISA KEV Yes · 2024-06-265EPSS 0.10458 (verify live)6Exploit Public PoC7CVSS 5.33CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-06-26).
Probability (EPSS)
EPSS 0.10458 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.3 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H) · Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 170 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain local system access as an unprivileged user.
Business
An attacker establishes initial foothold on the system through compromised credentials or application vulnerability.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the use-after-free condition in nft_object through crafted netfilter operations.
Business
The vulnerability becomes exploitable when the attacker interacts with kernel netfilter subsystem components.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with kernel privileges by corrupting memory state.
Business
Privilege escalation grants the attacker root-level control over the compromised system.
4
Data at risk — exfiltration narrative 4
Attacker
I maintain persistent access and move laterally across the infrastructure.
Business
Full system compromise enables data exfiltration, lateral movement, and establishment of persistent backdoors.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by canonicalCNA
Credited with finding itTeam Orca of Sea Security (@seasecresponse) working with Trend Micro's Zero Day Initiativefinder