# CVE-2026-72352: HID: bpf: Fix hid_bpf_get_data() range check

> An integer overflow in the Linux kernel HID-BPF subsystem allows out-of-bounds memory access, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-72352, DEBIAN-CVE-2026-72352, GHSA-p43j-9ghf-j8hh, UBUNTU-CVE-2026-72352

## What is CVE-2026-72352?

CVE-2026-72352 is a high-severity vulnerability in Linux, published on 15 Aug 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: bpf: Fix hid_bpf_get_data() range check

hid_bpf_get_data() returns a pointer into the HID-BPF context data when
the caller-provided offset and size fit inside ctx->allocated_size.

The current check adds rdwr_buf_size and offset before comparing the
result against ctx->allocated_size. Since both values are unsigned, a
very large size can wrap the sum below ctx->allocated_size and make the
helper return a pointer even though the requested range is not contained
in the backing buffer.

Use check_add_overflow() to reject wrapped range ends before comparing
the requested range end against ctx->allocated_size.

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


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

Apply the vendor's patch.

## Is CVE-2026-72352 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72352 is a high-severity vulnerability in Linux, published on 15 Aug 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-72352 in the wild and no public exploit code.

Affected product: Linux. 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-72352/ (Markdown: https://insights.sbomify.com/CVE-2026-72352/index.md)
```

## Sources

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

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