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

ipvlan: Make the addrs_lock be per port

Linux · Linux

7.8HighCVSS 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 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 severityHighOperational priority:Medium, 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.12% 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: As exposure requiresRemediation target: Within 365 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 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 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.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-23103 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ipvlan: Make the addrs_lock be per port
184 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 race condition vulnerability was found in the Linux kernel's ipvlan driver. The per-device addrs_lock was incorrectly used instead of a per-port lock, and some code paths (ipvlan_open/ipvlan_close) failed to acquire the lock entirely. For IPv6 address changes that don't require RTNL lock, concurrent address additions could cause false-negative results from ipvlan_addr_busy() or race conditions when adding addresses to the hash table.
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.
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: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-5439

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.

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.8 · 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 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: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.

What

In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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 → Improper Locking → 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
Low: no specialised conditions are recorded
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-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-667
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-5439Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ipvlan: Make the addrs_lock be per port Make the addrs_lock be per port, not per ipvlan dev. Initial code seems to be written in the assumption, that any address change must occur under RTNL. But it is not so for the case of IPv6. So 1) Introduce per-port addrs_lock. 2) It was needed to fix places where it was forgotten to take lock (ipvlan_open/ipvlan_close) This appears to be a very minor problem though. Since it's highly unlikely that ipvlan_add_addr() will be called on 2 CPU simultaneously. But nevertheless, this could cause: 1) False-negative of ipvlan_addr_busy(): one interface iterated through all port->ipvlans + ipvlan->addrs under some ipvlan spinlock, and another added IP under its own lock. Though this is only possible for IPv6, since looks like only ipvlan_addr6_event() can be called without rtnl_lock. 2) Race since ipvlan_ht_addr_add(port) is called under different ipvlan->addrs_lock locks This should not affect performance, since add/remove IP is a rare situation and spinlock is not taken on fast paths.

Official EUVD record ↗
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-1204Multiples vulnérabilités dans le noyau Linux de Red Hat

mbre 2026 https://access.redhat.com/errata/RHSA-2026:68507 Bulletin de sécurité Red Hat RHSA-2026:68532 du 17 septembre 2026 https://access.redhat.com/errata/RHSA-2026:68532 Référence CVE CVE-2024-53161 https://www.cve.org/CVERecord?id=CVE-2024-53161 Référence CVE CVE-2024-58007 https://www.cve.org/CVERecord?id=CVE-2024-58007 Référence CVE CVE-2025-40026 https://www.cve.org/CVERecord?id=CVE-2025-40026 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-68745 https://www.cve.org/CVERecord?id=CVE-2025-68745 Référence CVE CVE-2025-71127 https://www.cve.org/CVERecord?id=CVE-2025-71127 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23172 https://www.cve.org/CVERecord?id=CVE-2026-23172 Référence CVE CVE-2026-23466 https://www.cve.org/CVERecord?id=CVE-2026-23466 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31539 https://www.cve.org/CVERecord?id=CVE-2026-31539 Référence CVE CVE-2026-31566 https://www.cve.org/CVERecord?id=CVE-2026-31566 Référence CVE CVE-2026-31656 https://www.cve.org/CVERecord?id=CVE-2026-31656 Référence CVE CVE-2026-31663 https://www.cve.org/CVERecord?id=CVE-2026-31663 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

025-71112, CVE-2025-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

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

d?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23093 Référence CVE CVE-2026-23094 https://www.cve.org/CVERecord?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23093 Référence CVE CVE-2026-23094 https://www.cve.org/CVERecord?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23093 Référence CVE CVE-2026-23094 https://www.cve.org/CVERecord?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23093 Référence CVE CVE-2026-23094 https://www.cve.org/CVERecord?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2026-23090 Référence CVE CVE-2026-23091 https://www.cve.org/CVERecord?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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-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-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-0546Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-40309 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-23004 https://www.cve.org/CVERecord?id=CVE-2026-23004 Référence CVE CVE-2026-23030 https://www.cve.org/CVERecord?id=CVE-2026-23030 Référence CVE CVE-2026-23047 https://www.cve.org/CVERecord?id=CVE-2026-23047 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23136 https://www.cve.org/CVERecord?id=CVE-2026-23136 Référence CVE CVE-2026-23140 https://www.cve.org/CVERecord?id=CVE-2026-23140 Référence CVE CVE-2026-23187 https://www.cve.org/CVERecord?id=CVE-2026-23187 Référence CVE CVE-2026-23193 https://www.cve.org/CVERecord?id=CVE-2026-23193 Référence CVE CVE-2026-23201 https://www.cve.org/CVERecord?id=CVE-2026-23201 Référence CVE CVE-2026-23204 https://www.cve.org/CVERecord?id=CVE-2026-23204 Référence CVE CVE-2026-23215 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23090 Référence CVE CVE-2026-23091 https://www.cve.org/CVERecord?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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-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-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-0520Multiples vulnérabilités dans le noyau Linux de SUSE

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer une élévation de privilèges, un déni de service et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-71269 Référence CVE CVE-2026-22999 https://www.cve.org/CVERecord?id=CVE-2026-22999 Référence CVE CVE-2026-23030 https://www.cve.org/CVERecord?id=CVE-2026-23030 Référence CVE CVE-2026-23047 https://www.cve.org/CVERecord?id=CVE-2026-23047 Référence CVE CVE-2026-23054 https://www.cve.org/CVERecord?id=CVE-2026-23054 Référence CVE CVE-2026-23069 https://www.cve.org/CVERecord?id=CVE-2026-23069 Référence CVE CVE-2026-23072 https://www.cve.org/CVERecord?id=CVE-2026-23072 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23088 https://www.cve.org/CVERecord?id=CVE-2026-23088 Référence CVE CVE-2026-23103 https://www.cve.org/CVERecord?id=CVE-2026-23103 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23120 https://www.cve.org/CVERecord?id=CVE-2026-23120 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=CVE-2026-23125 Référence CVE CVE-2026-23136 https://www.cve.org/CVERecord?id=CVE-2026-23136 Référence CVE CVE-2026-23138 https://www.cve.org/CVERecord?id=CVE-2026-23138 Référence CVE CVE-2026-23140 https://www.cve.org/CVERecord?id=CVE-2026-23140 Référence CVE CVE-2026-23154 https://www.cve.org/CVERecord?id=CVE-2026-23154 Référence CVE CVE-2026-23157 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23090 Référence CVE CVE-2026-23091 https://www.cve.org/CVERecord?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 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=CVE-2026-23124 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23090 Référence CVE CVE-2026-23091 https://www.cve.org/CVERecord?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 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=CVE-2026-23124 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2026-23090 Référence CVE CVE-2026-23091 https://www.cve.org/CVERecord?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 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=CVE-2026-23124 Référence CVE CVE-2026-23125 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-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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=

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

