Linux Kernel Use of Uninitialized Resource Vulnerability
Linux · Kernel
The Linux kernel's HID core, which handles Human Interface Device report processing, allocated its report buffer without zero-initialisation, so memory left over from earlier use could persist in it. A local user with low privileges and no user interaction could craft a specially designed HID report to read this residual kernel memory, potentially disclosing sensitive information.
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.
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 2/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 12 days before it was disclosed.
- First seen exploitedVulnCheck KEV evidence12 days before
- Disclosedday 0
- Added to CISA KEVEU database agrees+3 mo
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order 2CollectionTA0009
Attackers can use malicious Human Interface Devices (keyboard, mouse, etc.) to trigger a kernel-level memory leak due to improper initialization and use of uninitialized resources. This leads to the returning of the uninitialized kernel data, which can be collected and exfiltrated.
ExfiltrationTA0010
Lower-confidence links (1)
These come from early or generic mappings, text matching, or contradict this CVE’s details (for example a public-facing technique on a bug that needs a user to open a file). Shown for completeness.
- Replication Through Removable MediaT1091 Windows-only technique on a non-Windows product
Detection
0 rules for this CVE · 14 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2024-50302 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Data from Local SystemT100514 general rules
- OpenCanary - SMB File Open Requesthightest
- Potential Conti Ransomware Database Dumping Activity Via SQLCmdhightest
- SQLite Chromium Profile Data DB Accesshightest
- SQLite Firefox Profile Data DB Accesshightest
- VeeamBackup Database Credentials Dump Via Sqlcmd.EXEhightest
- Script Interpreter Spawning Credential Scanner - Linuxhighexperimental
- Script Interpreter Spawning Credential Scanner - Windowshighexperimental
- Shai-Hulud NPM Package Malicious Exfiltration via Curlhighexperimental
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 30, 202629 Oct 2026
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- 44 more on OTX