# CVE-2025-68229: scsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()

> A local attacker can trigger a kernel crash via a null pointer dereference in the tcm_loop SCSI target module when reading configfs attributes.

- **Severity:** Not scored
- **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:** 16 Dec 2025
- **Updated:** 16 Jun 2026
- **Also known as:** AZL-72466, BELL-CVE-2025-68229, DEBIAN-CVE-2025-68229, GHSA-984g-3ggq-r83h, ROOT-OS-DEBIAN-12-CVE-2025-68229, ROOT-OS-DEBIAN-13-CVE-2025-68229, ROOT-OS-UBUNTU-2204-CVE-2025-68229, ROOT-OS-UBUNTU-2404-CVE-2025-68229, UBUNTU-CVE-2025-68229

## What is CVE-2025-68229?

CVE-2025-68229 is a vulnerability in Linux, published on 16 Dec 2025. 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:

scsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()

If the allocation of tl_hba->sh fails in tcm_loop_driver_probe() and we
attempt to dereference it in tcm_loop_tpg_address_show() we will get a
segfault, see below for an example. So, check tl_hba->sh before
dereferencing it.

  Unable to allocate struct scsi_host
  BUG: kernel NULL pointer dereference, address: 0000000000000194
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x0000) - not-present page
  PGD 0 P4D 0
  Oops: 0000 [#1] PREEMPT SMP NOPTI
  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1
  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024
  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]
...
  Call Trace:
   <TASK>
   configfs_read_iter+0x12d/0x1d0 [configfs]
   vfs_read+0x1b5/0x300
   ksys_read+0x6f/0xf0
...

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


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

Apply the vendor's patch.

## Is CVE-2025-68229 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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