CVE-2026-43048: HID: core: Mitigate potential OOB by removing bogus memset()
In the Linux kernel, the following vulnerability has been resolved:
HID: core: Mitigate potential OOB by removing bogus memset()
The memset() in hid_report_raw_event() has the good intention of
clearing out bogus data by zeroing the area from the end of the incoming
data string to the assumed end of the buffer. However, as we have
previously seen, doing so can easily result in OOB reads and writes in
the subsequent thread of execution.
The current suggestion from one of the HID maintainers is to remove the
memset() and simply return if the incoming event buffer size is not
large enough to fill the associated report.
Suggested-by Benjamin Tissoires <bentiss@kernel.org>
[bentiss: changed the return value]
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s HID event handling could corrupt or expose memory when a malformed device report is shorter than expected. The supplied CVSS score is 8.8, reflecting possible confidentiality, integrity, and availability impact without privileges or user interaction, but requiring adjacent access.
Executive priority
Treat as a high-priority kernel update for endpoints or systems able to receive untrusted HID input. The technical impact is serious, but the adjacent-access requirement and absence of cited active exploitation reduce immediate enterprise-wide urgency. Use accelerated, risk-based patching rather than emergency incident response solely from this evidence.
Technical view
hid_report_raw_event() attempted to clear trailing report data with memset(). The supplied description warns that this could cause out-of-bounds reads and writes later in execution. The kernel fix removes that memset() and rejects incoming event buffers too small for the associated HID report.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions that process attacker-controlled or malformed HID reports. The supplied version metadata names 2.6.15, 0, 6.18.22, 6.19.12, and 7.0 as affected, but does not provide clear range semantics. Confirm status with the distribution vendor.
Exploitation context
The CVSS vector classifies access as adjacent, with low complexity, no privileges, and no user interaction. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public proof-of-concept availability, or observed attacks.
Researcher notes
No CWE is assigned in the supplied record. The described condition involves potential out-of-bounds reads and writes caused by clearing memory beyond assumptions about an undersized report. Three Linux stable commits are cited, but the bundle does not map each commit to a specific maintained branch or provide exploitability details beyond CVSS.
Mitigation direction
Install a vendor-supported kernel containing the referenced stable fix.
Check distribution advisories for exact affected and corrected package versions.
Prioritize systems exposed to untrusted or physically accessible HID devices.
Restrict untrusted HID device access where updating cannot occur promptly.
Validation and detection
Record each system’s running kernel version and distribution package release.
Compare versions against current distribution or Linux stable guidance.
Confirm the installed kernel includes one applicable referenced fix commit.
Reboot after updating and verify the corrected kernel is running.
Review kernel logs for abnormal HID processing or memory-fault events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43048 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.