# CVE-2026-46149: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show()

> A local attacker can read adjacent stack memory or trigger a kernel panic via a long iSCSI IQN in the Linux kernel SCSI target subsystem.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 28 May 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-89064, BELL-CVE-2026-46149, DEBIAN-CVE-2026-46149, GHSA-vvx9-xfcg-g62v, ROOT-OS-DEBIAN-11-CVE-2026-46149, ROOT-OS-DEBIAN-12-CVE-2026-46149, ROOT-OS-UBUNTU-2204-CVE-2026-46149, ROOT-OS-UBUNTU-2404-CVE-2026-46149, UBUNTU-CVE-2026-46149

## What is CVE-2026-46149?

CVE-2026-46149 is a high-severity vulnerability in Linux kernel, published on 28 May 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:

scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show()

target_tg_pt_gp_members_show() formats LUN paths with snprintf() into a
256-byte stack buffer, then will memcpy() cur_len bytes from that
buffer.  snprintf() returns the length the output would have had, which
can exceed the buffer size when the fabric WWN is long because iSCSI IQN
names can be up to 223 bytes.  The check at the memcpy() site only
guards the destination page write, not the source read, so memcpy() will
read past the stack buffer and copy adjacent stack contents to the sysfs
reader, which when CONFIG_FORTIFY_SOURCE is enabled, fortify_panic()
will be triggered.

Commit 27e06650a5ea ("scsi: target: target_core_configfs: Add length
check to avoid buffer overflow") added the same bound to the
target_lu_gp_members_show() but the tg_pt_gp variant was missed so
resolve that here.

Weakness: CWE-674 (Uncontrolled Recursion), CWE-126 (Buffer Over-read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-46149 being exploited?

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

What it is: CVE-2026-46149 is a high-severity vulnerability in Linux kernel, published on 28 May 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-46149 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-46149/ (Markdown: https://insights.sbomify.com/CVE-2026-46149/index.md)
```

## Sources

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

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