Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74556scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer iscsi_tcp_hdr_dissect() receives the data segment of several PDU types into the fixed-size conn->data buffer, which is allocated for ISCSI_DEF_MAX_RECV_SEG_LEN (8192) bytes. For the LOGIN_RSP, TEXT_RSP, REJECT and ASYNC_EVENT opcodes the dissect path already rejects a PDU whose DataSegmentLength exceeds that buffer. The SCSI Command Response (ISCSI_OP_SCSI_CMD_RSP) path also copies its data segment (sense/response data) into conn->data via iscsi_tcp_data_recv_prep(), but it does so without the same check. The only upstream bound on in.datalen is conn->max_recv_dlength, the initiator's advertised MaxRecvDataSegmentLength, which is commonly negotiated well above 8192 (open-iscsi defaults to 262144). A target that returns a SCSI Response with a DataSegmentLength between 8193 and max_recv_dlength therefore overflows the 8192-byte conn->data buffer. Once the same bound applies, ISCSI_OP_SCSI_CMD_RSP is handled exactly like those responses: bound the data segment, receive it into conn->data when present, and otherwise complete the PDU with no data. Fold the opcode into that case group rather than duplicating the check.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74556, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.40% · top 65% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < a51812842084fd390590ab8dc0431f10c73ddc56
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < a8f94cc9f0e5759252551be3a172960c57f21f54
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < f1a3a51fc5dba0e99532379665069f1700da6b44
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < c97b5265cc47775f77fd2a23d6bde0426997b233
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < 084af0253673425ce2ae62e3c7f74f0dd023711b
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < 72815741715bd41556dac5eeb068bf0f8af06ee7
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676
    • affected a081c13e39b5c17052a7b46fafa61019c4c110ff – < c1dea15f819cded9b3faf58f8bec72323568b6e6
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74556 badge
[![CVE-2026-74556](https://cveledger.app/badge/CVE-2026-74556.svg)](https://cveledger.app/cve/CVE-2026-74556)

Record last updated .