IRONSMITHINTEL
MEDIUMCVSS5.5
|
Actively Exploited
|CISA KEV|CVE-2024-50302|Auth: low — authenticated user|Reboot: required|Manual only

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

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

Published Nov 19, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, with a low-privilege account, can achieve full data confidentiality loss. Federal agencies are required to remediate by 2025-03-25 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-908) (CWE-908) vulnerability in Linux Kernel. 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. Exploitation requires local access, low attack complexity, a low-privilege authenticated account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●IT Security
●Running android: -; debian linux: 11.0; simatic s7-1500 tm mfp firmware: -; sinec os: v < 3.2; linux kernel: 3.12 ≤ v < 4.19.324, 4.20 ≤ v < 5.4.286, 5.5 ≤ v < 5.10.230, 5.11 ≤ v < 5.15.172, 5.16 ≤ v < 6.1.117, 6.2 ≤ v < 6.6.61, 6.7 ≤ v < 6.11.8, 6.12
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-03-04 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-03-25.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2024-50302's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2024-50302↗ MSRC Advisory↗ NVD↗ Vendor Advisory