# CVE-2026-46332: greybus: gb-beagleplay: bound bootloader receive buffering

> A buffer overflow in the Linux kernel greybus bootloader driver allows attackers to corrupt memory, potentially leading to code execution or system crashes.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-46332, DEBIAN-CVE-2026-46332, GHSA-hf99-m7vw-4p34, UBUNTU-CVE-2026-46332

## What is CVE-2026-46332?

CVE-2026-46332 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

greybus: gb-beagleplay: bound bootloader receive buffering

cc1352_bootloader_rx() appends each serdev chunk into the fixed
rx_buffer before parsing bootloader packets. The helper can keep
leftover bytes between callbacks and may receive multiple packets in one
callback, so a single count value is not constrained by one packet
length.

Check that the incoming chunk fits in the remaining receive buffer space
before memcpy(). If it does not, drop the staged data and consume the
bytes instead of overflowing rx_buffer.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-46332 being exploited?

There is no known exploitation of CVE-2026-46332 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-46332 and fix it if it is affected.

What it is: CVE-2026-46332 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-46332 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-46332/ (Markdown: https://insights.sbomify.com/CVE-2026-46332/index.md)
```

## Sources

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

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