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

exfat: validate cluster allocation bits of the allocation bitmap

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

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2025-40307 · CSAF 2.0 · revision 47 · interimSUSE Product Security TeamCVE-2025-40307
493 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
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: exfat: validate cluster allocation bits of the allocation bitmap syzbot created an exfat image with cluster bits not set for the allocation bitmap. exfat-fs reads and uses the allocation bitmap without checking this. The problem is that if the start cluster of the allocation bitmap is 6, cluster 6 can be allocated when creating a directory with mkdir. exfat zeros out this cluster in exfat_mkdir, which can delete existing entries. This can reallocate the allocated entries. In addition, the allocation bitmap is also zeroed out, so cluster 6 can be reallocated. This patch adds exfat_test_bitmap_range to validate that clusters used for the allocation bitmap are correctly marked as in-use.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-201638

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: exfat: validate cluster allocation bits of the allocation bitmap syzbot created an exfat image with cluster bits not set for the allocation bitmap. exfat-fs reads and uses the allocation bitmap without checking this. The problem is that if the start cluster of the allocation bitmap is 6, cluster 6 can be allocated when creating a directory with mkdir. exfat zeros out this cluster in exfat_mkdir, which can delete existing entries. This can reallocate the allocated entries. In addition, the allocation bitmap is also zeroed out, so cluster 6 can be reallocated. This patch adds exfat_test_bitmap_range to validate that clusters used for the allocation bitmap are correctly marked as in-use.

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: exfat: validate cluster allocation bits of the allocation bitmap syzbot created an exfat image with cluster bits not set for the allocation bitmap. exfat-fs reads and uses the allocation bitmap without checking this. The problem is that if the start cluster of the allocation bitmap is 6, cluster 6 can be allocated when creating a directory with mkdir. exfat zeros out this cluster in exfat_mkdir, which can delete existing entries. This can reallocate the allocated entries. In addition, the allocation bitmap is also zeroed out, so cluster 6 can be reallocated. This patch adds exfat_test_bitmap_range to validate that clusters used for the allocation bitmap are correctly marked as in-use.

What

In the Linux kernel, the following vulnerability has been resolved: exfat: validate cluster allocation bits of the allocation bitmap syzbot created an exfat image with cluster bits not set for the allocation bitmap. exfat-fs reads and uses the allocation bitmap without checking this. The problem is that if the start cluster of the allocation bitmap is 6, cluster 6 can be allocated when creating a directory with mkdir. exfat zeros out this cluster in exfat_mkdir, which can delete existing entries. This can reallocate the allocated entries. In addition, the allocation bitmap is also zeroed out, so cluster 6 can be reallocated. This patch adds exfat_test_bitmap_range to validate that clusters used for the allocation bitmap are correctly marked as in-use.

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: exfat: validate cluster allocation bits of the allocation bitmap syzbot created an exfat image with cluster bits not set for the allocation bitmap. exfat-fs reads and uses the allocation bitmap without checking this. The problem is that if the start cluster of the allocation bitmap is 6, cluster 6 can be allocated when creating a directory with mkdir. exfat zeros out this cluster in exfat_mkdir, which can delete existing entries. This can reallocate the allocated entries. In addition, the allocation bitmap is also zeroed out, so cluster 6 can be reallocated. This patch adds exfat_test_bitmap_range to validate that clusters used for the allocation bitmap are correctly marked as in-use.

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-201638Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: exfat: validate cluster allocation bits of the allocation bitmap syzbot created an exfat image with cluster bits not set for the allocation bitmap. exfat-fs reads and uses the allocation bitmap without checking this. The problem is that if the start cluster of the allocation bitmap is 6, cluster 6 can be allocated when creating a directory with mkdir. exfat zeros out this cluster in exfat_mkdir, which can delete existing entries. This can reallocate the allocated entries. In addition, the allocation bitmap is also zeroed out, so cluster 6 can be reallocated. This patch adds exfat_test_bitmap_range to validate that clusters used for the allocation bitmap are correctly marked as in-use.

Official EUVD record ↗
BSI · German · WID-SEC-2025-2756Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251210Security Bulletin 10 Dec 2025

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

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

