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

scsi: core: Wake up the error handler when final completions race against each other

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

4.7MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.11% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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: No default targetRemediation target: Normal maintenance

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 25 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.69-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.8-1Debian Security Tracker ↗Source updated 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2026-23110 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: scsi: core: Wake up the error handler when final completions race against each other
62 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
Race condition vulnerabilities were found in the Linux kernel's SCSI error handler wake-up logic. Memory ordering issues in scsi_dec_host_busy() and ordering problems in scsi_eh_inc_host_failed() can cause the SCSI error handler to never wake up when command completions race against each other. This leaves I/O stuck indefinitely as the error recovery state cannot advance.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-5431

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 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: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.

What

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation with low privileges. 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: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-362
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-5431Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Wake up the error handler when final completions race against each other The fragile ordering between marking commands completed or failed so that the error handler only wakes when the last running command completes or times out has race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. First, there is an memory ordering issue within scsi_dec_host_busy(). The write which clears SCMD_STATE_INFLIGHT may be reordered with reads counting in scsi_host_busy(). While the local CPU will see its own write, reordering can allow other CPUs in scsi_dec_host_busy() or scsi_eh_inc_host_failed() to see a raised busy count, causing no CPU to see a host busy equal to the host_failed count. This race condition can be prevented with a memory barrier on the error path to force the write to be visible before counting host busy commands. Second, there is a general ordering issue with scsi_eh_inc_host_failed(). By counting busy commands before incrementing host_failed, it can race with a final command in scsi_dec_host_busy(), such that scsi_dec_host_busy() does not see host_failed incremented but scsi_eh_inc_host_failed() counts busy commands before SCMD_STATE_INFLIGHT is cleared by scsi_dec_host_busy(), resulting in neither waking the error handler task. This needs the call to scsi_host_busy() to be moved after host_failed is incremented to close the race condition.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0324Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260211Security Bulletin 11 Feb 2026

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

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

d?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23104 https://www.cve.org/CVERecord?id=CVE-2026-23104 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23106 https://www.cve.org/CVERecord?id=CVE-2026-23106 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23109 https://www.cve.org/CVERecord?id=CVE-2026-23109 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23114 https://www.cve.org/CVERecord?id=CVE-2026-23114 Référence CVE CVE-2026-23115 https://www.cve.org/CVERecord?id=CVE-2026-23115 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23118 https://www.cve.org/CVERecord?id=CVE-2026-23118 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=

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

lletin de sécurité Red Hat RHSA-2026:56573 du 19 août 2026 https://access.redhat.com/errata/RHSA-2026:56573 Bulletin de sécurité Red Hat RHSA-2026:56574 du 19 août 2026 https://access.redhat.com/errata/RHSA-2026:56574 Bulletin de sécurité Red Hat RHSA-2026:57254 du 20 août 2026 https://access.redhat.com/errata/RHSA-2026:57254 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2026-17523 https://www.cve.org/CVERecord?id=CVE-2026-17523 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23104 https://www.cve.org/CVERecord?id=CVE-2026-23104 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23106 https://www.cve.org/CVERecord?id=CVE-2026-23106 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23109 https://www.cve.org/CVERecord?id=CVE-2026-23109 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23114 https://www.cve.org/CVERecord?id=CVE-2026-23114 Référence CVE CVE-2026-23115 https://www.cve.org/CVERecord?id=CVE-2026-23115 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23118 https://www.cve.org/CVERecord?id=CVE-2026-23118 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=

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

