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

bpf: Enforce expected_attach_type for tailcall compatibility

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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 14 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.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
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-124960

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_DEVMAP nor BPF_XDP_CPUMAP. progA calls into a slot of a tailcall map it owns. progB's expected_attach_type must be BPF_XDP_DEVMAP to pass xdp_is_valid_access() validation. The program returns struct xdp_md's egress_ifindex, and the latter is only allowed to be accessed under mentioned expected_attach_type. progB is then inserted into the tailcall which progA calls. The underlying issue goes beyond XDP though. Another example are programs of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well as sock_addr_func_proto() have different logic depending on the programs' expected_attach_type. Similarly, a program attached to BPF_CGROUP_INET4_GETPEERNAME should not be allowed doing a tailcall into a program which calls bpf_bind() out of BPF which is only enabled for BPF_CGROUP_INET4_CONNECT. In short, specifying expected_attach_type allows to open up additional functionality or restrictions beyond what the basic bpf_prog_type enables. The use of tailcalls must not violate these constraints. Fix it by enforcing expected_attach_type in __bpf_prog_map_compatible(). Note that we only enforce this for tailcall maps, but not for BPF devmaps or cpumaps: There, the programs are invoked through dev_map_bpf_prog_run*() and cpu_map_bpf_prog_run*() which set up a new environment / context and therefore these situations are not prone to this issue.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_DEVMAP nor BPF_XDP_CPUMAP. progA calls into a slot of a tailcall map it owns. progB's expected_attach_type must be BPF_XDP_DEVMAP to pass xdp_is_valid_access() validation. The program returns struct xdp_md's egress_ifindex, and the latter is only allowed to be accessed under mentioned expected_attach_type. progB is then inserted into the tailcall which progA calls. The underlying issue goes beyond XDP though. Another example are programs of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well as sock_addr_func_proto() have different logic depending on the programs' expected_attach_type. Similarly, a program attached to BPF_CGROUP_INET4_GETPEERNAME should not be allowed doing a tailcall into a program which calls bpf_bind() out of BPF which is only enabled for BPF_CGROUP_INET4_CONNECT. In short, specifying expected_attach_type allows to open up additional functionality or restrictions beyond what the basic bpf_prog_type enables. The use of tailcalls must not violate these constraints. Fix it by enforcing expected_attach_type in __bpf_prog_map_compatible(). Note that we only enforce this for tailcall maps, but not for BPF devmaps or cpumaps: There, the programs are invoked through dev_map_bpf_prog_run*() and cpu_map_bpf_prog_run*() which set up a new environment / context and therefore these situations are not prone to this issue.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_DEVMAP nor BPF_XDP_CPUMAP. progA calls into a slot of a tailcall map it owns. progB's expected_attach_type must be BPF_XDP_DEVMAP to pass xdp_is_valid_access() validation. The program returns struct xdp_md's egress_ifindex, and the latter is only allowed to be accessed under mentioned expected_attach_type. progB is then inserted into the tailcall which progA calls. The underlying issue goes beyond XDP though. Another example are programs of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well as sock_addr_func_proto() have different logic depending on the programs' expected_attach_type. Similarly, a program attached to BPF_CGROUP_INET4_GETPEERNAME should not be allowed doing a tailcall into a program which calls bpf_bind() out of BPF which is only enabled for BPF_CGROUP_INET4_CONNECT. In short, specifying expected_attach_type allows to open up additional functionality or restrictions beyond what the basic bpf_prog_type enables. The use of tailcalls must not violate these constraints. Fix it by enforcing expected_attach_type in __bpf_prog_map_compatible(). Note that we only enforce this for tailcall maps, but not for BPF devmaps or cpumaps: There, the programs are invoked through dev_map_bpf_prog_run*() and cpu_map_bpf_prog_run*() which set up a new environment / context and therefore these situations are not prone to this issue.

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: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_DEVMAP nor BPF_XDP_CPUMAP. progA calls into a slot of a tailcall map it owns. progB's expected_attach_type must be BPF_XDP_DEVMAP to pass xdp_is_valid_access() validation. The program returns struct xdp_md's egress_ifindex, and the latter is only allowed to be accessed under mentioned expected_attach_type. progB is then inserted into the tailcall which progA calls. The underlying issue goes beyond XDP though. Another example are programs of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well as sock_addr_func_proto() have different logic depending on the programs' expected_attach_type. Similarly, a program attached to BPF_CGROUP_INET4_GETPEERNAME should not be allowed doing a tailcall into a program which calls bpf_bind() out of BPF which is only enabled for BPF_CGROUP_INET4_CONNECT. In short, specifying expected_attach_type allows to open up additional functionality or restrictions beyond what the basic bpf_prog_type enables. The use of tailcalls must not violate these constraints. Fix it by enforcing expected_attach_type in __bpf_prog_map_compatible(). Note that we only enforce this for tailcall maps, but not for BPF devmaps or cpumaps: There, the programs are invoked through dev_map_bpf_prog_run*() and cpu_map_bpf_prog_run*() which set up a new environment / context and therefore these situations are not prone to this issue.

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.

