BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-72084High confidence

scsi: target: Bound PR-OUT TransportID parsing to the received buffer

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 280 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.74% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 280 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-72084 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-72084
204 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-72084 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: scsi: target: Bound PR-OUT TransportID parsing to the received buffer
260 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's SCSI target subsystem. An attacker, by submitting a specially crafted iSCSI TransportID during a PERSISTENT RESERVE OUT operation, could cause an out-of-bounds read. This vulnerability, which occurs due to unbounded parsing of the TransportID, can lead to a system crash, resulting in a Denial of Service (DoS). This can be exploited by a remote attacker or a guest in a virtualized environment.
Remediation
To mitigate this issue, prevent module iscsi_target_mod from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-59042

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 280 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-59042Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2852Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-72014 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72033 https://www.cve.org/CVERecord?id=CVE-2026-72033 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72064 https://www.cve.org/CVERecord?id=CVE-2026-72064 Référence CVE CVE-2026-72065 https://www.cve.org/CVERecord?id=CVE-2026-72065 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72085 https://www.cve.org/CVERecord?id=CVE-2026-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72139 https://www.cve.org/CVERecord?id=CVE-2026-72139 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-72051 Référence CVE CVE-2026-72052 https://www.cve.org/CVERecord?id=CVE-2026-72052 Référence CVE CVE-2026-72053 https://www.cve.org/CVERecord?id=CVE-2026-72053 Référence CVE CVE-2026-72054 https://www.cve.org/CVERecord?id=CVE-2026-72054 Référence CVE CVE-2026-72055 https://www.cve.org/CVERecord?id=CVE-2026-72055 Référence CVE CVE-2026-72061 https://www.cve.org/CVERecord?id=CVE-2026-72061 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72072 https://www.cve.org/CVERecord?id=CVE-2026-72072 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72100 https://www.cve.org/CVERecord?id=CVE-2026-72100 Référence CVE CVE-2026-72101 https://www.cve.org/CVERecord?id=CVE-2026-72101 Référence CVE CVE-2026-72103 https://www.cve.org/CVERecord?id=CVE-2026-72103 Référence CVE CVE-2026-72106 https://www.cve.org/CVERecord?id=CVE-2026-72106 Référence CVE CVE-2026-72107 https://www.cve.org/CVERecord?id=CVE-2026-72107 Référence CVE CVE-2026-72108 https://www.cve.org/CVERecord?id=CVE-2026-72108 Référence CVE CVE-2026-72132 https://www.cve.org/CVERecord?id=CVE-2026-72132 Référence CVE CVE-2026-72136 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-72014 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72033 https://www.cve.org/CVERecord?id=CVE-2026-72033 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72064 https://www.cve.org/CVERecord?id=CVE-2026-72064 Référence CVE CVE-2026-72065 https://www.cve.org/CVERecord?id=CVE-2026-72065 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72085 https://www.cve.org/CVERecord?id=CVE-2026-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=CVE-2026-72130 Référence CVE CVE-2026-72137 https://www.cve.org/CVERecord?id=CVE-2026-72137 Référence CVE CVE-2026-72139 https://www.cve.org/CVERecord?id=CVE-2026-72139 Référence CVE CVE-2026-72191 https://www.cve.org/CVERecord?id=CVE-2026-72191 Référence CVE CVE-2026-72192 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1231Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68433 Référence CVE CVE-2026-68450 https://www.cve.org/CVERecord?id=CVE-2026-68450 Référence CVE CVE-2026-68480 https://www.cve.org/CVERecord?id=CVE-2026-68480 Référence CVE CVE-2026-72017 https://www.cve.org/CVERecord?id=CVE-2026-72017 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72036 https://www.cve.org/CVERecord?id=CVE-2026-72036 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72072 https://www.cve.org/CVERecord?id=CVE-2026-72072 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72086 https://www.cve.org/CVERecord?id=CVE-2026-72086 Référence CVE CVE-2026-72108 https://www.cve.org/CVERecord?id=CVE-2026-72108 Référence CVE CVE-2026-72123 https://www.cve.org/CVERecord?id=CVE-2026-72123 Référence CVE CVE-2026-72135 https://www.cve.org/CVERecord?id=CVE-2026-72135 Référence CVE CVE-2026-72138 https://www.cve.org/CVERecord?id=CVE-2026-72138 Référence CVE CVE-2026-72142 https://www.cve.org/CVERecord?id=CVE-2026-72142 Référence CVE CVE-2026-72164 https://www.cve.org/CVERecord?id=CVE-2026-72164 Référence CVE CVE-2026-72251 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68480 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72032 https://www.cve.org/CVERecord?id=CVE-2026-72032 Référence CVE CVE-2026-72035 https://www.cve.org/CVERecord?id=CVE-2026-72035 Référence CVE CVE-2026-72036 https://www.cve.org/CVERecord?id=CVE-2026-72036 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72072 https://www.cve.org/CVERecord?id=CVE-2026-72072 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72123 https://www.cve.org/CVERecord?id=CVE-2026-72123 Référence CVE CVE-2026-72132 https://www.cve.org/CVERecord?id=CVE-2026-72132 Référence CVE CVE-2026-72221 https://www.cve.org/CVERecord?id=CVE-2026-72221 Référence CVE CVE-2026-72222 https://www.cve.org/CVERecord?id=CVE-2026-72222 Référence CVE CVE-2026-72251 https://www.cve.org/CVERecord?id=CVE-2026-72251 Référence CVE CVE-2026-72254 https://www.cve.org/CVERecord?id=CVE-2026-72254 Référence CVE CVE-2026-72262 https://www.cve.org/CVERecord?id=CVE-2026-72262 Référence CVE CVE-2026-72288 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-68477 Référence CVE CVE-2026-72014 https://www.cve.org/CVERecord?id=CVE-2026-72014 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72033 https://www.cve.org/CVERecord?id=CVE-2026-72033 Référence CVE CVE-2026-72041 https://www.cve.org/CVERecord?id=CVE-2026-72041 Référence CVE CVE-2026-72065 https://www.cve.org/CVERecord?id=CVE-2026-72065 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72071 https://www.cve.org/CVERecord?id=CVE-2026-72071 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72085 https://www.cve.org/CVERecord?id=CVE-2026-72085 Référence CVE CVE-2026-72098 https://www.cve.org/CVERecord?id=CVE-2026-72098 Référence CVE CVE-2026-72111 https://www.cve.org/CVERecord?id=CVE-2026-72111 Référence CVE CVE-2026-72124 https://www.cve.org/CVERecord?id=CVE-2026-72124 Référence CVE CVE-2026-72125 https://www.cve.org/CVERecord?id=CVE-2026-72125 Référence CVE CVE-2026-72126 https://www.cve.org/CVERecord?id=CVE-2026-72126 Référence CVE CVE-2026-72129 https://www.cve.org/CVERecord?id=CVE-2026-72129 Référence CVE CVE-2026-72130 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68480 Référence CVE CVE-2026-72020 https://www.cve.org/CVERecord?id=CVE-2026-72020 Référence CVE CVE-2026-72032 https://www.cve.org/CVERecord?id=CVE-2026-72032 Référence CVE CVE-2026-72035 https://www.cve.org/CVERecord?id=CVE-2026-72035 Référence CVE CVE-2026-72036 https://www.cve.org/CVERecord?id=CVE-2026-72036 Référence CVE CVE-2026-72046 https://www.cve.org/CVERecord?id=CVE-2026-72046 Référence CVE CVE-2026-72069 https://www.cve.org/CVERecord?id=CVE-2026-72069 Référence CVE CVE-2026-72072 https://www.cve.org/CVERecord?id=CVE-2026-72072 Référence CVE CVE-2026-72083 https://www.cve.org/CVERecord?id=CVE-2026-72083 Référence CVE CVE-2026-72084 https://www.cve.org/CVERecord?id=CVE-2026-72084 Référence CVE CVE-2026-72123 https://www.cve.org/CVERecord?id=CVE-2026-72123 Référence CVE CVE-2026-72132 https://www.cve.org/CVERecord?id=CVE-2026-72132 Référence CVE CVE-2026-72221 https://www.cve.org/CVERecord?id=CVE-2026-72221 Référence CVE CVE-2026-72222 https://www.cve.org/CVERecord?id=CVE-2026-72222 Référence CVE CVE-2026-72251 https://www.cve.org/CVERecord?id=CVE-2026-72251 Référence CVE CVE-2026-72254 https://www.cve.org/CVERecord?id=CVE-2026-72254 Référence CVE CVE-2026-72262 https://www.cve.org/CVERecord?id=CVE-2026-72262 Référence CVE CVE-2026-72288 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.38, 5.10.266 ≤ 5.10.*, 5.15.212 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.145 ≤ 6.6.*, 6.12.97 ≤ 6.12.*, 6.18.40 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 15 Aug 2026 · Last source change 23 Aug 2026, 12:46 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-23
European sourceENISA EUVD · EUVD-2026-59042
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-72084 to remediation: access.redhat.com/CVE-2026-72084.
    Before
    remediation: access.redhat.com/CVE-2026-72084
    After
    remediation: access.redhat.com/CVE-2026-72084
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/88c67c3de914e19172e1d878a7625c5b06c20ec5; removed remediation: git.kernel.org/842248047ef28dbf3b3f7f49a0ec315054d4dab8.
    Before
    remediation: git.kernel.org/842248047ef28dbf3b3f7f49a0ec315054d4dab8
    After
    remediation: git.kernel.org/88c67c3de914e19172e1d878a7625c5b06c20ec5
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 842248047ef28dbf3b3f7f49a0ec315054d4dab8; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 03fbc7de8d5e85fc8420e57e8304c855efd453ab; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 9298078a8f7d8181a04614a34ab655ccdf038204; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 004ccd2d3b4ac36a300e05e01df152e5c02a5a82; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 555a89846ed888d7401b3f7200934c0fbedcbb46; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < d04a179085c262c9ed577d0a4cbc6482ff1fd9a3; 2.6.38 · Fixed: < 2.6.38; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    After
    c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 88c67c3de914e19172e1d878a7625c5b06c20ec5; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 842248047ef28dbf3b3f7f49a0ec315054d4dab8; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 03fbc7de8d5e85fc8420e57e8304c855efd453ab; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 9298078a8f7d8181a04614a34ab655ccdf038204; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 004ccd2d3b4ac36a300e05e01df152e5c02a5a82; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 555a89846ed888d7401b3f7200934c0fbedcbb46; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < d04a179085c262c9ed577d0a4cbc6482ff1fd9a3 · Fixed: < 2.6.38; 5.10.266 ≤ 5.10.*; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 842248047ef28dbf3b3f7f49a0ec315054d4dab8; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 03fbc7de8d5e85fc8420e57e8304c855efd453ab; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 9298078a8f7d8181a04614a34ab655ccdf038204; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 004ccd2d3b4ac36a300e05e01df152e5c02a5a82; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 555a89846ed888d7401b3f7200934c0fbedcbb46; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < d04a179085c262c9ed577d0a4cbc6482ff1fd9a3; 2.6.38 · Fixed: < 2.6.38; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2-rc4 ≤ *
    After
    c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 842248047ef28dbf3b3f7f49a0ec315054d4dab8; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 03fbc7de8d5e85fc8420e57e8304c855efd453ab; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 6ca5de8782e67573a61a6736b6dc0ffe58dcdf59; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 9298078a8f7d8181a04614a34ab655ccdf038204; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 004ccd2d3b4ac36a300e05e01df152e5c02a5a82; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < 555a89846ed888d7401b3f7200934c0fbedcbb46; c66ac9db8d4ad9994a02b3e933ea2ccc643e1fe5 < d04a179085c262c9ed577d0a4cbc6482ff1fd9a3; 2.6.38 · Fixed: < 2.6.38; 5.15.212 ≤ 5.15.*; 6.1.178 ≤ 6.1.*; 6.6.145 ≤ 6.6.*; 6.12.97 ≤ 6.12.*; 6.18.40 ≤ 6.18.*; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  6. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  7. CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  8. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-59042↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-72084 · cve.blacktree.nl