# CVE-2026-43048: HID: core: Mitigate potential OOB by removing bogus memset()

> A flaw in the Linux kernel HID core allows out-of-bounds memory access via a bogus memset, potentially leading to code execution or system crashes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 May 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-85350, BELL-CVE-2026-43048, DEBIAN-CVE-2026-43048, GHSA-7r6r-545m-fqv3, ROOT-OS-DEBIAN-11-CVE-2026-43048, ROOT-OS-DEBIAN-12-CVE-2026-43048, ROOT-OS-DEBIAN-13-CVE-2026-43048, ROOT-OS-UBUNTU-2204-CVE-2026-43048, ROOT-OS-UBUNTU-2404-CVE-2026-43048, UBUNTU-CVE-2026-43048

## What is CVE-2026-43048?

CVE-2026-43048 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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]

Weakness: CWE-125 (Out-of-bounds Read), CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-43048?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-43048?

Apply the vendor's patch.

## Is CVE-2026-43048 being exploited?

There is no known exploitation of CVE-2026-43048 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43048 and fix it if it is affected.

What it is: CVE-2026-43048 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43048 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43048/ (Markdown: https://insights.sbomify.com/CVE-2026-43048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43048
- OSV: https://osv.dev/vulnerability/CVE-2026-43048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43048/
Summaries are generated and may contain mistakes; the official description above is the record.