d?id=CVE-2025-39833 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=CVE-2025-39925 Référence CVE CVE-2025-40054 https://www.cve.org/CVERecord?id=CVE-2025-40054 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40206 https://www.cve.org/CVERecord?id=CVE-2025-40206 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-45963 https://www.cve.org/CVERecord?id=CVE-2026-45963 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46158 https://www.cve.org/CVERecord?id=CVE-2026-46158 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40289 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40290 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40290 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40290 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40287 Référence CVE CVE-2025-40288 https://www.cve.org/CVERecord?id=CVE-2025-40288 Référence CVE CVE-2025-40289 https://www.cve.org/CVERecord?id=CVE-2025-40289 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=CVE-2025-40297 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 https://www.cve.org/CVERecord?id=CVE-2025-40315 Référence CVE CVE-2025-40316 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-40290 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40285 Référence CVE CVE-2025-40286 https://www.cve.org/CVERecord?id=CVE-2025-40286 Référence CVE CVE-2025-40287 https://www.cve.org/CVERecord?id=CVE-2025-40287 Référence CVE CVE-2025-40288 https://www.cve.org/CVERecord?id=CVE-2025-40288 Référence CVE CVE-2025-40289 https://www.cve.org/CVERecord?id=CVE-2025-40289 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40285 Référence CVE CVE-2025-40286 https://www.cve.org/CVERecord?id=CVE-2025-40286 Référence CVE CVE-2025-40287 https://www.cve.org/CVERecord?id=CVE-2025-40287 Référence CVE CVE-2025-40288 https://www.cve.org/CVERecord?id=CVE-2025-40288 Référence CVE CVE-2025-40289 https://www.cve.org/CVERecord?id=CVE-2025-40289 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40287 Référence CVE CVE-2025-40288 https://www.cve.org/CVERecord?id=CVE-2025-40288 Référence CVE CVE-2025-40289 https://www.cve.org/CVERecord?id=CVE-2025-40289 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=CVE-2025-40297 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 https://www.cve.org/CVERecord?id=CVE-2025-40315 Référence CVE CVE-2025-40316 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-40288 Référence CVE CVE-2025-40289 https://www.cve.org/CVERecord?id=CVE-2025-40289 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=CVE-2025-40297 Référence CVE CVE-2025-40300 https://www.cve.org/CVERecord?id=CVE-2025-40300 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 https://www.cve.org/CVERecord?id=CVE-2025-40315 Référence CVE CVE-2025-40316 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-40297 Référence CVE CVE-2025-40298 https://www.cve.org/CVERecord?id=CVE-2025-40298 Référence CVE CVE-2025-40299 https://www.cve.org/CVERecord?id=CVE-2025-40299 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40302 https://www.cve.org/CVERecord?id=CVE-2025-40302 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40297 Référence CVE CVE-2025-40298 https://www.cve.org/CVERecord?id=CVE-2025-40298 Référence CVE CVE-2025-40299 https://www.cve.org/CVERecord?id=CVE-2025-40299 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40302 https://www.cve.org/CVERecord?id=CVE-2025-40302 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40297 Référence CVE CVE-2025-40298 https://www.cve.org/CVERecord?id=CVE-2025-40298 Référence CVE CVE-2025-40299 https://www.cve.org/CVERecord?id=CVE-2025-40299 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40302 https://www.cve.org/CVERecord?id=CVE-2025-40302 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40305 https://www.cve.org/CVERecord?id=CVE-2025-40305 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40313 https://www.cve.org/CVERecord?id=CVE-2025-40313 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 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-40289 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=CVE-2025-40297 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40302 https://www.cve.org/CVERecord?id=CVE-2025-40302 Référence CVE CVE-2025-40303 https://www.cve.org/CVERecord?id=CVE-2025-40303 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 https://www.cve.org/CVERecord?id=CVE-2025-40315 Référence CVE CVE-2025-40316 https://www.cve.org/CVERecord?id=CVE-2025-40316 Référence CVE CVE-2025-40317 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-40289 Référence CVE CVE-2025-40292 https://www.cve.org/CVERecord?id=CVE-2025-40292 Référence CVE CVE-2025-40293 https://www.cve.org/CVERecord?id=CVE-2025-40293 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=CVE-2025-40297 Référence CVE CVE-2025-40301 https://www.cve.org/CVERecord?id=CVE-2025-40301 Référence CVE CVE-2025-40302 https://www.cve.org/CVERecord?id=CVE-2025-40302 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40306 https://www.cve.org/CVERecord?id=CVE-2025-40306 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-40308 https://www.cve.org/CVERecord?id=CVE-2025-40308 Référence CVE CVE-2025-40309 https://www.cve.org/CVERecord?id=CVE-2025-40309 Référence CVE CVE-2025-40310 https://www.cve.org/CVERecord?id=CVE-2025-40310 Référence CVE CVE-2025-40311 https://www.cve.org/CVERecord?id=CVE-2025-40311 Référence CVE CVE-2025-40312 https://www.cve.org/CVERecord?id=CVE-2025-40312 Référence CVE CVE-2025-40314 https://www.cve.org/CVERecord?id=CVE-2025-40314 Référence CVE CVE-2025-40315 https://www.cve.org/CVERecord?id=CVE-2025-40315 Référence CVE CVE-2025-40316 https://www.cve.org/CVERecord?id=

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6641MS 12월 보안 위협에 따른 정기 보안 업데이트 권고

