BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-38572High confidence

ipv6: reject malicious packets in ipv6_gso_segment()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 21 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.

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

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2025-38572 · CSAF 2.0 · revision 63 · interimSUSE Product Security TeamCVE-2025-38572
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: ipv6: reject malicious packets in ipv6_gso_segment() syzbot was able to craft a packet with very long IPv6 extension headers leading to an overflow of skb->transport_header. This 16bit field has a limited range. Add skb_reset_transport_header_careful() helper and use it from ipv6_gso_segment() WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline] WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Modules linked in: CPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline] RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Call Trace: skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110 skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 __skb_gso_segment+0x342/0x510 net/core/gso.c:124 skb_gso_segment include/net/gso.h:83 [inline] validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950 validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000 sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329 __dev_xmit_skb net/core/dev.c:4102 [inline] __dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679
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-2025-26102

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 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: ipv6: reject malicious packets in ipv6_gso_segment() syzbot was able to craft a packet with very long IPv6 extension headers leading to an overflow of skb->transport_header. This 16bit field has a limited range. Add skb_reset_transport_header_careful() helper and use it from ipv6_gso_segment() WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline] WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Modules linked in: CPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline] RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Call Trace: <TASK> skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110 skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 __skb_gso_segment+0x342/0x510 net/core/gso.c:124 skb_gso_segment include/net/gso.h:83 [inline] validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950 validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000 sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329 __dev_xmit_skb net/core/dev.c:4102 [inline] __dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679

What

In the Linux kernel, the following vulnerability has been resolved: ipv6: reject malicious packets in ipv6_gso_segment() syzbot was able to craft a packet with very long IPv6 extension headers leading to an overflow of skb->transport_header. This 16bit field has a limited range. Add skb_reset_transport_header_careful() helper and use it from ipv6_gso_segment() WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline] WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Modules linked in: CPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline] RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Call Trace: <TASK> skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110 skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 __skb_gso_segment+0x342/0x510 net/core/gso.c:124 skb_gso_segment include/net/gso.h:83 [inline] validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950 validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000 sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329 __dev_xmit_skb net/core/dev.c:4102 [inline] __dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679

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: ipv6: reject malicious packets in ipv6_gso_segment() syzbot was able to craft a packet with very long IPv6 extension headers leading to an overflow of skb->transport_header. This 16bit field has a limited range. Add skb_reset_transport_header_careful() helper and use it from ipv6_gso_segment() WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 skb_reset_transport_header include/linux/skbuff.h:3032 [inline] WARNING: CPU: 0 PID: 5871 at ./include/linux/skbuff.h:3032 ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Modules linked in: CPU: 0 UID: 0 PID: 5871 Comm: syz-executor211 Not tainted 6.16.0-rc6-syzkaller-g7abc678e3084 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:skb_reset_transport_header include/linux/skbuff.h:3032 [inline] RIP: 0010:ipv6_gso_segment+0x15e2/0x21e0 net/ipv6/ip6_offload.c:151 Call Trace: <TASK> skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 nsh_gso_segment+0x54a/0xe10 net/nsh/nsh.c:110 skb_mac_gso_segment+0x31c/0x640 net/core/gso.c:53 __skb_gso_segment+0x342/0x510 net/core/gso.c:124 skb_gso_segment include/net/gso.h:83 [inline] validate_xmit_skb+0x857/0x11b0 net/core/dev.c:3950 validate_xmit_skb_list+0x84/0x120 net/core/dev.c:4000 sch_direct_xmit+0xd3/0x4b0 net/sched/sch_generic.c:329 __dev_xmit_skb net/core/dev.c:4102 [inline] __dev_queue_xmit+0x17b6/0x3a70 net/core/dev.c:4679

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: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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory ↗
BSI · German · WID-SEC-2025-1869Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-53164 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-38085 https://www.cve.org/CVERecord?id=CVE-2025-38085 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38554 https://www.cve.org/CVERecord?id=CVE-2025-38554 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38608 https://www.cve.org/CVERecord?id=CVE-2025-38608 Référence CVE CVE-2025-38616 https://www.cve.org/CVERecord?id=CVE-2025-38616 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=CVE-2025-38617 Référence CVE CVE-2025-38618 https://www.cve.org/CVERecord?id=CVE-2025-38618 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38352 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38546 https://www.cve.org/CVERecord?id=CVE-2025-38546 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38608 https://www.cve.org/CVERecord?id=CVE-2025-38608 Référence CVE CVE-2025-38617 https://www.cve.org/CVERecord?id=CVE-2025-38617 Référence CVE CVE-2025-38618 https://www.cve.org/CVERecord?id=CVE-2025-38618 Référence CVE CVE-2025-38644 https://www.cve.org/CVERecord?id=CVE-2025-38644 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Gestion détaillée du document le 23 janvier 2026 Version initi

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

