Skip to content
major vulnerability· requires attention

Affects Linux kernel HID subsystem; widely deployed; could disrupt IT infrastructure.

Infrastructure

CVE-2026-43048

8.8
High
EPSS 0.24%Patch availableMay 3, 2026

Kernel HID OOB risk in report handling; fix removes memset.

common questions

Is CVE-2026-43048 being exploited?

Not confirmed. CVE-2026-43048 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-43048?

CVE-2026-43048 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-43048?

Yes. A fix has been recorded for CVE-2026-43048. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-43048 affect?

CVE-2026-43048 affects Linux kernel (HID subsystem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43048?

Apply kernel update containing HID fix

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (HID subsystem)
impact

Local attacker/process can trigger HID report OOB read/write, risking memory corruption or kernel crash.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= cd6104572bca9e4afe0dcdb8ecd65ef90b01297b and < 8f71034649738fdeb6859b8d6cddf132024fac06
  • affected>= cd6104572bca9e4afe0dcdb8ecd65ef90b01297b and < bd6e1d0230cca9575f5d118148f51e2a56b5373f
  • affected>= cd6104572bca9e4afe0dcdb8ecd65ef90b01297b and < 0a3fe972a7cb1404f693d6f1711f32bc1d244b1c
  • affected2.6.15
vendor says fixed in< 2.6.15, >= 6.18.22 and <= 6.18.*, >= 6.19.12 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free