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

scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer

Linux · Linux

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 294 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 severityHighOperational priority:High, 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.33% 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 30 daysRemediation target: Within 180 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 294 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.

25 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.105-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.107-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-1Debian Security Tracker ↗Source updated 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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-74557 · CSAF 2.0 · revision 9 · interimSUSE Product Security TeamCVE-2026-74557
325 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-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros 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
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the target-supplied data segment. The segment carries a 2-byte sense length followed by the sense bytes, so it must hold 2 + senselen bytes, but the bounds check only requires datalen >= senselen: senselen = get_unaligned_be16(data); if (datalen sense_buffer, data + 2, min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE)); A target that returns a SCSI Response whose datalen equals senselen (with senselen data contents and end up in the command's sense buffer, which is returned to userspace. Account for the 2-byte sense length prefix in the check.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-74557 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer
274 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 libiscsi component. An incorrect bounds check in the `iscsi_scsi_cmd_rsp()` function allows a malicious iSCSI target to craft a SCSI Response. This can lead to a read beyond the intended buffer, causing stale connection data to be copied into the SCSI sense buffer and subsequently returned to userspace, potentially disclosing sensitive information.
Remediation
Affected
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-59622

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the target-supplied data segment. The segment carries a 2-byte sense length followed by the sense bytes, so it must hold 2 + senselen bytes, but the bounds check only requires datalen >= senselen: senselen = get_unaligned_be16(data); if (datalen < senselen) goto invalid_datalen; memcpy(sc->sense_buffer, data + 2, min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE)); A target that returns a SCSI Response whose datalen equals senselen (with senselen <= SCSI_SENSE_BUFFERSIZE) makes the memcpy() from data + 2 read up to two bytes past the received data. Those bytes are stale conn->data contents and end up in the command's sense buffer, which is returned to userspace. Account for the 2-byte sense length prefix in the check.

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
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 294 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: libiscsi: Fix stale-data leak into the SCSI sense buffer iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the target-supplied data segment. The segment carries a 2-byte sense length followed by the sense bytes, so it must hold 2 + senselen bytes, but the bounds check only requires datalen >= senselen: senselen = get_unaligned_be16(data); if (datalen < senselen) goto invalid_datalen; memcpy(sc->sense_buffer, data + 2, min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE)); A target that returns a SCSI Response whose datalen equals senselen (with senselen <= SCSI_SENSE_BUFFERSIZE) makes the memcpy() from data + 2 read up to two bytes past the received data. Those bytes are stale conn->data contents and end up in the command's sense buffer, which is returned to userspace. Account for the 2-byte sense length prefix in the check.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the target-supplied data segment. The segment carries a 2-byte sense length followed by the sense bytes, so it must hold 2 + senselen bytes, but the bounds check only requires datalen >= senselen: senselen = get_unaligned_be16(data); if (datalen < senselen) goto invalid_datalen; memcpy(sc->sense_buffer, data + 2, min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE)); A target that returns a SCSI Response whose datalen equals senselen (with senselen <= SCSI_SENSE_BUFFERSIZE) makes the memcpy() from data + 2 read up to two bytes past the received data. Those bytes are stale conn->data contents and end up in the command's sense buffer, which is returned to userspace. Account for the 2-byte sense length prefix in the check.

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: libiscsi: Fix stale-data leak into the SCSI sense buffer iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the target-supplied data segment. The segment carries a 2-byte sense length followed by the sense bytes, so it must hold 2 + senselen bytes, but the bounds check only requires datalen >= senselen: senselen = get_unaligned_be16(data); if (datalen < senselen) goto invalid_datalen; memcpy(sc->sense_buffer, data + 2, min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE)); A target that returns a SCSI Response whose datalen equals senselen (with senselen <= SCSI_SENSE_BUFFERSIZE) makes the memcpy() from data + 2 read up to two bytes past the received data. Those bytes are stale conn->data contents and end up in the command's sense buffer, which is returned to userspace. Account for the 2-byte sense length prefix in the check.

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:N/A:N

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.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
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-59622Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer iscsi_scsi_cmd_rsp() copies the sense data of a SCSI Response from the target-supplied data segment. The segment carries a 2-byte sense length followed by the sense bytes, so it must hold 2 + senselen bytes, but the bounds check only requires datalen >= senselen: senselen = get_unaligned_be16(data); if (datalen < senselen) goto invalid_datalen; memcpy(sc->sense_buffer, data + 2, min_t(uint16_t, senselen, SCSI_SENSE_BUFFERSIZE)); A target that returns a SCSI Response whose datalen equals senselen (with senselen <= SCSI_SENSE_BUFFERSIZE) makes the memcpy() from data + 2 read up to two bytes past the received data. Those bytes are stale conn->data contents and end up in the command's sense buffer, which is returned to userspace. Account for the 2-byte sense length prefix in the check.

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 ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-74534 Référence CVE CVE-2026-74535 https://www.cve.org/CVERecord?id=CVE-2026-74535 Référence CVE CVE-2026-74536 https://www.cve.org/CVERecord?id=CVE-2026-74536 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74545 https://www.cve.org/CVERecord?id=CVE-2026-74545 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74571 https://www.cve.org/CVERecord?id=CVE-2026-74571 Référence CVE CVE-2026-74577 https://www.cve.org/CVERecord?id=CVE-2026-74577 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74582 https://www.cve.org/CVERecord?id=CVE-2026-74582 Référence CVE CVE-2026-74584 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-74496 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 https://www.cve.org/CVERecord?id=CVE-2026-74519 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74581 https://www.cve.org/CVERecord?id=CVE-2026-74581 Référence CVE CVE-2026-74582 https://www.cve.org/CVERecord?id=CVE-2026-74582 Référence CVE CVE-2026-74584 https://www.cve.org/CVERecord?id=CVE-2026-74584 Référence CVE CVE-2026-74615 https://www.cve.org/CVERecord?id=CVE-2026-74615 Référence CVE CVE-2026-74616 https://www.cve.org/CVERecord?id=CVE-2026-74616 Référence CVE CVE-2026-74669 https://www.cve.org/CVERecord?id=CVE-2026-74669 Référence CVE CVE-2026-74673 https://www.cve.org/CVERecord?id=CVE-2026-74673 Référence CVE CVE-2026-74695 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74547 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74549 https://www.cve.org/CVERecord?id=CVE-2026-74549 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74551 https://www.cve.org/CVERecord?id=CVE-2026-74551 Référence CVE CVE-2026-74552 https://www.cve.org/CVERecord?id=CVE-2026-74552 Référence CVE CVE-2026-74553 https://www.cve.org/CVERecord?id=CVE-2026-74553 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74564 https://www.cve.org/CVERecord?id=CVE-2026-74564 Référence CVE CVE-2026-74565 https://www.cve.org/CVERecord?id=CVE-2026-74565 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74569 https://www.cve.org/CVERecord?id=CVE-2026-74569 Référence CVE CVE-2026-74572 https://www.cve.org/CVERecord?id=CVE-2026-74572 Référence CVE CVE-2026-74574 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74547 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74549 https://www.cve.org/CVERecord?id=CVE-2026-74549 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74551 https://www.cve.org/CVERecord?id=CVE-2026-74551 Référence CVE CVE-2026-74552 https://www.cve.org/CVERecord?id=CVE-2026-74552 Référence CVE CVE-2026-74553 https://www.cve.org/CVERecord?id=CVE-2026-74553 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74564 https://www.cve.org/CVERecord?id=CVE-2026-74564 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74569 https://www.cve.org/CVERecord?id=CVE-2026-74569 Référence CVE CVE-2026-74575 https://www.cve.org/CVERecord?id=CVE-2026-74575 Référence CVE CVE-2026-74577 https://www.cve.org/CVERecord?id=CVE-2026-74577 Référence CVE CVE-2026-74579 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74547 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74549 https://www.cve.org/CVERecord?id=CVE-2026-74549 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=CVE-2026-74550 Référence CVE CVE-2026-74551 https://www.cve.org/CVERecord?id=CVE-2026-74551 Référence CVE CVE-2026-74552 https://www.cve.org/CVERecord?id=CVE-2026-74552 Référence CVE CVE-2026-74553 https://www.cve.org/CVERecord?id=CVE-2026-74553 Référence CVE CVE-2026-74555 https://www.cve.org/CVERecord?id=CVE-2026-74555 Référence CVE CVE-2026-74556 https://www.cve.org/CVERecord?id=CVE-2026-74556 Référence CVE CVE-2026-74557 https://www.cve.org/CVERecord?id=CVE-2026-74557 Référence CVE CVE-2026-74563 https://www.cve.org/CVERecord?id=CVE-2026-74563 Référence CVE CVE-2026-74564 https://www.cve.org/CVERecord?id=CVE-2026-74564 Référence CVE CVE-2026-74565 https://www.cve.org/CVERecord?id=CVE-2026-74565 Référence CVE CVE-2026-74566 https://www.cve.org/CVERecord?id=CVE-2026-74566 Référence CVE CVE-2026-74567 https://www.cve.org/CVERecord?id=CVE-2026-74567 Référence CVE CVE-2026-74569 https://www.cve.org/CVERecord?id=CVE-2026-74569 Référence CVE CVE-2026-74572 https://www.cve.org/CVERecord?id=CVE-2026-74572 Référence CVE CVE-2026-74574 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.18, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.151 ≤ 6.6.*, 6.12.103 ≤ 6.12.*, 6.18.44 ≤ 6.18.*, 7.1.8 ≤ 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 19 Aug 2026, 16:38 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-59622
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-74557 to remediation: access.redhat.com/CVE-2026-74557.
    Before
    remediation: access.redhat.com/CVE-2026-74557
    After
    remediation: access.redhat.com/CVE-2026-74557
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    After
    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; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 244 more
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/812f1ae95b22419422972748f173b0916ee4d621; removed remediation: git.kernel.org/7567f06abdefb1caf2d836107c4d08c5185c650e.
    Before
    remediation: git.kernel.org/7567f06abdefb1caf2d836107c4d08c5185c650e
    After
    remediation: git.kernel.org/812f1ae95b22419422972748f173b0916ee4d621
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 7567f06abdefb1caf2d836107c4d08c5185c650e; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 60499924faf4ef97e84228c20515218ef121facf; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 3ef209ca0b4b68c75e9a814d90cc916026b5a6ac; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 1f07a897d43c63e6c9458bf77450defef39b5833; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 98b87885de4b7f605533a2860685f5689fce8e82; 2.6.18 · Fixed: < 2.6.18; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 812f1ae95b22419422972748f173b0916ee4d621; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < fef6167e8149896cd81bea333fd51b1c91239149; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < baa04572673125e4d5bc309b4077d1cb46cc78d1; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 7567f06abdefb1caf2d836107c4d08c5185c650e; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 60499924faf4ef97e84228c20515218ef121facf; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 3ef209ca0b4b68c75e9a814d90cc916026b5a6ac; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 1f07a897d43c63e6c9458bf77450defef39b5833; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 98b87885de4b7f605533a2860685f5689fce8e82 · Fixed: < 2.6.18; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 7567f06abdefb1caf2d836107c4d08c5185c650e; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 60499924faf4ef97e84228c20515218ef121facf; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 3ef209ca0b4b68c75e9a814d90cc916026b5a6ac; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 1f07a897d43c63e6c9458bf77450defef39b5833; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 98b87885de4b7f605533a2860685f5689fce8e82; 2.6.18 · Fixed: < 2.6.18; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2-rc6 ≤ *
    After
    7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 7567f06abdefb1caf2d836107c4d08c5185c650e; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 60499924faf4ef97e84228c20515218ef121facf; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 3ef209ca0b4b68c75e9a814d90cc916026b5a6ac; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 1f07a897d43c63e6c9458bf77450defef39b5833; 7996a778ff8c717cb1a7a294475c59cc8f1e9fb8 < 98b87885de4b7f605533a2860685f5689fce8e82; 2.6.18 · Fixed: < 2.6.18; 6.6.151 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  6. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  7. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
    Before
    not recorded
    After
    7.5 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)
    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-59622↗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-74557 · cve.blacktree.nl