CVE-2024-50302VulnerabilityPublished 10 Mar 2025Updated 1 Sep 2026

Red Hat Security Advisory: kernel security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

Exploited in the wild · KEV due 25 Mar 2025 : upgrade to 8.10 now.

Data as of 26 Oct 2026, 06:26 UTC

Exploitation

Actively exploited

High severity · No CVSS score from NVD or the CNA

KEV deadline: 25 Mar 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.10

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 10 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 6 days before disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

Added to CISA KEV (opens in a new tab)
exploitation confirmed
2025-03-04, 6 days before disclosure
CVE published
on cve.org
2025-03-1001:37Z, t = 0
KEV remediation due
US federal deadline
2025-03-25, 15 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redhat/kernel to 8.10.

Affected software

Product	Affected	Fixed in
Red Hatredhat/kernel`pkg:rpm/redhat/kernel`Other threats	Affected =8.* <8.10	Fixed in 8.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Red Hat has issued a security advisory for multiple vulnerabilities in the Linux kernel packages included in Red Hat Enterprise Linux 8. These vulnerabilities include a zero-initialization issue in the HID core (CVE-2024-50302), potential out-of-bound accesses in ALSA usb-audio drivers (CVE-2024-53197), a potential deadlock in the megaraid_sas SCSI driver (CVE-2024-57807), and a use-after-free in the pps subsystem (CVE-2024-57979). The update addresses these issues and requires a system reboot to take effect. The advisory rates the security impact as Important (high severity).

Impact

The vulnerabilities affect the Linux kernel core and several subsystems, potentially leading to memory safety issues such as out-of-bound accesses, use-after-free, and deadlocks. These could impact system stability and security if exploited. The advisory classifies the overall impact as Important, indicating a high severity level but does not provide specific CVSS scores or known exploit activity.

Mitigation

A security update for the kernel packages is available from Red Hat and should be applied promptly. The update includes fixes for all listed vulnerabilities. Systems must be rebooted after applying the update for the changes to take effect. Refer to Red Hat's official advisory and update instructions at https://access.redhat.com/articles/11258 for detailed guidance.

CWE-908Use of Uninitialized Resource (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses or accesses a resource that has not been initialized.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #11
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.1 (opens in a new tab)
V14.1.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-667Improper Locking (opens in a new tab)
Class weakness
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Implementation · Libraries or Frameworks
Use industry standard APIs to implement locking mechanism.
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Forced Deadlock (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Sep 2026, 22:31 UTC

WeaknessesCWE-908, CWE-120, CWE-667

Technical details

References

Community reviews

Related threats