d?id=CVE-2025-38562 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38567 https://www.cve.org/CVERecord?id=CVE-2025-38567 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38570 https://www.cve.org/CVERecord?id=CVE-2025-38570 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38573 https://www.cve.org/CVERecord?id=CVE-2025-38573 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38575 https://www.cve.org/CVERecord?id=CVE-2025-38575 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38557 Référence CVE CVE-2025-38559 https://www.cve.org/CVERecord?id=CVE-2025-38559 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38564 https://www.cve.org/CVERecord?id=CVE-2025-38564 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38573 https://www.cve.org/CVERecord?id=CVE-2025-38573 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38562 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38567 https://www.cve.org/CVERecord?id=CVE-2025-38567 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38570 https://www.cve.org/CVERecord?id=CVE-2025-38570 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38573 https://www.cve.org/CVERecord?id=CVE-2025-38573 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38562 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38567 https://www.cve.org/CVERecord?id=CVE-2025-38567 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38570 https://www.cve.org/CVERecord?id=CVE-2025-38570 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38573 https://www.cve.org/CVERecord?id=CVE-2025-38573 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38575 https://www.cve.org/CVERecord?id=CVE-2025-38575 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53373 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-38351 https://www.cve.org/CVERecord?id=CVE-2025-38351 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38550 https://www.cve.org/CVERecord?id=CVE-2025-38550 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38614 https://www.cve.org/CVERecord?id=CVE-2025-38614 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=CVE-2025-39751 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39849 https://www.cve.org/CVERecord?id=CVE-2025-39849 Gestion détaillée du document le 24 octobre 2025 Version initi

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=CVE-2025-38585 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=CVE-2025-38585 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38552 Référence CVE CVE-2025-38553 https://www.cve.org/CVERecord?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38569 https://www.cve.org/CVERecord?id=CVE-2025-38569 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38574 https://www.cve.org/CVERecord?id=CVE-2025-38574 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38577 https://www.cve.org/CVERecord?id=CVE-2025-38577 Référence CVE CVE-2025-38578 https://www.cve.org/CVERecord?id=CVE-2025-38578 Référence CVE CVE-2025-38579 https://www.cve.org/CVERecord?id=CVE-2025-38579 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38550 Référence CVE CVE-2025-38553 https://www.cve.org/CVERecord?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=CVE-2025-38585 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=CVE-2025-38587 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38550 Référence CVE CVE-2025-38553 https://www.cve.org/CVERecord?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=CVE-2025-38585 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=CVE-2025-38587 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=CVE-2025-38585 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=CVE-2025-38587 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38550 Référence CVE CVE-2025-38553 https://www.cve.org/CVERecord?id=CVE-2025-38553 Référence CVE CVE-2025-38555 https://www.cve.org/CVERecord?id=CVE-2025-38555 Référence CVE CVE-2025-38560 https://www.cve.org/CVERecord?id=CVE-2025-38560 Référence CVE CVE-2025-38563 https://www.cve.org/CVERecord?id=CVE-2025-38563 Référence CVE CVE-2025-38565 https://www.cve.org/CVERecord?id=CVE-2025-38565 Référence CVE CVE-2025-38566 https://www.cve.org/CVERecord?id=CVE-2025-38566 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38571 https://www.cve.org/CVERecord?id=CVE-2025-38571 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38576 https://www.cve.org/CVERecord?id=CVE-2025-38576 Référence CVE CVE-2025-38581 https://www.cve.org/CVERecord?id=CVE-2025-38581 Référence CVE CVE-2025-38582 https://www.cve.org/CVERecord?id=CVE-2025-38582 Référence CVE CVE-2025-38583 https://www.cve.org/CVERecord?id=CVE-2025-38583 Référence CVE CVE-2025-38585 https://www.cve.org/CVERecord?id=CVE-2025-38585 Référence CVE CVE-2025-38587 https://www.cve.org/CVERecord?id=CVE-2025-38587 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=CVE-2025-38588 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-024481Debian等の複数ベンダの製品における不特定の脆弱性

Linuxカーネルでは、ipv6_gso_segment関数が悪意のあるパケットを拒否できない脆弱性が修正されました。この脆弱性は、非常に長いIPv6拡張ヘッダーを持つパケットによってskb->transport_headerがオーバーフローし、不正なメモリアクセスが発生することが原因でした。新たにskb_reset_transport_header_careful関数を導入することで、安全でないパケットの処理を防止し、この脆弱性に対応しています。

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: < 3.8, 5.4.297 ≤ 5.4.*, 5.10.241 ≤ 5.10.*, 5.15.190 ≤ 5.15.*, 6.1.148 ≤ 6.1.*, 6.6.102 ≤ 6.6.*, 6.12.42 ≤ 6.12.*, 6.15.10 ≤ 6.15.*, 6.16.1 ≤ 6.16.*, 6.17 ≤ *
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 19 Aug 2025 · Last source change 5 Aug 2026, 12:03 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-2025-26102
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
    SLES 15 SP1 CHOST Images for Amazon EC2; SLES 15 SP2 CHOST Images for Amazon EC2; SLES 15 SP3 CHOST Images for Amazon EC2; SLES 15 SP4 CHOST Images for Amazon EC2; SLES 15 SP5 CHOST Images for Amazon EC2; SLES 15 SP1 CHOST Images for Google; SLES 15 SP2 CHOST Images for Google; SLES 15 SP3 CHOST Images for Google; SLES 15 SP4 CHOST Images for Google; SLES 15 SP5 CHOST Images for Google; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure · Fixed: kernel-obs-build-6.12.0-160000.6.1 as component of SUSE Linux Micro Extras 6.2; kernel-syms-6.12.0-160000.6.1 as component of SUSE Linux Micro Extras 6.2
    After
    SUSE Linux Micro Extras 6.2:kernel-obs-build; SUSE Linux Micro Extras 6.2:kernel-syms; SLES 15 SP1 CHOST Images for Amazon EC2; SLES 15 SP2 CHOST Images for Amazon EC2; SLES 15 SP3 CHOST Images for Amazon EC2; SLES 15 SP4 CHOST Images for Amazon EC2; SLES 15 SP5 CHOST Images for Amazon EC2; SLES 15 SP1 CHOST Images for Google; SLES 15 SP2 CHOST Images for Google; SLES 15 SP3 CHOST Images for Google; SLES 15 SP4 CHOST Images for Google; SLES 15 SP5 CHOST Images for Google; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure
    SUSE Product Security Team ↗
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-2025-26102↗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-2025-38572 · cve.blacktree.nl