dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 25 Mar 2025.
Debian LinuxOperating system · Debian

CVE-2024-50302

MEDIUM · 5.5 CVSS v3.1 Published 2024-11-19
Fix available
A fix is available. Upgrade to 3.2 / 4.19.324 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The HID (Human Interface Device) core in the Linux kernel fails to zero-initialize the report buffer during allocation. This uninitialized memory can contain residual kernel data that may be leaked through specially-crafted HID reports, allowing local or physical attackers to potentially read sensitive kernel memory contents.

MitigationApply the kernel patch that zero-initializes the report buffer during allocation. Update to a kernel version containing this fix. For systems unable to update immediately, restrict access to untrusted HID devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
Linux KernelOperating system
Affected:>= 3.12, < 4.19.324>= 4.20, < 5.4.286>= 5.5, < 5.10.230>= 5.11, < 5.15.172>= 5.16, < 6.1.117>= 6.2, < 6.6.61>= 6.7, < 6.11.8= 6.12
AndroidOperating system
Affected:all versions
Simatic S7 1500 Tm Mfp FirmwareOperating system
Affected:all versions
Sinec OsOperating system
Affected:< 3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the running Linux kernel version
    Run `uname -r` or `cat /proc/version` to obtain the kernel version string
    Affected if The kernel version falls within any of these vulnerable ranges: >= 3.12 and < 4.19.324; >= 4.20 and < 5.4.286; >= 5.5 and < 5.10.230; >= 5.11 and < 5.15.172; >= 5.16 and < 6.1.117; >= 6.2 and < 6.6.61; >= 6.7 and < 6.11.8; or equals exactly 6.12
  2. Confirm the HID subsystem is in use
    Run `lsmod | grep hid` to list loaded HID-related kernel modules, or check /sys/bus/hid/devices for connected HID devices
    Affected if The system has HID modules loaded or has HID devices present, making the uninitialized buffer code path reachable
  3. Verify the report buffer allocation code path exists
    Check if the kernel source file drivers/hid/hid-core.c contains the vulnerable allocation function and is used at runtime
    Affected if The system uses the Linux kernel HID driver to process HID reports, which triggers the non-zero-initialized buffer allocation

A system is affected if it runs a Linux kernel version within the vulnerable ranges listed and uses the HID subsystem to process HID device reports.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2 / 4.19.324 / 5.4.286 or later
Fixed in 3.24.19.3245.4.286
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch that zero-initializes the report buffer during allocation. Update to a kernel version containing this fix. For systems unable to update immediately, restrict access to untrusted HID devices.

Recommended fix High confidence

Linux Kernel 4.19.324+ / 5.4.286+ / 5.10.230+ / 5.15.172+

  1. Upgrade Linux kernel to version 4.19.324 or later for 4.19.x branch
  2. Upgrade Linux kernel to version 5.4.286 or later for 5.4.x branch
  3. Upgrade Linux kernel to version 5.10.230 or later for 5.10.x branch
  4. Upgrade Linux kernel to version 5.15.172 or later for 5.15.x branch
  5. For Android devices: apply vendor-specific security update
  6. For Simatic S7 1500 Tm Mfp Firmware: apply vendor firmware patch
  7. For Sinec OS: upgrade to version 3.2 or later
  8. For Debian 11.0: apply Debian kernel security updates
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom kernel modules

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-50302 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data