ENISA EUVD · EUVD-2025-124960Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_DEVMAP nor BPF_XDP_CPUMAP. progA calls into a slot of a tailcall map it owns. progB's expected_attach_type must be BPF_XDP_DEVMAP to pass xdp_is_valid_access() validation. The program returns struct xdp_md's egress_ifindex, and the latter is only allowed to be accessed under mentioned expected_attach_type. progB is then inserted into the tailcall which progA calls. The underlying issue goes beyond XDP though. Another example are programs of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well as sock_addr_func_proto() have different logic depending on the programs' expected_attach_type. Similarly, a program attached to BPF_CGROUP_INET4_GETPEERNAME should not be allowed doing a tailcall into a program which calls bpf_bind() out of BPF which is only enabled for BPF_CGROUP_INET4_CONNECT. In short, specifying expected_attach_type allows to open up additional functionality or restrictions beyond what the basic bpf_prog_type enables. The use of tailcalls must not violate these constraints. Fix it by enforcing expected_attach_type in __bpf_prog_map_compatible(). Note that we only enforce this for tailcall maps, but not for BPF devmaps or cpumaps: There, the programs are invoked through dev_map_bpf_prog_run*() and cpu_map_bpf_prog_run*() which set up a new environment / context and therefore these situations are not prone to this issue.

Official EUVD record ↗
BSI · German · WID-SEC-2025-2579Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251119Security Bulletin 19 Nov 2025

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

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

