basicsecurity.net
Proof, not just disclosure.
Threats / Linux / CVE-2024-1086
CVE-2024-1086 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Linux Kernel vulnerability

Linux kernel netfilter nf_tables use-after-free vulnerability enables local privilege escalation. Actively exploited in ransomware campaigns.

Verdict

Today item, not a backlog item.

A use-after-free flaw in the Linux kernel netfilter nf_tables subsystem allows local attackers to escalate privileges. The vulnerability is actively exploited in the wild and associated with ransomware operations, presenting significant risk to affected systems.

CISA KEV Yes · 2024-05-303Ransomware use Flagged3EPSS 0.23582 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
7 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-05-30), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.23582 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-416 · Use After FreeMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious nf_tables rule that references freed memory to trigger the use-after-free condition.
Business
An unprivileged local user gains kernel-level code execution on the system.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute the exploit to escalate my privileges from unprivileged user to root.
Business
The attacker obtains full system control, bypassing all access controls and security boundaries.
3

Lateral reach — past segmentation narrative 3

Attacker
I install persistent backdoors and deploy ransomware payloads across the compromised infrastructure.
Business
Critical data is encrypted, systems become unavailable, and ransom demands are issued to the organization.
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’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 7 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by Google (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by GoogleCNA
    Credited with finding itNotselwynfinder