m/errata/RHSA-2026:44385 Bulletin de sécurité Red Hat RHSA-2026:44522 du 23 juillet 2026 https://access.redhat.com/errata/RHSA-2026:44522 Bulletin de sécurité Red Hat RHSA-2026:44694 du 23 juillet 2026 https://access.redhat.com/errata/RHSA-2026:44694 Référence CVE CVE-2024-46738 https://www.cve.org/CVERecord?id=CVE-2024-46738 Référence CVE CVE-2024-50076 https://www.cve.org/CVERecord?id=CVE-2024-50076 Référence CVE CVE-2025-39982 https://www.cve.org/CVERecord?id=CVE-2025-39982 Référence CVE CVE-2025-71113 https://www.cve.org/CVERecord?id=CVE-2025-71113 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23168 https://www.cve.org/CVERecord?id=CVE-2026-23168 Référence CVE CVE-2026-23243 https://www.cve.org/CVERecord?id=CVE-2026-23243 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31530 https://www.cve.org/CVERecord?id=CVE-2026-31530 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23104 https://www.cve.org/CVERecord?id=CVE-2026-23104 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23106 https://www.cve.org/CVERecord?id=CVE-2026-23106 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23109 https://www.cve.org/CVERecord?id=CVE-2026-23109 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23114 https://www.cve.org/CVERecord?id=CVE-2026-23114 Référence CVE CVE-2026-23115 https://www.cve.org/CVERecord?id=CVE-2026-23115 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23118 https://www.cve.org/CVERecord?id=CVE-2026-23118 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71197, CVE-2025-71221, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2026-3497, CVE-2026-22977, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-22992, CVE-2026-22994, CVE-2026-23003, CVE-2026-23005, CVE-2026-23010, CVE-2026-23011, CVE-2026-23019, CVE-2026-23026, CVE-2026-23038, CVE-2026-23054, CVE-2026-23060, CVE-2026-23083, CVE-2026-23084, CVE-2026-23086, CVE-2026-23087, CVE-2026-23095, CVE-2026-23100, CVE-2026-23103, CVE-2026-23110, CVE-2026-23111, CVE-2026-23113, CVE-2026-23154, CVE-2026-23204, CVE-2026-23231, CVE-2026-23242, CVE-2026-23243, CVE-2026-23245, CVE-2026-23270, CVE-2026-23271, CVE-2026-23273, CVE-2026-23274, CVE-2026-23277, CVE-2026-23284, CVE-2026-23287, CVE-2026-23290, CVE-2026-23293, CVE-2026-23300, CVE-2026-23304, CVE-2026-23319, CVE-2026-23321, CVE-2026-23335, CVE-2026-23340, CVE-2026-23343, CVE-2026-23351, CVE-2026-23359, CVE-2026-23365, CVE-2026-23368, CVE-2026-23370, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381, CVE-2026-23391, CVE-2026-23392, CVE-2026-23397, CVE-2026-23398, CVE-2026-23414, CVE-2026-23422, CVE-2026-23434, CVE-2026-23438, CVE-2026

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

