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

netfilter: x_tables: avoid leaking percpu counter pointers

Linux · Linux

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 2026

Evidence used

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

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-53219 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-53219
314 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.
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-39310

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.

Why

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

How

An attacker operating through 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: netfilter: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.

Why

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

How

An attacker operating through 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 → vulnerable operation → 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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-39310Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: avoid leaking percpu counter pointers The native and compat get-entries paths copy the fixed rule entry header from the kernelized rule blob to userspace before overwriting the entry's counter fields with a sanitized counter snapshot. On SMP kernels, entry->counters.pcnt contains the percpu allocation address used by x_tables rule counters. A caller can provide a userspace buffer that faults during the initial fixed-header copy after pcnt has been copied but before the later sanitized counter copy runs. The syscall then returns -EFAULT while leaving the raw percpu pointer in userspace. Copy only the fixed entry prefix before counters from the kernelized rule blob, then copy the sanitized counter snapshot into the counter field. Apply this ordering to the IPv4, IPv6, and ARP native and compat get-entries implementations so a fault cannot expose the internal percpu counter pointer.

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

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

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

d?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53222 https://www.cve.org/CVERecord?id=CVE-2026-53222 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53111 Référence CVE CVE-2026-53114 https://www.cve.org/CVERecord?id=CVE-2026-53114 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53129 https://www.cve.org/CVERecord?id=CVE-2026-53129 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=CVE-2026-53142 Référence CVE CVE-2026-53154 https://www.cve.org/CVERecord?id=CVE-2026-53154 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=CVE-2026-53163 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53269 https://www.cve.org/CVERecord?id=CVE-2026-53269 Référence CVE CVE-2026-53284 https://www.cve.org/CVERecord?id=CVE-2026-53284 Référence CVE CVE-2026-53291 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52977 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53061 https://www.cve.org/CVERecord?id=CVE-2026-53061 Référence CVE CVE-2026-53077 https://www.cve.org/CVERecord?id=CVE-2026-53077 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53149 https://www.cve.org/CVERecord?id=CVE-2026-53149 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=CVE-2026-53163 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53264 https://www.cve.org/CVERecord?id=CVE-2026-53264 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53309 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53222 https://www.cve.org/CVERecord?id=CVE-2026-53222 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53111 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=CVE-2026-53142 Référence CVE CVE-2026-53154 https://www.cve.org/CVERecord?id=CVE-2026-53154 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=CVE-2026-53163 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53263 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53209 Référence CVE CVE-2026-53210 https://www.cve.org/CVERecord?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53222 https://www.cve.org/CVERecord?id=CVE-2026-53222 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53210 Référence CVE CVE-2026-53211 https://www.cve.org/CVERecord?id=CVE-2026-53211 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53214 https://www.cve.org/CVERecord?id=CVE-2026-53214 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53222 https://www.cve.org/CVERecord?id=CVE-2026-53222 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53111 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=CVE-2026-53142 Référence CVE CVE-2026-53154 https://www.cve.org/CVERecord?id=CVE-2026-53154 Référence CVE CVE-2026-53163 https://www.cve.org/CVERecord?id=CVE-2026-53163 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?id=CVE-2026-53207 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53220 https://www.cve.org/CVERecord?id=CVE-2026-53220 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53263 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53207 Référence CVE CVE-2026-53208 https://www.cve.org/CVERecord?id=CVE-2026-53208 Référence CVE CVE-2026-53209 https://www.cve.org/CVERecord?id=CVE-2026-53209 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53213 https://www.cve.org/CVERecord?id=CVE-2026-53213 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53217 https://www.cve.org/CVERecord?id=CVE-2026-53217 Référence CVE CVE-2026-53218 https://www.cve.org/CVERecord?id=CVE-2026-53218 Référence CVE CVE-2026-53219 https://www.cve.org/CVERecord?id=CVE-2026-53219 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53223 https://www.cve.org/CVERecord?id=CVE-2026-53223 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53238 https://www.cve.org/CVERecord?id=CVE-2026-53238 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0812Multiples vulnérabilités dans Microsoft Azure Linux

ulletin de sécurité Microsoft CVE-2026-53194 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53196 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53199 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53207 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53209 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53213 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53214 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53215 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53217 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53218 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53219 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53221 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53225 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53227 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53228 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53230 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53236 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53237 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53238 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53239 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53242 du 27 juin 2026 Bulletin de s

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022332LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、次の脆弱性が修正されました:netfilter: x_tables: per-CPUカウンタポインタの漏えいを回避ネイティブおよび compat の get-entries パスは、エントリのカウンタフィールドをサニタイズ済みのカウンタスナップショットで上書きする前に、カーネル内のルールブロブから固定ルールエントリヘッダをユーザー空間へコピーします。SMPカーネルでは、entry->counters.pcnt には x_tables のルールカウンタで使用される per-CPU の割り当てアドレスが含まれます。呼び出し側は、pcnt がコピーされた後で、後段のサニタイズ済みカウンタのコピーが実行される前というタイミングで、最初の固定ヘッダのコピー中にフォールトするユーザー空間バッファを渡すことができます。この場合、システムコールは -EFAULT を返しますが、生の per-CPU ポインタがユーザー空間に残ってしまいます。対策として、カーネル内のルールブロブからはカウンタより前の固定エントリのプレフィックスだけをコピーし、その後にサニタイズ済みのカウンタスナップショットをカウンタフィールドへコピーします。この順序を IPv4、IPv6、ARP のネイティブおよび compat の get-entries 実装に適用し、フォールトにより内部の per-CPU カウンタポインタが露出しないようにします。

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: < 4.2, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
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 25 Jun 2026 · Last source change 8 Sept 2026, 08:50 UTC · CWE not yet assigned

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    71ae0dff02d756e4d2ca710b79f2ff5390029a5f < b74ba3343eb44b2cbf7e9665918c287df1d52ebb; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < 0b35dc8527ccc16b7dc34e8a3164313e68cd4e45; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < b28e2fcad3db7e8687b15bc20bced26b5b7c920e; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < a0d16941adf3a501956d74aefd8d6e217906e79c; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < 8d67e42ad3b1a95a152541015a07110e06992d6c; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < 08a3e218064db11f154ad9ad5541751ea7f34ebe; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < fb0521aff1e10e300d89725cc439d3ea74c828c5; 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < f7f2fbb0e893a0238dc464f8d8c0f5609bec584f · Fixed: < 4.2; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.143 ≤ 6.6.*; 6.12.94 ≤ 6.12.*; 6.18.36 ≤ 6.18.*; 7.0.13 ≤ 7.0.*
    After
    Linux: 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < b74ba3343eb44b2cbf7e9665918c287df1d52ebb, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < 0b35dc8527ccc16b7dc34e8a3164313e68cd4e45, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < b28e2fcad3db7e8687b15bc20bced26b5b7c920e, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < a0d16941adf3a501956d74aefd8d6e217906e79c, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < 8d67e42ad3b1a95a152541015a07110e06992d6c, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < 08a3e218064db11f154ad9ad5541751ea7f34ebe, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < fb0521aff1e10e300d89725cc439d3ea74c828c5, 71ae0dff02d756e4d2ca710b79f2ff5390029a5f < f7f2fbb0e893a0238dc464f8d8c0f5609bec584f, 4.2 · Fixed: Linux: < 4.2, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
    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-39310↗Vendor CSAF · SUSE Product Security Team↗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-53219 · cve.blacktree.nl