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-90011scsi: target: iscsi: Reserve a terminator byte for the login payload

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Reserve a terminator byte for the login payload iscsi_target_check_login_request() rejects a login PDU whose DataSegmentLength exceeds MAX_KEY_VALUE_PAIRS, but the test is '>' and login->req_buf is allocated with exactly MAX_KEY_VALUE_PAIRS bytes. Since iscsit_get_login_rx() receives payload_length + padding bytes, where padding = ((-payload_length) & 3); any payload_length from 8189 to 8192 fills the whole 8192 byte buffer. The write stays in bounds, but no byte is left for a NUL terminator. The buffer is subsequently consumed as a C string. In the CHAP path chap_check_algorithm() calls kstrdup(a_str), and extract_param() calls strstr(in_buf, pattern) followed by strlen_semi(), none of which take a length. convert_null_to_semi() additionally rewrites every embedded NUL to ';', so even a payload made of well formed NUL separated key=value records is left without a terminator. These walk past the end of the object into adjacent slab memory. It is reachable by an unauthenticated initiator against a portal configured for CHAP; when authentication is not required iscsi_login_zero_tsih_s2() rewrites AuthMethod to None and the CHAP path is never entered. Allocate one extra byte. kzalloc() zeroes it and nothing ever writes to it, as every writer copies to offset 0 for at most MAX_KEY_VALUE_PAIRS bytes, so the buffer is always terminated.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days 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-90011, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Received3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.84% · top 42% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < 5fac79f248c37774d1dd761406f83d25ca6ff8e4
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < 6ddddcad436d8e6e619204d3c848147ff2f5bf1e
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < b19dc17ed963ac36c0db4b52a1803fb11169f91f
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < 6b589ef9d5f6cdc70d2b4f269ca6cf26b5ebb076
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < eb9dadf4d552ebe10644871c5189286552aa48f5
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < 1624bff4c5118ad494d50ad94d44f22064667a7f
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < 3ddf3ea291a0ef2ea93b82e158960ac2cc42302b
    • affected e48354ce078c079996f89d715dfa44814b4eba01 – < f4825922d2fb371e2b969697d792077f1b62b62c
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .