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

bpf: Explicitly check accesses to bpf_sock_addr

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.24% 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: Manual assessmentRemediation target: Manual assessment

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

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2025-40078 · CSAF 2.0 · revision 53 · interimSUSE Product Security TeamCVE-2025-40078
253 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.
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: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.
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-2025-36450

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.

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

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. 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: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.

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 the affected interface may attempt exploitation when the stated preconditions are met. 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: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.

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 the affected interface may attempt exploitation when the stated preconditions are met. 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-36450Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.

Official EUVD record ↗
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-2431Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um beliebigen Code auszuführen, privilegierten Zugriff zu erlangen, sensible Informationen zu stehlen oder betroffene Systeme funktionsunfähig zu machen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251029Security Bulletin 29 Oct 2025

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

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

25-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025

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

d?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40043 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40049 https://www.cve.org/CVERecord?id=CVE-2025-40049 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40043 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40049 https://www.cve.org/CVERecord?id=CVE-2025-40049 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 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-40069 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40072 https://www.cve.org/CVERecord?id=CVE-2025-40072 Référence CVE CVE-2025-40073 https://www.cve.org/CVERecord?id=CVE-2025-40073 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40076 https://www.cve.org/CVERecord?id=CVE-2025-40076 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40086 https://www.cve.org/CVERecord?id=CVE-2025-40086 Référence CVE CVE-2025-40087 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-40043 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40049 https://www.cve.org/CVERecord?id=CVE-2025-40049 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=CVE-2025-40105 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40043 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40049 https://www.cve.org/CVERecord?id=CVE-2025-40049 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=CVE-2025-40105 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40043 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40049 https://www.cve.org/CVERecord?id=CVE-2025-40049 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40094 https://www.cve.org/CVERecord?id=CVE-2025-40094 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=CVE-2025-40105 Référence CVE CVE-2025-40106 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-40069 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40072 https://www.cve.org/CVERecord?id=CVE-2025-40072 Référence CVE CVE-2025-40073 https://www.cve.org/CVERecord?id=CVE-2025-40073 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40076 https://www.cve.org/CVERecord?id=CVE-2025-40076 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40086 https://www.cve.org/CVERecord?id=CVE-2025-40086 Référence CVE CVE-2025-40087 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-40069 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40072 https://www.cve.org/CVERecord?id=CVE-2025-40072 Référence CVE CVE-2025-40073 https://www.cve.org/CVERecord?id=CVE-2025-40073 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40076 https://www.cve.org/CVERecord?id=CVE-2025-40076 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40079 https://www.cve.org/CVERecord?id=CVE-2025-40079 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40086 https://www.cve.org/CVERecord?id=CVE-2025-40086 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40030 Référence CVE CVE-2025-40035 https://www.cve.org/CVERecord?id=CVE-2025-40035 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40049 https://www.cve.org/CVERecord?id=CVE-2025-40049 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=CVE-2025-40105 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40109 https://www.cve.org/CVERecord?id=CVE-2025-40109 Référence CVE CVE-2025-40111 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-40049 Référence CVE CVE-2025-40051 https://www.cve.org/CVERecord?id=CVE-2025-40051 Référence CVE CVE-2025-40052 https://www.cve.org/CVERecord?id=CVE-2025-40052 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40091 https://www.cve.org/CVERecord?id=CVE-2025-40091 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40049 Référence CVE CVE-2025-40051 https://www.cve.org/CVERecord?id=CVE-2025-40051 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40049 Référence CVE CVE-2025-40051 https://www.cve.org/CVERecord?id=CVE-2025-40051 Référence CVE CVE-2025-40052 https://www.cve.org/CVERecord?id=CVE-2025-40052 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Gestion détaillée du document le 28 novembre 2025 Version init

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

d?id=CVE-2025-40049 Référence CVE CVE-2025-40051 https://www.cve.org/CVERecord?id=CVE-2025-40051 Référence CVE CVE-2025-40052 https://www.cve.org/CVERecord?id=CVE-2025-40052 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40091 https://www.cve.org/CVERecord?id=CVE-2025-40091 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40049 Référence CVE CVE-2025-40051 https://www.cve.org/CVERecord?id=CVE-2025-40051 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40084 https://www.cve.org/CVERecord?id=CVE-2025-40084 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40092 https://www.cve.org/CVERecord?id=CVE-2025-40092 Référence CVE CVE-2025-40093 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40049 Référence CVE CVE-2025-40051 https://www.cve.org/CVERecord?id=CVE-2025-40051 Référence CVE CVE-2025-40052 https://www.cve.org/CVERecord?id=CVE-2025-40052 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40078 https://www.cve.org/CVERecord?id=CVE-2025-40078 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40085 https://www.cve.org/CVERecord?id=CVE-2025-40085 Référence CVE CVE-2025-40087 https://www.cve.org/CVERecord?id=CVE-2025-40087 Référence CVE CVE-2025-40088 https://www.cve.org/CVERecord?id=CVE-2025-40088 Référence CVE CVE-2025-40091 https://www.cve.org/CVERecord?id=CVE-2025-40091 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0941Multiples vulnérabilités dans les produits Microsoft

CVE-2025-40057 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40060 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40061 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40064 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40065 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40068 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40071 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40074 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40075 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40077 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40078 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40079 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40080 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40081 du 29 octobre 2025 Une gestion de version détaillée se trouve à la fin de ce document. Risque Non spécifié par l'éditeur Systèmes affectés azl3 bind 9.20.11-1 azl3 binutils 2.41-9 azl3 coredns 1.11.4-10 azl3 kata-containers-cc 3.15.0.aks0-5 azl3 kernel 6.6.104.2-4 cbl2 bind 9.16.50-2 cbl2 binutils 2.37-17 cbl2 coredns 1.11.1-22 versions antérieures à 1.11.1-24 Résumé De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles p

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.18, 5.4.301 ≤ 5.4.*, 5.10.246 ≤ 5.10.*, 5.15.195 ≤ 5.15.*, 6.1.156 ≤ 6.1.*, 6.6.112 ≤ 6.6.*, 6.12.53 ≤ 6.12.*, 6.17.3 ≤ 6.17.*, 6.18 ≤ *
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 28 Oct 2025 · Last source change 8 Sept 2026, 08:42 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-36450
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CVSS base score, 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
    1cedee13d25ab118d325f95588c1a084e9317229 < de44cdc50d2dce8718cb57deddf9cf1be9a7759f; 1cedee13d25ab118d325f95588c1a084e9317229 < 76e04bbb4296fb6eac084dbfc27e02ccc744db3e; 1cedee13d25ab118d325f95588c1a084e9317229 < 6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec; 1cedee13d25ab118d325f95588c1a084e9317229 < 4f00858cd9bbbdf67159e28b85a8ca9e77c83622; 1cedee13d25ab118d325f95588c1a084e9317229 < cdeafacb4f9ff261a96baef519e29480fd7b1019; 1cedee13d25ab118d325f95588c1a084e9317229 < fe9d33f0470350558cb08cecb54cf2267b3a45d2; 1cedee13d25ab118d325f95588c1a084e9317229 < ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69; 1cedee13d25ab118d325f95588c1a084e9317229 < 6fabca2fc94d33cdf7ec102058983b086293395f · Fixed: < 4.18; 5.4.301 ≤ 5.4.*; 5.10.246 ≤ 5.10.*; 5.15.195 ≤ 5.15.*; 6.1.156 ≤ 6.1.*; 6.6.112 ≤ 6.6.*; 6.12.53 ≤ 6.12.*; 6.17.3 ≤ 6.17.*
    After
    Linux: 1cedee13d25ab118d325f95588c1a084e9317229 < de44cdc50d2dce8718cb57deddf9cf1be9a7759f, 1cedee13d25ab118d325f95588c1a084e9317229 < 76e04bbb4296fb6eac084dbfc27e02ccc744db3e, 1cedee13d25ab118d325f95588c1a084e9317229 < 6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec, 1cedee13d25ab118d325f95588c1a084e9317229 < 4f00858cd9bbbdf67159e28b85a8ca9e77c83622, 1cedee13d25ab118d325f95588c1a084e9317229 < cdeafacb4f9ff261a96baef519e29480fd7b1019, 1cedee13d25ab118d325f95588c1a084e9317229 < fe9d33f0470350558cb08cecb54cf2267b3a45d2, 1cedee13d25ab118d325f95588c1a084e9317229 < ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69, 1cedee13d25ab118d325f95588c1a084e9317229 < 6fabca2fc94d33cdf7ec102058983b086293395f, 4.18 · Fixed: Linux: < 4.18, 5.4.301 ≤ 5.4.*, 5.10.246 ≤ 5.10.*, 5.15.195 ≤ 5.15.*, 6.1.156 ≤ 6.1.*, 6.6.112 ≤ 6.6.*, 6.12.53 ≤ 6.12.*, 6.17.3 ≤ 6.17.*, 6.18 ≤ *
    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-2025-36450↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-40078 · cve.blacktree.nl