CVE-2024-50302: HID: core: zero-initialize the report buffer
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-50302 is a Linux kernel information disclosure flaw in HID handling. A specially crafted HID report could expose kernel memory because a report buffer was not zero-initialized. The base severity is medium, but CISA KEV listing raises urgency because exploitation is documented there.
Executive priority
Treat as urgent for Linux fleets because CISA KEV indicates real-world exploitation. It is not a remote takeover issue in the provided evidence, but kernel memory disclosure can support broader compromise chains.
Technical view
The Linux HID core allocated a report buffer without zero-initializing it. Because many HID drivers share this buffer, crafted reports could cause disclosure of uninitialized kernel memory. CVSS is 5.5 with local access, low complexity, low privileges, no user interaction, and high confidentiality impact.
Likely exposure
Linux systems running affected kernel versions or downstream vendor builds are in scope. Exposure depends on kernel lineage and backported fixes, so distro and appliance advisories matter more than upstream version strings alone.
Exploitation context
CISA KEV status supports known exploitation. The provided data does not describe public exploit code, targets, or attack procedures. The CVSS vector indicates a local, low-privilege confidentiality issue rather than remote code execution.
Researcher notes
Focus validation on whether the HID core fix is present in the running kernel source or vendor package. Do not rely only on upstream version numbers, because distro kernels commonly backport security patches.
Mitigation direction
Apply vendor-provided Linux kernel updates or fixed downstream packages.
Prioritize systems covered by CISA KEV requirements or exposed multi-user workloads.
Check Debian, Siemens, and other vendor advisories for backported fixes.
Avoid direct wrangler-style assumptions; validate kernel package provenance before closure.
Validation and detection
Inventory Linux kernel versions and vendor appliance firmware using affected advisories.
Confirm installed kernels include the HID report buffer zero-initialization fix.
Map Debian LTS package updates to deployed Debian systems.
Review CISA KEV tracking for required remediation deadlines.
Document exceptions where vendors have not yet issued guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-908: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-908 · source CWE mapping
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.