Actively exploited

CVE-2024-50302 Linux Kernel Use of Uninitialized Resource Vulnerability

The Linux kernel contains a use of uninitialized resource vulnerability that allows an attacker to leak kernel memory via a specially crafted HID report.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 4 Mar 2025.
  • Rated Medium severity (CVSS 5.5, scored by CISA).
  • It has been in the catalogue for 612 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.

Affected Versions

ProductVersions
Linux Linux27ce405039bfe6d3f4143415c638f56a3df77dca to before e7ea60184e1e88a3c9e437b3265cbb6439aa7e26
27ce405039bfe6d3f4143415c638f56a3df77dca to before 3f9e88f2672c4635960570ee9741778d4135ecf5
27ce405039bfe6d3f4143415c638f56a3df77dca to before d7dc68d82ab3fcfc3f65322465da3d7031d4ab46
27ce405039bfe6d3f4143415c638f56a3df77dca to before 05ade5d4337867929e7ef664e7ac8e0c734f1aaf
27ce405039bfe6d3f4143415c638f56a3df77dca to before 1884ab3d22536a5c14b17c78c2ce76d1734e8b0b
27ce405039bfe6d3f4143415c638f56a3df77dca to before 9d9f5c75c0c7f31766ec27d90f7a6ac673193191
Linux Linux3.12

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Linux Kernel. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-50302 and every other exploited flaw on the list.

Check My Exposure