d?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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=

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

d?id=CVE-2026-23091 Référence CVE CVE-2026-23093 https://www.cve.org/CVERecord?id=CVE-2026-23093 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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

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

d?id=CVE-2026-23093 Référence CVE CVE-2026-23094 https://www.cve.org/CVERecord?id=CVE-2026-23094 Référence CVE CVE-2026-23095 https://www.cve.org/CVERecord?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-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-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

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-008343LinuxのLinux Kernelにおけるリソースのロックに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。ipvlanにおけるaddrs_lockをipvlanデバイス単位ではなくポート単位に変更しました。初期のコードは、アドレスの変更はすべてRTNLの下で行われるという前提で書かれていましたが、IPv6の場合はそうではありません。そのため、1) ポート単位のaddrs_lockを導入しました。2) ipvlan_openやipvlan_closeでロックを取得し忘れていた箇所も修正しました。この問題は非常に小さく、ipvlan_add_addr()が2つのCPUで同時に呼ばれる可能性は極めて低いため、重大ではありません。しかし、次の問題を引き起こす可能性があります。1) ipvlan_addr_busy()の誤った否定判定。具体的には、一方のインターフェースがあるipvlanスピンロックの下で全ポートのipvlansおよびipvlanのアドレスを走査している間に、別のインターフェースが自身のロックでIPを追加した場合です。これはIPv6の場合のみ可能で、ipvlan_addr6_event()だけがrtnl_lockなしで呼ばれうるためです。2) 異なるipvlan-addrs_lockロックの下でipvlan_ht_addr_add(port)が呼ばれることによる競合状態です。この修正はパフォーマンスに影響しません。なぜなら、IPの追加・削除は稀な操作であり、スピンロックは高速パス上で取得されないためです。

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
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 4 Feb 2026 · Last source change 8 Sept 2026, 08:44 UTC · CWE-667 · Improper Locking

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-14
European sourceENISA EUVD · EUVD-2026-5439
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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. Affected versionsThe structured affected or fixed version information changed.
    Before
    8230819494b3bf284ca7262ac5f877333147b937 < 3c149b662cbb202a450e81f938e702ba333864ad; 8230819494b3bf284ca7262ac5f877333147b937 < 70feb16e3fbfb10b15de1396557c38e99f1ab8df; 8230819494b3bf284ca7262ac5f877333147b937 < 88f83e6c9cdb46b8c8ddd0ba01393362963cf589; 8230819494b3bf284ca7262ac5f877333147b937 < 04ba6de6eff61238e5397c14ac26a6578c7735a5; 8230819494b3bf284ca7262ac5f877333147b937 < 1f300c10d92c547c3a7d978e1212ff52f18256ed; 8230819494b3bf284ca7262ac5f877333147b937 < 6a81e2db096913d7e43aada1c350c1282e76db39; 8230819494b3bf284ca7262ac5f877333147b937 < d3ba32162488283c0a4c5bedd8817aec91748802; 4.17 · Fixed: < 4.17; 5.10.249 ≤ 5.10.*; 5.15.199 ≤ 5.15.*; 6.1.162 ≤ 6.1.*; 6.6.122 ≤ 6.6.*; 6.12.68 ≤ 6.12.*; 6.18.8 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 8230819494b3bf284ca7262ac5f877333147b937 < 3c149b662cbb202a450e81f938e702ba333864ad, 8230819494b3bf284ca7262ac5f877333147b937 < 70feb16e3fbfb10b15de1396557c38e99f1ab8df, 8230819494b3bf284ca7262ac5f877333147b937 < 88f83e6c9cdb46b8c8ddd0ba01393362963cf589, 8230819494b3bf284ca7262ac5f877333147b937 < 04ba6de6eff61238e5397c14ac26a6578c7735a5, 8230819494b3bf284ca7262ac5f877333147b937 < 1f300c10d92c547c3a7d978e1212ff52f18256ed, 8230819494b3bf284ca7262ac5f877333147b937 < 6a81e2db096913d7e43aada1c350c1282e76db39, 8230819494b3bf284ca7262ac5f877333147b937 < d3ba32162488283c0a4c5bedd8817aec91748802, 4.17 · Fixed: Linux: < 4.17, 5.10.249 ≤ 5.10.*, 5.15.199 ≤ 5.15.*, 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-5439↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-23103 · cve.blacktree.nl