CVE-2026-43048
What it is
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 <[email protected]> [bentiss: changed the return value]
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Linux Kernel < 6.18.22
- Linux Kernel < 6.19.12
- Linux Kernel 2.6.15
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43048.md and follow it. Check whether this project is affected by CVE-2026-43048. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0a3fe972a7cb1404f693d6f1711f32bc1d244b1c
- https://git.kernel.org/stable/c/8f71034649738fdeb6859b8d6cddf132024fac06
- https://git.kernel.org/stable/c/bd6e1d0230cca9575f5d118148f51e2a56b5373f
References
- https://git.kernel.org/stable/c/0a3fe972a7cb1404f693d6f1711f32bc1d244b1c
- https://git.kernel.org/stable/c/218b93b7e284de1aa40a53f8f130f84f7da38858
- https://git.kernel.org/stable/c/8f71034649738fdeb6859b8d6cddf132024fac06
- https://git.kernel.org/stable/c/ad4316edbc63949094edeee538517dd689df7b24
- https://git.kernel.org/stable/c/b37e6019fe420335d884e30535549a25f084e00d
- https://git.kernel.org/stable/c/bd6e1d0230cca9575f5d118148f51e2a56b5373f