d?id=CVE-2025-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40112 https://www.cve.org/CVERecord?id=CVE-2025-40112 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 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-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40112 https://www.cve.org/CVERecord?id=CVE-2025-40112 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 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-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40112 https://www.cve.org/CVERecord?id=CVE-2025-40112 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 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-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40112 https://www.cve.org/CVERecord?id=CVE-2025-40112 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40033 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40106 https://www.cve.org/CVERecord?id=CVE-2025-40106 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40178 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-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40112 https://www.cve.org/CVERecord?id=CVE-2025-40112 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40095 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40107 https://www.cve.org/CVERecord?id=CVE-2025-40107 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40146 https://www.cve.org/CVERecord?id=CVE-2025-40146 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40095 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40100 https://www.cve.org/CVERecord?id=CVE-2025-40100 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40104 https://www.cve.org/CVERecord?id=CVE-2025-40104 Référence CVE CVE-2025-40107 https://www.cve.org/CVERecord?id=CVE-2025-40107 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40137 https://www.cve.org/CVERecord?id=CVE-2025-40137 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40146 https://www.cve.org/CVERecord?id=CVE-2025-40146 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40164 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40107 Référence CVE CVE-2025-40109 https://www.cve.org/CVERecord?id=CVE-2025-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40147 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40107 Référence CVE CVE-2025-40109 https://www.cve.org/CVERecord?id=CVE-2025-40109 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40111 https://www.cve.org/CVERecord?id=CVE-2025-40111 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40132 https://www.cve.org/CVERecord?id=CVE-2025-40132 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40136 https://www.cve.org/CVERecord?id=CVE-2025-40136 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40140 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-40113 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40117 https://www.cve.org/CVERecord?id=CVE-2025-40117 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40119 https://www.cve.org/CVERecord?id=CVE-2025-40119 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40122 https://www.cve.org/CVERecord?id=CVE-2025-40122 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40130 https://www.cve.org/CVERecord?id=CVE-2025-40130 Référence CVE CVE-2025-40131 https://www.cve.org/CVERecord?id=CVE-2025-40131 Référence CVE CVE-2025-40132 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-40113 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40117 https://www.cve.org/CVERecord?id=CVE-2025-40117 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40119 https://www.cve.org/CVERecord?id=CVE-2025-40119 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40122 https://www.cve.org/CVERecord?id=CVE-2025-40122 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40130 https://www.cve.org/CVERecord?id=CVE-2025-40130 Référence CVE CVE-2025-40131 https://www.cve.org/CVERecord?id=CVE-2025-40131 Référence CVE CVE-2025-40132 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-40113 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40117 https://www.cve.org/CVERecord?id=CVE-2025-40117 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40119 https://www.cve.org/CVERecord?id=CVE-2025-40119 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40122 https://www.cve.org/CVERecord?id=CVE-2025-40122 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40129 https://www.cve.org/CVERecord?id=CVE-2025-40129 Référence CVE CVE-2025-40130 https://www.cve.org/CVERecord?id=CVE-2025-40130 Référence CVE CVE-2025-40131 https://www.cve.org/CVERecord?id=CVE-2025-40131 Référence CVE CVE-2025-40132 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38068 Référence CVE CVE-2025-38159 https://www.cve.org/CVERecord?id=CVE-2025-38159 Référence CVE CVE-2025-38704 https://www.cve.org/CVERecord?id=CVE-2025-38704 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39963 https://www.cve.org/CVERecord?id=CVE-2025-39963 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-40018 https://www.cve.org/CVERecord?id=CVE-2025-40018 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40130 https://www.cve.org/CVERecord?id=CVE-2025-40130 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40167 https://www.cve.org/CVERecord?id=CVE-2025-40167 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40179 https://www.cve.org/CVERecord?id=CVE-2025-40179 Référence CVE CVE-2025-40190 https://www.cve.org/CVERecord?id=CVE-2025-40190 Référence CVE CVE-2025-40204 https://www.cve.org/CVERecord?id=CVE-2025-40204 Référence CVE CVE-2025-40209 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-2025-40035 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 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-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40149 https://www.cve.org/CVERecord?id=CVE-2025-40149 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=CVE-2025-40153 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40160 https://www.cve.org/CVERecord?id=CVE-2025-40160 Référence CVE CVE-2025-40164 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-40107 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=CVE-2025-40111 Référence CVE CVE-2025-40112 https://www.cve.org/CVERecord?id=CVE-2025-40112 Référence CVE CVE-2025-40115 https://www.cve.org/CVERecord?id=CVE-2025-40115 Référence CVE CVE-2025-40116 https://www.cve.org/CVERecord?id=CVE-2025-40116 Référence CVE CVE-2025-40118 https://www.cve.org/CVERecord?id=CVE-2025-40118 Référence CVE CVE-2025-40120 https://www.cve.org/CVERecord?id=CVE-2025-40120 Référence CVE CVE-2025-40121 https://www.cve.org/CVERecord?id=CVE-2025-40121 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40124 https://www.cve.org/CVERecord?id=CVE-2025-40124 Référence CVE CVE-2025-40125 https://www.cve.org/CVERecord?id=CVE-2025-40125 Référence CVE CVE-2025-40126 https://www.cve.org/CVERecord?id=CVE-2025-40126 Référence CVE CVE-2025-40127 https://www.cve.org/CVERecord?id=CVE-2025-40127 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40140 https://www.cve.org/CVERecord?id=CVE-2025-40140 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40153 https://www.cve.org/CVERecord?id=

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
Linux: 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < dc4f348952173beb8ceb15be30b249276eccb605, patch: 6.6.112, 4.17, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < c1ad19b5d8e23123503dcaf2d4342e1b90b923ad, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 4540aed51b12bc13364149bf95f6ecef013197c0, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < a99de19128aec0913f3d529f529fbbff5edfaff8, patch: 5.10.270, patch: 6.17.3, patch: 6.1.156, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < e53a59e7cee5c1605d1ed595933098c2b69108f9, patch: 6.12.53, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32, patch: 6.18, patch: 5.15.221, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a, patch: 0
Fixed
Linux: < 4.17, 5.10.270 ≤ 5.10.*, 5.15.221 ≤ 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 12 Nov 2025 · Last source change 14 Sept 2026, 11:58 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-124960
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/e53a59e7cee5c1605d1ed595933098c2b69108f9; removed remediation: git.kernel.org/a99de19128aec0913f3d529f529fbbff5edfaff8.
    Before
    remediation: git.kernel.org/a99de19128aec0913f3d529f529fbbff5edfaff8
    After
    remediation: git.kernel.org/e53a59e7cee5c1605d1ed595933098c2b69108f9
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    5e43f899b03a3492ce5fc44e8900becb04dae9c0 < a99de19128aec0913f3d529f529fbbff5edfaff8; 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32; 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a; 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < c1ad19b5d8e23123503dcaf2d4342e1b90b923ad; 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 4540aed51b12bc13364149bf95f6ecef013197c0; 4.17 · Fixed: < 4.17; 6.1.156 ≤ 6.1.*; 6.6.112 ≤ 6.6.*; 6.12.53 ≤ 6.12.*; 6.17.3 ≤ 6.17.*; 6.18 ≤ *
    After
    Linux: 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < e53a59e7cee5c1605d1ed595933098c2b69108f9, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < dc4f348952173beb8ceb15be30b249276eccb605, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < a99de19128aec0913f3d529f529fbbff5edfaff8, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < c1ad19b5d8e23123503dcaf2d4342e1b90b923ad, 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 4540aed51b12bc13364149bf95f6ecef013197c0, 4.17 · Fixed: Linux: < 4.17, 5.10.270 ≤ 5.10.*, 5.15.221 ≤ 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-124960↗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-40123 · cve.blacktree.nl