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

net: mvpp2: limit XDP frame size to the RX buffer

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.50% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 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 20 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.

1 current
CVE-2026-53216 · CSAF 2.0 · revision 18 · interimSUSE Product Security TeamCVE-2026-53216
151 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks. Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-39307

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 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: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks. Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.

What

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks. Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: limit XDP frame size to the RX buffer mvpp2 has short and long BM pools, and short pool buffers can be smaller than PAGE_SIZE. The XDP path nevertheless initializes every xdp_buff with PAGE_SIZE as frame size. XDP helpers use frame_sz to validate tail growth and to derive the hard end of the data area. Advertising PAGE_SIZE for short buffers can let bpf_xdp_adjust_tail() grow a packet past the real allocation, corrupting memory or later tripping skb tailroom checks. Initialize the XDP buffer with bm_pool->frag_size so XDP tailroom matches the actual buffer backing the packet.

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

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

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-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-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-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=

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

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-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-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=

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

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

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

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-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-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=

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

d?id=CVE-2026-53130 Référence CVE CVE-2026-53131 https://www.cve.org/CVERecord?id=CVE-2026-53131 Référence CVE CVE-2026-53151 https://www.cve.org/CVERecord?id=CVE-2026-53151 Référence CVE CVE-2026-53174 https://www.cve.org/CVERecord?id=CVE-2026-53174 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 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-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 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-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=CVE-2026-53247 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53277 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53148 Référence CVE CVE-2026-53149 https://www.cve.org/CVERecord?id=CVE-2026-53149 Référence CVE CVE-2026-53150 https://www.cve.org/CVERecord?id=CVE-2026-53150 Référence CVE CVE-2026-53151 https://www.cve.org/CVERecord?id=CVE-2026-53151 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 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-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 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-53228 https://www.cve.org/CVERecord?id=CVE-2026-53228 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=CVE-2026-53247 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53156 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53168 https://www.cve.org/CVERecord?id=CVE-2026-53168 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53178 https://www.cve.org/CVERecord?id=CVE-2026-53178 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53194 https://www.cve.org/CVERecord?id=CVE-2026-53194 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 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-53229 https://www.cve.org/CVERecord?id=CVE-2026-53229 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53249 https://www.cve.org/CVERecord?id=CVE-2026-53249 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=CVE-2026-53258 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53263 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53194 Référence CVE CVE-2026-53195 https://www.cve.org/CVERecord?id=CVE-2026-53195 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53202 https://www.cve.org/CVERecord?id=CVE-2026-53202 Référence CVE CVE-2026-53203 https://www.cve.org/CVERecord?id=CVE-2026-53203 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-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-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-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53229 https://www.cve.org/CVERecord?id=CVE-2026-53229 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53239 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-53196 Référence CVE CVE-2026-53198 https://www.cve.org/CVERecord?id=CVE-2026-53198 Référence CVE CVE-2026-53199 https://www.cve.org/CVERecord?id=CVE-2026-53199 Référence CVE CVE-2026-53207 https://www.cve.org/CVERecord?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=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました:net: mvpp2: XDPフレームサイズをRXバッファに制限mvpp2にはshortとlongのBMプールがあり、shortプールのバッファはPAGE_SIZEより小さい場合があります。にもかかわらず、XDPパスはすべてのxdp_buffをフレームサイズとしてPAGE_SIZEで初期化しています。XDPヘルパーはframe_szを用いてテイルの拡張を検証し、データ領域の厳密な終端を導出します。shortバッファに対してPAGE_SIZEを提示すると、bpf_xdp_adjust_tail()が実際の割り当てを超えてパケットを拡張できてしまい、メモリ破壊を招いたり、後でskbのテイルルーム検査に引っかかったりする可能性があります。XDPバッファをbm_pool->frag_sizeで初期化し、XDPのテイルルームがパケットを支える実際のバッファと一致するようにします。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.9, 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 5 Aug 2026, 12:34 UTC · CWE not yet assigned

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

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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-39307↗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-53216 · cve.blacktree.nl