CriticalCVE-2026-72084

    Linux Kernel: Out-of-bounds Read (CVE-2026-72084)

    Published Last modified Sources: SUSE, Ubuntu, CVE.org, BSI

    Share

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: scsi: target: Bound PR-OUT TransportID parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move() hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with a further unbounded "%s").

    Update Linux Kernel to version 5.10.266, Linux Kernel to version 5.15.212, Linux Kernel to version 6.1.178.

    Affected
    • Linux Kernel lt 2.6.38..5.10.266
    • Linux Kernel lt 5.11..5.15.212
    • Linux Kernel lt 5.16..6.1.178
    • Linux Kernel lt 6.2..6.6.145
    • Linux Kernel lt 6.7..6.12.97
    • Linux Kernel lt 6.13..6.18.40
    • Linux Kernel lt 6.19..7.1.5
    Fixed in
    • Linux Kernel 5.10.266
    • Linux Kernel 5.15.212
    • Linux Kernel 6.1.178
    • Linux Kernel 6.6.145
    • Linux Kernel 6.12.97
    • Linux Kernel 6.18.40
    • Linux Kernel 7.1.5
    • Linux Kernel 7.2

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: SUSE, Ubuntu, CVE.org, BSI

    0.8 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 54.9

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    95.82 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.8 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    54.9
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 16 October 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-125

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    In the Linux kernel, the following vulnerability has been resolved: scsi: target: Bound PR-OUT TransportID parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move() hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with a further unbounded "%s"). An initiator can submit a TransportID whose iSCSI name contains neither a ",i,0x" substring nor a NUL terminator, filling the parameter list to its end, so the scan runs off the end of the buffer. When the parameter list spans more than one page the buffer is a multi-page vmap (transport_kmap_data_sg()), so the over-read walks into the trailing vmalloc guard page and oopses (KASAN: vmalloc-out-of-bounds in strstr). It is reachable by any fabric that delivers a PR OUT to a device exported through an iSCSI TPG, including a guest via vhost-scsi. Pass the number of received bytes down to the parser and validate the iSCSI TransportID's own self-described length (ADDITIONAL LENGTH + 4) once, up front: reject it if it is below the spc4r17 minimum or larger than the received buffer, then bound the separator search, the ISID walk and the name copy by that length. This is the length check the callers already perform after the parse (core_scsi3_decode_spec_i_port() compares tid_len against tpdl, core_scsi3_emulate_register_and_move() validates it against data_length), moved ahead of the scan. Also drop the unbounded "%s" of the unterminated name. Add per-format explicit name-length checks before copying into i_str, rather than silently truncating with min_t: for FORMAT CODE 00b reject if the descriptor body (tid_len - 4 bytes) cannot fit in i_str[TRANSPORT_IQN_LEN]; for FORMAT CODE 01b reject if the name portion (from &buf[4] up to the separator) cannot fit. Both checks make the bounds intent explicit at each format branch. While here, also reject a FORMAT CODE 01b TransportID whose ",i,0x" separator sits at the very end of the descriptor: that leaves an empty ISID and points the returned port nexus pointer at buf + tid_len, one past the descriptor, which the registration code (__core_scsi3_locate_pr_reg(), __core_scsi3_alloc_registration()) then dereferences as the ISID string -- the same over-read of the parameter buffer for a malformed descriptor.

    Source: suse_csaf, Ubuntu Security Notices, cvelistv5, NVD (NIST), BSI WID Portal, BSI CSAF

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 6.7 – < 6.12.97
    • 6.19 – < 7.1.5
    • 5.11 – < 5.15.212
    • 6.2 – < 6.6.145
    • 2.6.38 – < 5.10.266
    • —
    • 6.13 – < 6.18.40
    • 5.16 – < 6.1.178
    • 6.12.97
    • 7.1.5
    • 5.15.212
    • 6.6.145
    • 5.10.266
    • 7.2
    • 6.18.40
    • 6.1.178

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxubuntulinuxnoble
    Linuxubuntulinuxresolute
    Linuxubuntulinux-awsnoble
    Linuxubuntulinux-awsresolute
    Linuxubuntulinux-aws-7.0noble
    Linuxubuntulinux-aws-fipsnoble
    Linuxubuntulinux-azurenoble
    Linuxubuntulinux-azureresolute
    Linuxubuntulinux-azure-7.0noble
    Linuxubuntulinux-azure-fdenoble
    Linuxubuntulinux-azure-fderesolute
    Linuxubuntulinux-azure-fde-7.0noble
    Linuxubuntulinux-azure-fipsnoble
    Linuxubuntulinux-fipsnoble
    Linuxubuntulinux-gcpnoble
    Linuxubuntulinux-gcp-fipsnoble
    Linuxubuntulinux-gkenoble
    Linuxubuntulinux-gkeopnoble
    Linuxubuntulinux-hwe-7.0noble
    Linuxubuntulinux-ibmnoble
    Linuxubuntulinux-ibmresolute
    Linuxubuntulinux-lowlatencynoble
    Linuxubuntulinux-nvidiajammy
    Linuxubuntulinux-nvidia-tegrajammy

    Weakness classes (CWE)

    • CWE-125Out-of-bounds Read

      Base

      The product reads data past the end, or before the beginning, of the intended buffer.

      Entry at MITRE CWE-125

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      Weakness type: CWE-125

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Weakness type (CWE)added
      —
      CWE-125

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Record modifiedLinux

      Show 16 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/004ccd2d3b4ac36a300e05e01df152e5c02a5a82
      Referenceadded
      —
      https://git.kernel.org/stable/c/03fbc7de8d5e85fc8420e57e8304c855efd453ab
      Referenceadded
      —
      https://git.kernel.org/stable/c/555a89846ed888d7401b3f7200934c0fbedcbb46
      Referenceadded
      —
      https://git.kernel.org/stable/c/6ca5de8782e67573a61a6736b6dc0ffe58dcdf59
      Referenceadded
      —
      https://git.kernel.org/stable/c/842248047ef28dbf3b3f7f49a0ec315054d4dab8
      Referenceadded
      —
      https://git.kernel.org/stable/c/88c67c3de914e19172e1d878a7625c5b06c20ec5
      Referenceadded
      —
      https://git.kernel.org/stable/c/9298078a8f7d8181a04614a34ab655ccdf038204
      Referenceadded
      —
      https://git.kernel.org/stable/c/d04a179085c262c9ed577d0a4cbc6482ff1fd9a3
      Referenceremoved
      https://git.kernel.org/stable/c/004ccd2d3b4ac36a300e05e01df152e5c02a5a82
      —
      Referenceremoved
      https://git.kernel.org/stable/c/03fbc7de8d5e85fc8420e57e8304c855efd453ab
      —
      Referenceremoved
      https://git.kernel.org/stable/c/555a89846ed888d7401b3f7200934c0fbedcbb46
      —
      Referenceremoved
      https://git.kernel.org/stable/c/6ca5de8782e67573a61a6736b6dc0ffe58dcdf59
      —
      Referenceremoved
      https://git.kernel.org/stable/c/842248047ef28dbf3b3f7f49a0ec315054d4dab8
      —
      Referenceremoved
      https://git.kernel.org/stable/c/88c67c3de914e19172e1d878a7625c5b06c20ec5
      —
      Referenceremoved
      https://git.kernel.org/stable/c/9298078a8f7d8181a04614a34ab655ccdf038204
      —
      Referenceremoved
      https://git.kernel.org/stable/c/d04a179085c262c9ed577d0a4cbc6482ff1fd9a3
      —

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    3. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-72084","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-16T15:51:41.769272Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    4. Record modifiedLinux

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/88c67c3de914e19172e1d878a7625c5b06c20ec5
      Affected versions (publisher)changed
      Linux, Linux
      Linux, Linux

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    5. Record modifiedLinux

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
      Affected versions (publisher)changed
      Linux, Linux
      Linux, Linux

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Show one older change

    1. ReceivedLinux

      Description added or changed

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Linux, Linux
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: scsi: target: Bound PR-OUT TransportID parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move() hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id() locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with a further unbounded "%s"). An initiator can submit a TransportID whose iSCSI name contains neither a ",i,0x" substring nor a NUL terminator, filling the parameter list to its end, so the scan runs off the end of the buffer. When the parameter list spans more than one page the buffer is a multi-page vmap (transport_kmap_data_sg()), so the over-read walks into the trailing vmalloc guard page and oopses (KASAN: vmalloc-out-of-bounds in strstr). It is reachable by any fabric that delivers a PR OUT to a device exported through an iSCSI TPG, including a guest via vhost-scsi. Pass the number of received bytes down to the parser and validate the iSCSI TransportID's own self-described length (ADDITIONAL LENGTH + 4) once, up front: reject it if it is below the spc4r17 minimum or larger than the received buffer, then bound the separator search, the ISID walk and the name copy by that length. This is the length check the callers already perform after the parse (core_scsi3_decode_spec_i_port() compares tid_len against tpdl, core_scsi3_emulate_register_and_move() validates it against data_length), moved ahead of the scan. Also drop the unbounded "%s" of the unterminated name. Add per-format explicit name-length checks before copying into i_str, rather than silently truncating with min_t: for FORMAT CODE 00b reject if the descriptor body (tid_len - 4 bytes) cannot fit in i_str[TRANSPORT_IQN_LEN]; for FORMAT CODE 01b reject if the name portion (from &buf[4] up to the separator) cannot fit. Both checks make the bounds intent explicit at each format branch. While here, also reject a FORMAT CODE 01b TransportID whose ",i,0x" separator sits at the very end of the descriptor: that leaves an empty ISID and points the returned port nexus pointer at buf + tid_len, one past the descriptor, which the registration code (__core_scsi3_locate_pr_reg(), __core_scsi3_alloc_registration()) then dereferences as the ISID string -- the same over-read of the parameter buffer for a malformed descriptor.
      Referenceadded
      —
      https://git.kernel.org/stable/c/004ccd2d3b4ac36a300e05e01df152e5c02a5a82
      Referenceadded
      —
      https://git.kernel.org/stable/c/03fbc7de8d5e85fc8420e57e8304c855efd453ab
      Referenceadded
      —
      https://git.kernel.org/stable/c/555a89846ed888d7401b3f7200934c0fbedcbb46
      Referenceadded
      —
      https://git.kernel.org/stable/c/6ca5de8782e67573a61a6736b6dc0ffe58dcdf59
      Referenceadded
      —
      https://git.kernel.org/stable/c/842248047ef28dbf3b3f7f49a0ec315054d4dab8
      Referenceadded
      —
      https://git.kernel.org/stable/c/9298078a8f7d8181a04614a34ab655ccdf038204
      Referenceadded
      —
      https://git.kernel.org/stable/c/d04a179085c262c9ed577d0a4cbc6482ff1fd9a3

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-72084
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-72084"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-72084.svg?lang=en" alt="CVE-2026-72084 – NEOSEC Intel" height="20"></a>