CVE-2025-39998High· 7.1▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: scsi: target: target_core_configfs: Add length check to avoid buffer overflow A buffer overflow arises from the usage of snprintf to write into the buffer "buf" in tar…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 39.1 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: target_core_configfs: Add length check to avoid buffer overflow
A buffer overflow arises from the usage of snprintf to write into the buffer "buf" in target_lu_gp_members_show function located in /drivers/target/target_core_configfs.c. This buffer is allocated with size LU_GROUP_NAME_BUF (256 bytes).
snprintf(...) formats multiple strings into buf with the HBA name (hba->hba_group.cg_item), a slash character, a devicename (dev-> dev_group.cg_item) and a newline character, the total formatted string length may exceed the buffer size of 256 bytes.
Since snprintf() returns the total number of bytes that would have been written (the length of %s/%sn ), this value may exceed the buffer length (256 bytes) passed to memcpy(), this will ultimately cause function memcpy reporting a buffer overflow error.
An additional check of the return value of snprintf() can avoid this buffer overflow.
Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < e6eeee5dc0d9221ff96d1b229b1d0222c8871b84Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 764a91e2fc9639e07aac93bc70e387e6b1e33084Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < ddc79fba132b807ff775467acceaf48b456e008bLinux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < e73fe0eefac3e15bf88fb5b4afae4c76215ee4d4Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < f03aa5e39da7d045615b3951d2a6ca1d7132f881Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 53c6351597e6a17ec6619f6f060d54128cb9a187Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 4b292286949588bd2818e66ff102db278de8dd26Linux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < a150275831b765b0f1de8b8ff52ec5c6933ac15dLinux >= c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 27e06650a5eafe832a90fd2604f0c5e920857faeLinux 2.6.38Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets