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

netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()

Linux · Linux

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

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 31 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.50% 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 31 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.73-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.164-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.10-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.

4 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: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2026-23111 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Kernel: Privilege escalation or denial of service in nf_tables via inverted element activity check
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel's nf_tables component. A logic bug in nft_map_catchall_activate causes an inverted element activity check during the abort path of a failed transaction. This can lead to a use-after-free vulnerability, as catchall verdict elements may still reference a freed chain. A local low privileged user can exploit this to cause a denial of service or potentially achieve privilege escalation.
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.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
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.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-253495 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-253495: Multiple Vulnerabilities in SINEC OS before V4.0
1 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.
Remediation
Update to V4.0 or later version
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-6170

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.

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 31 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: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

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 → Use After Free → gain additional privileges
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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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.
Privilege escalationCWE-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-6170Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0421Linux 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-20260218Security Bulletin 18 Feb 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 18 Feb 2026, published on 18 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-0880Multiples vulnérabilités dans les produits Siemens

025-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-23439, CVE-2026

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

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

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et un déni de service à distance.

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

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

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

d?id=CVE-2025-39766 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23066 https://www.cve.org/CVERecord?id=CVE-2026-23066 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23144 https://www.cve.org/CVERecord?id=CVE-2026-23144 Référence CVE CVE-2026-23156 https://www.cve.org/CVERecord?id=CVE-2026-23156 Référence CVE CVE-2026-23171 https://www.cve.org/CVERecord?id=CVE-2026-23171 Référence CVE CVE-2026-23191 https://www.cve.org/CVERecord?id=CVE-2026-23191 Référence CVE CVE-2026-23193 https://www.cve.org/CVERecord?id=CVE-2026-23193 Référence CVE CVE-2026-23204 https://www.cve.org/CVERecord?id=CVE-2026-23204 Référence CVE CVE-2026-23209 https://www.cve.org/CVERecord?id=CVE-2026-23209 Référence CVE CVE-2026-23216 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-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=CVE-2026-23125 Référence CVE CVE-2026-23128 https://www.cve.org/CVERecord?id=CVE-2026-23128 Référence CVE CVE-2026-23133 https://www.cve.org/CVERecord?id=CVE-2026-23133 Référence CVE CVE-2026-23145 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-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=CVE-2026-23125 Référence CVE CVE-2026-23128 https://www.cve.org/CVERecord?id=CVE-2026-23128 Référence CVE CVE-2026-23133 https://www.cve.org/CVERecord?id=CVE-2026-23133 Référence CVE CVE-2026-23145 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-0423Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2025-38206 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40240 https://www.cve.org/CVERecord?id=CVE-2025-40240 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23144 https://www.cve.org/CVERecord?id=CVE-2026-23144 Référence CVE CVE-2026-23171 https://www.cve.org/CVERecord?id=CVE-2026-23171 Référence CVE CVE-2026-23191 https://www.cve.org/CVERecord?id=CVE-2026-23191 Référence CVE CVE-2026-23193 https://www.cve.org/CVERecord?id=CVE-2026-23193 Référence CVE CVE-2026-23204 https://www.cve.org/CVERecord?id=CVE-2026-23204 Référence CVE CVE-2026-23209 https://www.cve.org/CVERecord?id=CVE-2026-23209 Référence CVE CVE-2026-23210 https://www.cve.org/CVERecord?id=CVE-2026-23210 Référence CVE CVE-2026-23231 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0422Multiples 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-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=CVE-2026-23125 Référence CVE CVE-2026-23128 https://www.cve.org/CVERecord?id=CVE-2026-23128 Référence CVE CVE-2026-23133 https://www.cve.org/CVERecord?id=CVE-2026-23133 Référence CVE CVE-2026-23145 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-23019 https://www.cve.org/CVERecord?id=CVE-2026-23019 Référence CVE CVE-2026-23020 https://www.cve.org/CVERecord?id=CVE-2026-23020 Référence CVE CVE-2026-23021 https://www.cve.org/CVERecord?id=CVE-2026-23021 Référence CVE CVE-2026-23047 https://www.cve.org/CVERecord?id=CVE-2026-23047 Référence CVE CVE-2026-23060 https://www.cve.org/CVERecord?id=CVE-2026-23060 Référence CVE CVE-2026-23074 https://www.cve.org/CVERecord?id=CVE-2026-23074 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23268 https://www.cve.org/CVERecord?id=CVE-2026-23268 Référence CVE CVE-2026-23269 https://www.cve.org/CVERecord?id=CVE-2026-23269 Gestion détaillée du document le 03 avril 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-0369Multiples vulnérabilités dans le noyau Linux de SUSE

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

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

d?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 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-23169 https://www.cve.org/CVERecord?id=CVE-2026-23169 Référence CVE CVE-2026-23176 https://www.cve.org/CVERecord?id=CVE-2026-23176 Référence CVE CVE-2026-23178 https://www.cve.org/CVERecord?id=CVE-2026-23178 Référence CVE CVE-2026-23180 https://www.cve.org/CVERecord?id=CVE-2026-23180 Référence CVE CVE-2026-23182 https://www.cve.org/CVERecord?id=CVE-2026-23182 Référence CVE CVE-2026-23187 https://www.cve.org/CVERecord?id=CVE-2026-23187 Référence CVE CVE-2026-23190 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-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=CVE-2026-23124 Référence CVE CVE-2026-23125 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-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=CVE-2026-23124 Référence CVE CVE-2026-23125 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2026-23100 https://www.cve.org/CVERecord?id=CVE-2026-23100 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-23169 https://www.cve.org/CVERecord?id=CVE-2026-23169 Référence CVE CVE-2026-23176 https://www.cve.org/CVERecord?id=CVE-2026-23176 Référence CVE CVE-2026-23178 https://www.cve.org/CVERecord?id=CVE-2026-23178 Référence CVE CVE-2026-23180 https://www.cve.org/CVERecord?id=CVE-2026-23180 Référence CVE CVE-2026-23182 https://www.cve.org/CVERecord?id=CVE-2026-23182 Référence CVE CVE-2026-23187 https://www.cve.org/CVERecord?id=CVE-2026-23187 Référence CVE CVE-2026-23190 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71228 Référence CVE CVE-2025-71229 https://www.cve.org/CVERecord?id=CVE-2025-71229 Référence CVE CVE-2025-71231 https://www.cve.org/CVERecord?id=CVE-2025-71231 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71234 https://www.cve.org/CVERecord?id=CVE-2025-71234 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 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-23169 https://www.cve.org/CVERecord?id=CVE-2026-23169 Référence CVE CVE-2026-23176 https://www.cve.org/CVERecord?id=CVE-2026-23176 Référence CVE CVE-2026-23177 https://www.cve.org/CVERecord?id=CVE-2026-23177 Référence CVE CVE-2026-23178 https://www.cve.org/CVERecord?id=CVE-2026-23178 Référence CVE CVE-2026-23179 https://www.cve.org/CVERecord?id=CVE-2026-23179 Référence CVE CVE-2026-23180 https://www.cve.org/CVERecord?id=CVE-2026-23180 Référence CVE CVE-2026-23182 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-007925LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。netfilterのnf_tablesにおけるnft_map_catchall_activate()関数の逆転したgenmaskチェックが修正されました。nft_map_catchall_activate()はcatchallでない対応関数であるnft_mapelem_activate()および論理的に必要な動作と比較すると、要素のアクティビティチェックが逆転していました。nft_map_catchall_activate()は失敗したトランザクション中に非アクティブ化されたcatchallマップ要素を再アクティブ化するために中止パスから呼び出されます。この関数はすでにアクティブな要素をスキップし（再アクティブ化不要）、非アクティブな要素を処理すべきですが、現行のコードはその逆を行い、非アクティブな要素をスキップしアクティブな要素を処理していました。正しい非catchall版のコールバックであるnft_mapelem_activate()と比較すると、バグのあるcatchall版は不適切な条件を用いています。この結果、DELSET操作が中止された場合、catchall要素に対してnft_setelem_data_activate()が呼ばれず、NFT_GOTO判定要素においてnft_data_hold()が呼ばれずにchain-use参照カウントが復元されません。そのため、各中止サイクルでchain-useが永久に減少し、ゼロになるとDELCHAINが成功してチェーンを解放しますが、catchall判定要素はまだそれを参照し続け、use-after-freeが発生します。この脆弱性はCONFIG_USER_NSとCONFIG_NF_TABLESが有効なディストリビューションにおいて、ユーザーネームスペースとnftablesを通じて非特権ユーザーがローカル権限昇格を行うために悪用可能です。修正では否定を除去し、チェックがnft_mapelem_activate()と一致するように変更し、アクティブな要素をスキップし非アクティブな要素を処理する動作に修正しました。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6838Linux Kernel 보안 업데이트 권고

Linux Kernel에서 발생하는 Use After Free 취약점(CVE-2026-23111) [1]~[7]

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: < 6.4, 5.15.200 ≤ 5.15.*, 6.1.163 ≤ 6.1.*, 6.6.124 ≤ 6.6.*, 6.12.70 ≤ 6.12.*, 6.18.10 ≤ 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 13 Feb 2026 · Last source change 8 Sept 2026, 08:44 UTC · CWE-416 · Use After Free

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-6170
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
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: removed vendor advisory: access.redhat.com/RHSA-2026:62639; removed vendor advisory: access.redhat.com/RHSA-2026:62641.
    Before
    patch: git.kernel.org/1444ff890b4653add12f734ffeffc173d42862dd · patch: git.kernel.org/42c574c1504aa089a0a142e4c13859327570473d · patch: git.kernel.org/8b68a45f9722f2babe9e7bad00aa74638addf081 · 6 more references
    After
    patch: git.kernel.org/1444ff890b4653add12f734ffeffc173d42862dd · patch: git.kernel.org/42c574c1504aa089a0a142e4c13859327570473d · patch: git.kernel.org/8b68a45f9722f2babe9e7bad00aa74638addf081 · 4 more references
    git.kernel.org ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:62639; added vendor advisory: access.redhat.com/RHSA-2026:62641.
    Before
    patch: git.kernel.org/1444ff890b4653add12f734ffeffc173d42862dd · patch: git.kernel.org/42c574c1504aa089a0a142e4c13859327570473d · patch: git.kernel.org/8b68a45f9722f2babe9e7bad00aa74638addf081 · 4 more references
    After
    patch: git.kernel.org/1444ff890b4653add12f734ffeffc173d42862dd · patch: git.kernel.org/42c574c1504aa089a0a142e4c13859327570473d · patch: git.kernel.org/8b68a45f9722f2babe9e7bad00aa74638addf081 · 6 more references
    git.kernel.org ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9; kernel-rt.src as a component of Red Hat Enterprise Linux 9 · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-55.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.70.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.70.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.70.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.70.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.70.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.70.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.70.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.70.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.70.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.70.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.70.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); and 1473 more
    After
    kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9; kernel-rt.src as a component of Red Hat Enterprise Linux 9 · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-55.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.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.70.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.70.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.70.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-debuginfo-0:6.12.0-55.70.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.70.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.70.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.70.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.70.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.70.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.70.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.70.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); kernel-devel-0:6.12.0-55.70.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0); and 1543 more
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    25aa2ad37c2162be1c0bc4fe6397f7e4c13f00f8 < 8c760ba4e36c750379d13569f23f5a6e185333f5; d60be2da67d172aecf866302c91ea11533eca4d9 < b9b6573421de51829f7ec1cce76d85f5f6fbbd7f; 628bd3e49cba1c066228e23d71a852c23e26da73 < 42c574c1504aa089a0a142e4c13859327570473d; 628bd3e49cba1c066228e23d71a852c23e26da73 < 1444ff890b4653add12f734ffeffc173d42862dd; 628bd3e49cba1c066228e23d71a852c23e26da73 < 8b68a45f9722f2babe9e7bad00aa74638addf081; 628bd3e49cba1c066228e23d71a852c23e26da73 < f41c5d151078c5348271ffaf8e7410d96f2d82f8; bc9f791d2593f17e39f87c6e2b3a36549a3705b1; 3c7ec098e3b588434a8b07ea9b5b36f04cef1f50 · Fixed: < 6.4; 5.15.200 ≤ 5.15.*; 6.1.163 ≤ 6.1.*; 6.6.124 ≤ 6.6.*; 6.12.70 ≤ 6.12.*; 6.18.10 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 25aa2ad37c2162be1c0bc4fe6397f7e4c13f00f8 < 8c760ba4e36c750379d13569f23f5a6e185333f5, d60be2da67d172aecf866302c91ea11533eca4d9 < b9b6573421de51829f7ec1cce76d85f5f6fbbd7f, 628bd3e49cba1c066228e23d71a852c23e26da73 < 42c574c1504aa089a0a142e4c13859327570473d, 628bd3e49cba1c066228e23d71a852c23e26da73 < 1444ff890b4653add12f734ffeffc173d42862dd, 628bd3e49cba1c066228e23d71a852c23e26da73 < 8b68a45f9722f2babe9e7bad00aa74638addf081, 628bd3e49cba1c066228e23d71a852c23e26da73 < f41c5d151078c5348271ffaf8e7410d96f2d82f8, bc9f791d2593f17e39f87c6e2b3a36549a3705b1, 3c7ec098e3b588434a8b07ea9b5b36f04cef1f50, a136b7942ad2a50de708f76ea299ccb45ac7a7f9, dc7cdf8cbcbf8b13de1df93f356ec04cdeef5c41, 5.15.121 < 5.15.200, 6.1.36 < 6.1.163, 4.19.316 < 4.20, 5.4.262 < 5.5, 5.10.188 < 5.11, 6.3.10 < 6.4, 6.4 · Fixed: Linux: < 6.4, 5.15.200 ≤ 5.15.*, 6.1.163 ≤ 6.1.*, 6.6.124 ≤ 6.6.*, 6.12.70 ≤ 6.12.*, 6.18.10 ≤ 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-6170↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗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-23111 · cve.blacktree.nl