Linux Kernel up to 6.5.4 scsi lio_target_nacl_info_show buffer overflow

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.5.4. This affects the function lio_target_nacl_info_show of the component scsi. The manipulation leads to buffer overflow.
This vulnerability is documented as CVE-2023-53676. There is not any exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.5.4 and classified as critical. This issue affects the function lio_target_nacl_info_show of the component scsi. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-53676 since 10/07/2025. The exploitation is known to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/01/2026).
The vulnerability scanner Nessus provides a plugin with the ID 279063 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:4422-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.14.326, 4.19.295, 5.4.257, 5.10.197, 5.15.133, 6.1.55 or 6.5.5 eliminates this vulnerability. Applying the patch df349e84c2cb0dd05d98c8e1189c26ab4b116083/114b44dddea1f8f99576de3c0e6e9059012002fc/2cbe6a88fbdd6e8aeab358eef61472e2de43d6f6/bbe3ff47bf09db8956bc2eeb49d2d514d256ad2a/5353df78c22623b42a71d51226d228a8413097e2/4738bf8b2d3635c2944b81b2a84d97b8c8b0978d/0cac6cbb9908309352a5d30c1876882771d3da50/801f287c93ff95582b0a2d2163f12870a2f076d4 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (279063), EUVD (EUVD-2025-31973) and CERT Bund (WID-SEC-2025-2229). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- RESF Rocky Linux
- Open Source Linux Kernel
- IBM QRadar SIEM
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 4.14.325
- 4.19.294
- 5.4.256
- 5.10.196
- 5.15.132
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.1.28
- 6.1.29
- 6.1.30
- 6.1.31
- 6.1.32
- 6.1.33
- 6.1.34
- 6.1.35
- 6.1.36
- 6.1.37
- 6.1.38
- 6.1.39
- 6.1.40
- 6.1.41
- 6.1.42
- 6.1.43
- 6.1.44
- 6.1.45
- 6.1.46
- 6.1.47
- 6.1.48
- 6.1.49
- 6.1.50
- 6.1.51
- 6.1.52
- 6.1.53
- 6.1.54
- 6.5.0
- 6.5.1
- 6.5.2
- 6.5.3
- 6.5.4
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 279063
Nessus Name: SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:4422-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.14.326/4.19.295/5.4.257/5.10.197/5.15.133/6.1.55/6.5.5
Patch: df349e84c2cb0dd05d98c8e1189c26ab4b116083/114b44dddea1f8f99576de3c0e6e9059012002fc/2cbe6a88fbdd6e8aeab358eef61472e2de43d6f6/bbe3ff47bf09db8956bc2eeb49d2d514d256ad2a/5353df78c22623b42a71d51226d228a8413097e2/4738bf8b2d3635c2944b81b2a84d97b8c8b0978d/0cac6cbb9908309352a5d30c1876882771d3da50/801f287c93ff95582b0a2d2163f12870a2f076d4
Timeline
10/07/2025 Advisory disclosed10/07/2025 CVE reserved
10/07/2025 VulDB entry created
03/01/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53676 (🔒)
GCVE (CVE): GCVE-0-2023-53676
GCVE (VulDB): GCVE-100-327461
EUVD: 🔒
CERT Bund: WID-SEC-2025-2229 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 10/07/2025 19:20Updated: 03/01/2026 13:14
Changes: 10/07/2025 19:20 (59), 11/23/2025 06:01 (7), 12/19/2025 03:01 (2), 12/26/2025 02:15 (1), 02/03/2026 20:58 (11), 02/04/2026 05:47 (1), 03/01/2026 13:14 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.