How severe is CVE-2024-50302?

CVE-2024-50302 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-50302?

CVE-2024-50302 affects the following packages: Kernel (Linux). Ecosystems affected: Linux.

How do I fix CVE-2024-50302?

Update Kernel to 4.19.324 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-50302 is resolved across your whole dependency graph.

How do I detect CVE-2024-50302 in my Linux dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-50302 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2024-50302 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-50302 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-50302?

CVE-2024-50302 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2024-50302 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-50302 (Linux Kernel Use of Uninitialized Resource Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-03-04. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-03-25. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-50302?

CVE-2024-50302 is classified as CWE-908 (CWE-908). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-50302 published, and has it been updated?

CVE-2024-50302 was published on November 19, 2024 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐧

🐧 Linux

CISA KEV · ACTIVELY EXPLOITED

MEDIUM severity

CVE-2024-50302 — Kernel

MEDIUM

CVE-2024-50302 is a medium-severity (CVSS 5.5) CWE-908 vulnerability in Kernel. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-03-04) — treat it as actively exploited and patch now. A fix is available for Kernel — see the affected versions and patch details below.

HID: core: zero-initialize the report buffer

Also known asA-380395346ASB-A-380395346

Published

Nov 19, 2024

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-03-04. Federal agencies were required to remediate by 2025-03-25.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-50302.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2024-50302 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐧Kernel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Linux packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐧Linux	`Kernel`	≥ 3.12.0&&< 4.19.324	4.19.324

Affected Products

5 products · 17 configurations

debian linuxdebian

1 version

11.0

androidgoogle

all

linux kernellinux

≥ 6.7 && < 6.11.8

1 version

6.12

simatic s7-1500 tm mfp firmwaresiemens

all

sinec ossiemens

< 3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Kernel to 4.19.324 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-50302 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

While this vulnerability could lead to disclosure of kernel memory, the impact is rated Moderate because exploitation requires bypassing additional security features such as kernel address-space layout randomization (KASLR). It could be exploited by an authenticated, local attacker who emulates a malicious Human…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2024-50302 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6 Extended Lifecycle Support - EXTENSION	`kernel-0:2.6.32-754.56.1.el6`	RHSA-2025:2517
Red Hat Enterprise Linux 7.7 Advanced Update Support	`kernel-0:3.10.0-1062.93.1.el7`	RHSA-2025:2514
Red Hat Enterprise Linux 7 Extended Lifecycle Support	`kernel-rt-0:3.10.0-1160.133.1.rt56.1285.el7`	RHSA-2025:2510
Red Hat Enterprise Linux 7 Extended Lifecycle Support	`kernel-0:3.10.0-1160.133.1.el7`	RHSA-2025:2501
Red Hat Enterprise Linux 8	`kernel-rt-0:4.18.0-553.44.1.rt7.385.el8_10`	RHSA-2025:2474
Red Hat Enterprise Linux 8	`kernel-0:4.18.0-553.44.1.el8_10`	RHSA-2025:2473
Red Hat Enterprise Linux 8.2 Advanced Update Support	`kernel-0:4.18.0-193.146.1.el8_2`	RHSA-2025:2646
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support	`kernel-0:4.18.0-305.151.1.el8_4`	RHSA-2025:2528

UbuntuMEDIUM

USN-7276-1Ubuntu USN-7277-1Ubuntu USN-7288-1Ubuntu USN-7289-1Ubuntu USN-7291-1Ubuntu USN-7288-2Ubuntu USN-7289-2Ubuntu USN-7293-1Ubuntu

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2024-50302 in your dependencies?

Find it across Linux, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-908CWE-908

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Nov 19, 2024

KEV added

Mar 4, 2025

Last updated

Oct 20, 2026

Identifiers

CVE-2024-50302

A-380395346

ASB-A-380395346

References

Advisorygithub.com Advisorynvd.nist.gov Webcert-portal.siemens.com Webcert-portal.siemens.com Webgit.kernel.org Webgit.kernel.org Webgit.kernel.org Webgit.kernel.org Webgit.kernel.org Webgit.kernel.org Webgit.kernel.org Webgit.kernel.org Weblists.debian.org Weblists.debian.org Webcisa.gov Packagegit.kernel.org

Related vulnerabilities

This CVE is medium severity; 6 of 8 other CVEs with CWE-908 are rated as high or higher (top: high).

CVE-2026-114501CVE-2026-112897CVE-2026-54500CVE-2026-45736CVE-2026-7141CVE-2026-34543CVE-2026-27496GHSA-fp5x-7m4q-449fBrowse all CWE-908

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2024-50302 — Kernel

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2024-50302 in your dependencies?