er ep enable. | | Mariner | CVE-2025-40314 | usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget | | Mariner | CVE-2025-40313 | ntfs3: pretend $Extend records as regular files | | Mariner | CVE-2025-40312 | jfs: Verify inode mode when loading from disk | | Mariner | CVE-2025-40311 | accel/habanalabs: support mapping cb with vmalloc-backed coherent memory | | Mariner | CVE-2025-40310 | amd/amdkfd: resolve a race in amdgpu_amdkfd_device_fini_sw | | Mariner | CVE-2025-40309 | Bluetooth: SCO: Fix UAF on sco_conn_free | | Mariner | CVE-2025-40308 | Bluetooth: bcsp: receive data only if registered | | Mariner | CVE-2025-40307 | exfat: validate cluster allocation bits of the allocation bitmap | | Mariner | CVE-2025-40306 | orangefs: fix xattr related buffer overflow... | | Mariner | CVE-2025-40305 | 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN | | Mariner | CVE-2025-40304 | fbdev: Add bounds checking in bit_putcs to fix vmalloc-out-of-bounds | | Mariner | CVE-2025-40303 | btrfs: ensure no dirty metadata is written back for an fs with errors | | Mariner | CVE-2025-40301 | Bluetooth: hci_event: validate skb length for unknown CC opcode | | Mariner | CVE-2025-40297 | net: bridge: fix use-after-free due to MST port state bypass | | Mariner | CVE-2025-40294 |

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.7, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.58 ≤ 6.12.*, 6.17.8 ≤ 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 8 Dec 2025 · Last source change 19 Aug 2026, 16:27 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-201638
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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/87f827d53bd0688597bda63ae95908e2ad39bac0; removed remediation: git.kernel.org/67ce8034dc0278ddd88cad93d4218a945180dddd.
    Before
    remediation: git.kernel.org/67ce8034dc0278ddd88cad93d4218a945180dddd
    After
    remediation: git.kernel.org/87f827d53bd0688597bda63ae95908e2ad39bac0
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 67ce8034dc0278ddd88cad93d4218a945180dddd; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 6bc58b4c53795ab5fe00648344aa7d9d61175f90; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 13c1d24803d5b0446b3f6f0fdd67e07ac1fdc7bf; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 79c1587b6cda74deb0c86fc7ba194b92958c793c; 5.7 · Fixed: < 5.7; 6.6.148 ≤ 6.6.*; 6.12.58 ≤ 6.12.*; 6.17.8 ≤ 6.17.*; 6.18 ≤ *
    After
    1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 87f827d53bd0688597bda63ae95908e2ad39bac0; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 67ce8034dc0278ddd88cad93d4218a945180dddd; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 6bc58b4c53795ab5fe00648344aa7d9d61175f90; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 13c1d24803d5b0446b3f6f0fdd67e07ac1fdc7bf; 1acf1a564b6034b5af1e7fb23cb98cb3bb4f6003 < 79c1587b6cda74deb0c86fc7ba194b92958c793c; 5.7 · Fixed: < 5.7; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.58 ≤ 6.12.*; 6.17.8 ≤ 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-201638↗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-40307 · cve.blacktree.nl