# CVE-2025-68782: scsi: target: Reset t_task_cdb pointer in error case

> A null pointer dereference in the Linux kernel SCSI target subsystem can cause a system crash when command allocation fails.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-74363, BELL-CVE-2025-68782, DEBIAN-CVE-2025-68782, GHSA-r6v3-89j7-2957, ROOT-OS-UBUNTU-2204-CVE-2025-68782, ROOT-OS-UBUNTU-2404-CVE-2025-68782, UBUNTU-CVE-2025-68782

## What is CVE-2025-68782?

CVE-2025-68782 is a high-severity vulnerability in Linux, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

scsi: target: Reset t_task_cdb pointer in error case

If allocation of cmd->t_task_cdb fails, it remains NULL but is later
dereferenced in the 'err' path.

In case of error, reset NULL t_task_cdb value to point at the default
fixed-size buffer.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Apply the vendor's patch.

## Is CVE-2025-68782 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68782 is a high-severity vulnerability in Linux, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68782 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-68782/ (Markdown: https://insights.sbomify.com/CVE-2025-68782/index.md)
```

## Sources

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

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