# CVE-2025-40345: usb: storage: sddr55: Reject out-of-bound new_pba

> A malicious USB device can trigger heap memory corruption in the Linux kernel sddr55 driver, potentially leading to code execution or system crash.

- **Severity:** Not scored
- **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:** 12 Dec 2025
- **Updated:** 2 Jun 2026
- **Also known as:** AZL-72332, BELL-CVE-2025-40345, DEBIAN-CVE-2025-40345, GHSA-9r78-47qh-www2, ROOT-OS-DEBIAN-12-CVE-2025-40345, ROOT-OS-DEBIAN-13-CVE-2025-40345, ROOT-OS-UBUNTU-2204-CVE-2025-40345, ROOT-OS-UBUNTU-2404-CVE-2025-40345, UBUNTU-CVE-2025-40345

## What is CVE-2025-40345?

CVE-2025-40345 is a memory corruption vulnerability in Linux, published on 12 Dec 2025. 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:

usb: storage: sddr55: Reject out-of-bound new_pba

Discovered by Atuin - Automated Vulnerability Discovery Engine.

new_pba comes from the status packet returned after each write.
A bogus device could report values beyond the block count derived
from info->capacity, letting the driver walk off the end of
pba_to_lba[] and corrupt heap memory.

Reject PBAs that exceed the computed block count and fail the
transfer so we avoid touching out-of-range mapping entries.

## Which versions are affected by CVE-2025-40345?


## How do I fix CVE-2025-40345?

Apply the vendor's patch.

## Is CVE-2025-40345 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40345 and fix it if it is affected.

What it is: CVE-2025-40345 is a memory corruption vulnerability in Linux, published on 12 Dec 2025. 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-2025-40345 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-2025-40345/ (Markdown: https://insights.sbomify.com/CVE-2025-40345/index.md)
```

## Sources

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

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