HID: core: Mitigate potential OOB by removing bogus memset()
CVE-2026-43048 · published 1 May 2026
How serious is it
- Severity: high, CVSS score 8.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-43048?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: cd6104572bca9e4afe0dcdb8ecd65ef90b01297b to < 218b93b7e284de1aa40a53f8f130f84f7da38858, cd6104572bca9e4afe0dcdb8ecd65ef90b01297b to < b37e6019fe420335d884e30535549a25f084e00d, cd6104572bca9e4afe0dcdb8ecd65ef90b01297b to < 8f71034649738fdeb6859b8d6cddf132024fac06, cd6104572bca9e4afe0dcdb8ecd65ef90b01297b to < bd6e1d0230cca9575f5d118148f51e2a56b5373f
- Linux Linux: 2.6.15
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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]
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/218b93b7e284de1aa40a53f8f130f84f7da38858
- git.kernel.org/stable/c/b37e6019fe420335d884e30535549a25f084e00d
- git.kernel.org/stable/c/8f71034649738fdeb6859b8d6cddf132024fac06
- git.kernel.org/stable/c/bd6e1d0230cca9575f5d118148f51e2a56b5373f
- git.kernel.org/stable/c/0a3fe972a7cb1404f693d6f1711f32bc1d244b1c
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON