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

Linux Kernel vulnerability

The Linux kernel contains a use of uninitialized resource vulnerability allowing attackers to leak kernel memory through specially crafted HID reports.

Verdict

Today item — known-exploited.

A local attacker can exploit uninitialized memory in the kernel's HID subsystem to disclose sensitive kernel data, potentially enabling further privilege escalation or system compromise.

CISA KEV Yes · 2025-03-043EPSS 0.00809 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
6 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 2025-03-04).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00809 — 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-908 Use of Uninitialized Resource — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
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 HID report to trigger uninitialized memory access in the kernel.
Business
Kernel memory disclosure exposes sensitive data that could compromise system security posture.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I read leaked kernel memory to identify addresses and sensitive information for further exploitation.
Business
Information disclosure undermines defense mechanisms like ASLR and enables targeted privilege escalation attacks.
3

Lateral reach — past segmentation narrative 3

Attacker
I use the leaked kernel addresses to construct follow-up exploits targeting kernel code or data structures.
Business
Chained exploitation leads to unauthorized code execution with kernel privileges, enabling full system compromise.
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)
  • EPSS probability (FIRST)
  • 6 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Linux (CNA)
  • 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.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by LinuxCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.