# CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()

> A buffer overflow in the Linux kernel iSCSI target allows attackers to corrupt memory, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Oct 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-53676, DEBIAN-CVE-2023-53676, GHSA-4832-crwv-4gfx, SUSE-SU-2025:4507-1, UBUNTU-CVE-2023-53676

## What is CVE-2023-53676?

CVE-2023-53676 is a high-severity memory corruption vulnerability in Linux kernel, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()

The function lio_target_nacl_info_show() uses sprintf() in a loop to print
details for every iSCSI connection in a session without checking for the
buffer length. With enough iSCSI connections it's possible to overflow the
buffer provided by configfs and corrupt the memory.

This patch replaces sprintf() with sysfs_emit_at() that checks for buffer
boundries.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-53676?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-default` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |
| `kernel-docs` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |
| `kernel-ec2` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |
| `kernel-source` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |
| `kernel-syms` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |
| `kernel-trace` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |
| `kernel-xen` | SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | All versions | 3.0.101-108.195.1 |

Products: Linux kernel.

## How do I fix CVE-2023-53676?

Apply the vendor's patch.

## Is CVE-2023-53676 being exploited?

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

What it is: CVE-2023-53676 is a high-severity memory corruption vulnerability in Linux kernel, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-53676 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-2023-53676/ (Markdown: https://insights.sbomify.com/CVE-2023-53676/index.md)
```

## Sources

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

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