d?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23100 https://www.cve.org/CVERecord?id=CVE-2026-23100 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23123 https://www.cve.org/CVERecord?id=CVE-2026-23123 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=CVE-2026-23124 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23123 https://www.cve.org/CVERecord?id=CVE-2026-23123 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23123 https://www.cve.org/CVERecord?id=CVE-2026-23123 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23123 https://www.cve.org/CVERecord?id=CVE-2026-23123 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23123 https://www.cve.org/CVERecord?id=CVE-2026-23123 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23095 Référence CVE CVE-2026-23096 https://www.cve.org/CVERecord?id=CVE-2026-23096 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23104 https://www.cve.org/CVERecord?id=CVE-2026-23104 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=CVE-2026-23125 Référence CVE CVE-2026-23128 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23095 Référence CVE CVE-2026-23096 https://www.cve.org/CVERecord?id=CVE-2026-23096 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23104 https://www.cve.org/CVERecord?id=CVE-2026-23104 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23116 https://www.cve.org/CVERecord?id=CVE-2026-23116 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23129 https://www.cve.org/CVERecord?id=CVE-2026-23129 Référence CVE CVE-2026-23133 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-23096 Référence CVE CVE-2026-23097 https://www.cve.org/CVERecord?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23100 https://www.cve.org/CVERecord?id=CVE-2026-23100 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23118 https://www.cve.org/CVERecord?id=CVE-2026-23118 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-23096 Référence CVE CVE-2026-23097 https://www.cve.org/CVERecord?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23100 https://www.cve.org/CVERecord?id=CVE-2026-23100 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23112 https://www.cve.org/CVERecord?id=CVE-2026-23112 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23118 https://www.cve.org/CVERecord?id=CVE-2026-23118 Référence CVE CVE-2026-23119 https://www.cve.org/CVERecord?id=CVE-2026-23119 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23121 https://www.cve.org/CVERecord?id=CVE-2026-23121 Référence CVE CVE-2026-23124 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Gestion détaillée du document le 13 février 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2026-23097 Référence CVE CVE-2026-23098 https://www.cve.org/CVERecord?id=CVE-2026-23098 Référence CVE CVE-2026-23099 https://www.cve.org/CVERecord?id=CVE-2026-23099 Référence CVE CVE-2026-23101 https://www.cve.org/CVERecord?id=CVE-2026-23101 Référence CVE CVE-2026-23102 https://www.cve.org/CVERecord?id=CVE-2026-23102 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23105 https://www.cve.org/CVERecord?id=CVE-2026-23105 Référence CVE CVE-2026-23107 https://www.cve.org/CVERecord?id=CVE-2026-23107 Référence CVE CVE-2026-23108 https://www.cve.org/CVERecord?id=CVE-2026-23108 Référence CVE CVE-2026-23110 https://www.cve.org/CVERecord?id=CVE-2026-23110 Gestion détaillée du document le 13 février 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-007926LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。scsi: コアにおいて、最終完了処理が競合したときにエラーハンドラが起動する問題が存在していました。コマンドが完了または失敗としてマークされる順序に脆弱性があり、エラーハンドラが最後に実行中のコマンドが完了またはタイムアウトしたときのみ起動する仕組みに競合条件が発生していました。これにより、SCSIレイヤがエラーハンドラを起動できず、SCSIホストを通るI/Oが停止し、エラー状態が進行できなくなる恐れがありました。第一に、scsi_dec_host_busy()内でメモリの順序に関する問題がありました。SCMD_STATE_INFLIGHTをクリアする書き込みが、scsi_host_busy()の読み取りと再順序化される可能性があります。ローカルCPUは自身の書き込みを認識しますが、他のCPUはscsi_dec_host_busy()やscsi_eh_inc_host_failed()においてカウントが増加した状態を見てしまい、どのCPUもhost_busyがhost_failedカウントと等しい状態を認識しません。この競合条件は、エラーパス上にメモリバリアを設け、書き込みがhost_busyコマンドのカウントより先に可視化されるようにすることで防止できます。第二に、scsi_eh_inc_host_failed()に一般的な順序問題があります。host_failedをインクリメントする前にbusyコマンドをカウントしているため、scsi_dec_host_busy()の最終コマンドと競合し、scsi_dec_host_busy()がhost_failedの増加を認識せず、scsi_eh_inc_host_failed()がSCMD_STATE_INFLIGHTをscsi_dec_host_busy()によってクリアされる前にbusyコマンドをカウントしてしまい、エラーハンドラタスクが起動しない状態になります。この競合条件を解消するために、host_failedがインクリメントされた後にscsi_host_busy()を呼び出すように変更されました。

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: < 5.5, 5.10.249 ≤ 5.10.*, 6.1.162 ≤ 6.1.*, 6.6.122 ≤ 6.6.*, 6.12.68 ≤ 6.12.*, 6.18.8 ≤ 6.18.*, 6.19 ≤ *
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
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 4 Feb 2026 · Last source change 8 Sept 2026, 08:44 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-5431
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-23110 to remediation: access.redhat.com/CVE-2026-23110.
    Before
    remediation: access.redhat.com/CVE-2026-23110
    After
    remediation: access.redhat.com/CVE-2026-23110
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; kernel-doc as a component of Red Hat Enterprise Linux 8; kernel-headers as a component of Red Hat Enterprise Linux 8; kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8; and 32 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.39.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.39.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.39.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.39.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.39.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.39.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.39.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.39.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.39.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.39.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.39.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.39.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.39.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.39.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.39.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.39.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.39.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.39.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.39.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 582 more
    After
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; kernel-doc as a component of Red Hat Enterprise Linux 8; kernel-headers as a component of Red Hat Enterprise Linux 8; kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8; and 32 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debug-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debug-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-64k-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-debuginfo-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debug-devel-matched-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-aarch64-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-ppc64le-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-s390x-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-common-x86_64-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.98.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); and 1194 more
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    6eb045e092efefafc6687409a6fa6d1dabf0fb69 < cc872e35c0df80062abc71268d690a2f749e542e; 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 6d9a367be356101963c249ebf10ea10b32886607; 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 9fdc6f28d5e81350ab1d2cac8389062bd09e61e1; 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0; 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 219f009ebfd1ef3970888ee9eef4c8a06357f862; 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < fe2f8ad6f0999db3b318359a01ee0108c703a8c3; 5.5 · Fixed: < 5.5; 5.10.249 ≤ 5.10.*; 6.1.162 ≤ 6.1.*; 6.6.122 ≤ 6.6.*; 6.12.68 ≤ 6.12.*; 6.18.8 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < cc872e35c0df80062abc71268d690a2f749e542e, 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 6d9a367be356101963c249ebf10ea10b32886607, 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 9fdc6f28d5e81350ab1d2cac8389062bd09e61e1, 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 64ae21b9c4f0c7e60cf47a53fa7ab68852079ef0, 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < 219f009ebfd1ef3970888ee9eef4c8a06357f862, 6eb045e092efefafc6687409a6fa6d1dabf0fb69 < fe2f8ad6f0999db3b318359a01ee0108c703a8c3, 5.5 · Fixed: Linux: < 5.5, 5.10.249 ≤ 5.10.*, 6.1.162 ≤ 6.1.*, 6.6.122 ≤ 6.6.*, 6.12.68 ≤ 6.12.*, 6.18.8 ≤ 6.18.*, 6.19 ≤ *
    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-5431↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗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-23110 · cve.blacktree.nl