Skip to main content

Linux Kernel CVE-2026-43048

| EUVDEUVD-2026-26647 HIGH
Out-of-bounds Read (CWE-125)
2026-05-01 Linux
8.8
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Deploy malicious HID device
  2. Delivery
    Establish USB/Bluetooth connection
  3. Exploit
    Send undersized HID report
  4. Install
    Trigger memset() OOB write
  5. C2
    Corrupt kernel memory structures
  6. Execute
    Execute arbitrary kernel code
  7. Impact
    Achieve full system compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires adjacent network access to deploy malicious HID-compliant devices (USB peripherals, Bluetooth keyboards/mice, or other HID-over-transport implementations). Attacker must have physical proximity to connect rogue USB devices or establish Bluetooth pairing, or must have already compromised a device on the local network segment capable of emulating HID devices. Exploitation targets the kernel's HID event processing path, which runs for any recognized HID device regardless of user-space permissions. No special kernel configuration required - default CONFIG_HID and CONFIG_USB_HID or CONFIG_BT_HIDP compilation settings are sufficient. Vulnerability triggers when HID devices send input reports smaller than the kernel's expected report structure size, a condition trivially achievable with custom device firmware. No user interaction required beyond the physical connection event (UI:N). Systems without USB/Bluetooth HID support compiled into the kernel, or those with HID subsystem disabled via boot parameters, are not affected.

Impact

Real-world risk is moderate despite the 8.8 CVSS score. The AV:A (adjacent network) vector limits exploitation to attackers with physical proximity or those who have already compromised devices on the same network segment, such as rogue USB/Bluetooth HID peripherals or compromised devices masquerading as HID controllers. Attack complexity is low (AC:L) with no authentication required (PR:N), making exploitation straightforward once adjacent access is achieved. EPSS score of 0.02% (4th percentile) indicates minimal observed exploitation in the wild, likely because adjacent access prerequisite naturally limits attack surface. The high impact ratings (C:H/I:H/A:H) reflect kernel-level compromise potential - successful exploitation could lead to arbitrary code execution in kernel context. Primary risk scenarios include supply-chain attacks via malicious USB devices, evil-maid attacks with crafted HID peripherals, or lateral movement in already-compromised networks. Patches available across multiple stable kernel branches significantly reduce urgency for patched systems. Organizations should prioritize patching on systems regularly exposed to untrusted HID devices (public kiosks, shared workstations, IoT gateways) over isolated servers without physical peripheral access.

Exploit ScenarioDerived

An attacker deploys a malicious USB device disguised as a keyboard to a target workstation running vulnerable kernel versions. When connected, the device sends a crafted HID input report with a buffer size smaller than the expected report structure. The undersized buffer triggers the vulnerable memset() in hid_report_raw_event(), causing an out-of-bounds write that corrupts adjacent kernel memory. The attacker leverages this memory corruption to overwrite function pointers or other critical kernel structures, achieving arbitrary code execution with kernel privileges. Publicly available exploit code exists per input data, lowering the technical barrier for exploitation beyond proof-of-concept.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 03, 2026

Adjacent network attackers can achieve high-severity code execution, information disclosure, or denial of service in the Linux kernel HID (Human Interface Device) subsystem by exploiting a bounds-checking flaw in hid_report_raw_event(). A bogus memset() operation intended to zero unused buffer space instead creates out-of-bounds read/write conditions when processing malformed HID input reports from adjacent devices (USB, Bluetooth). Vendor patches available for stable branches 6.18.22, 6.19.12, and 7.0. EPSS score of 0.02% suggests minimal observed exploitation, but the unauthenticated adjacent-network attack vector with low complexity makes this exploitable in environments with untrusted HID peripherals.

RemediationAI

Upgrade to patched kernel versions: mainline 7.0 or later, stable branch 6.19.12 or later, or LTS branch 6.18.22 or later depending on your distribution's kernel series. Distribution-specific packages should be applied via normal update channels (apt, yum, dnf) rather than compiling upstream kernels directly. For Red Hat/CentOS/Fedora users, monitor RHSA advisories; for Debian/Ubuntu, check USN notices; for SUSE, review SUSE-SU advisories. If immediate patching is not feasible, implement defense-in-depth controls: disable unused HID drivers via kernel module blacklisting (modprobe.d configuration for hid-generic, usbhid if USB HID not required), restrict physical access to USB/Bluetooth ports on critical systems, employ USB device whitelisting via USBGuard or similar tools to block unauthorized HID peripherals, and enable kernel hardening features like CONFIG_FORTIFY_SOURCE and CONFIG_HARDENED_USERCOPY if not already active. Note that disabling HID entirely breaks keyboard/mouse functionality on workstations, making this mitigation viable only for headless servers. Bluetooth-based exploitation can be mitigated by disabling Bluetooth (systemctl disable bluetooth) on systems not requiring wireless peripherals, though this impacts usability. Reference advisory at https://vuldb.com/vuln/360720 for additional context.

Affected VersionsENISA

Linux patch: 7.0
Linux patch: 6.19.12
Linux patch: 6.18.22
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0a3fe972a7cb1404f693d6f1711f32bc1d244b1c
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8f71034649738fdeb6859b8d6cddf132024fac06
Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd6e1d0230cca9575f5d118148f51e2a56b5373f

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The HID subsystem (drivers/hid/hid-core.c) processes input reports from human interface devices like keyboards, mice, and game controllers. The vulnerability exists in hid_report_raw_event(), which previously attempted to sanitize incoming event buffers by calling memset() to zero memory from the end of received data to the expected buffer end. When the incoming buffer size is smaller than the report structure expects, this memset() operation accesses memory beyond allocated bounds. The fix removes the unsafe memset() and adds early return validation to reject undersized buffers before processing. This prevents both out-of-bounds reads during the zeroing operation and subsequent OOB writes when the kernel processes the malformed report structure. The vulnerability affects the core HID infrastructure used across USB-HID, Bluetooth-HID, and other transport layers.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SUSE HIGH
Red Hat 5.5 MEDIUM

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
May 03, 2026 - 07:22 NVD
8.8 (HIGH)
Patch released
May 03, 2026 - 07:16 nvd
Patch available
Patch available
May 01, 2026 - 16:33 EUVD
CVE Published
May 01, 2026 - 14:15 nvd
HIGH 8.8

DescriptionCVE.org

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]

Executive ViewAI

Why It Matters

CVE-2026-43048 is a high-severity code execution vulnerability in the Linux kernel HID subsystem that allows adjacent network attackers to execute arbitrary code, disclose information, or crash systems through malformed USB or Bluetooth device input. Organizations running vulnerable Linux kernel versions face direct risk from untrusted or compromised peripheral devices connected to their endpoints and servers, requiring immediate patching to prevent potential lateral movement and data exfiltration.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is not feasible, disable or restrict access to untrusted USB and Bluetooth HID devices through device policies and physical access controls until patching is completed.

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: High
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy