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

net: rose: include node references in rose_neigh refcount

Linux · Linux

8.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 27 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.22% 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: Within 30 daysRemediation target: Within 180 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 27 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

25 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.48-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.153-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.5-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-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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.

3 current
CVE-2025-39827 · CSAF 2.0 · revision 52 · interimSUSE Product Security TeamCVE-2025-39827
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

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

  • SIMATIC CN 4100
Summary
In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.
Remediation
Update to V5.0 or later version
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-29587

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.

What

In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.

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 an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.

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 an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

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

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

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Unauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-29587Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: rose: include node references in rose_neigh refcount Current implementation maintains two separate reference counting mechanisms: the 'count' field in struct rose_neigh tracks references from rose_node structures, while the 'use' field (now refcount_t) tracks references from rose_sock. This patch merges these two reference counting systems using 'use' field for proper reference management. Specifically, this patch adds incrementing and decrementing of rose_neigh->use when rose_neigh->count is incremented or decremented. This patch also modifies rose_rt_free(), rose_rt_device_down() and rose_clear_route() to properly release references to rose_neigh objects before freeing a rose_node through rose_remove_node(). These changes ensure rose_neigh structures are properly freed only when all references, including those from rose_node structures, are released. As a result, this resolves a slab-use-after-free issue reported by Syzbot.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250917SECURITY BULLETIN 17 SEPT 2025

The Cyber Security Agency of Singapore included this CVE in its official SECURITY BULLETIN 17 SEPT 2025, published on 17 September 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

25-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025

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

d?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39815 https://www.cve.org/CVERecord?id=CVE-2025-39815 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39808 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39842 https://www.cve.org/CVERecord?id=CVE-2025-39842 Référence CVE CVE-2025-39843 https://www.cve.org/CVERecord?id=CVE-2025-39843 Référence CVE CVE-2025-39844 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-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39815 https://www.cve.org/CVERecord?id=CVE-2025-39815 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 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-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39815 https://www.cve.org/CVERecord?id=CVE-2025-39815 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 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-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39815 https://www.cve.org/CVERecord?id=CVE-2025-39815 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 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-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39815 https://www.cve.org/CVERecord?id=CVE-2025-39815 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 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-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39789 https://www.cve.org/CVERecord?id=CVE-2025-39789 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39850 https://www.cve.org/CVERecord?id=CVE-2025-39850 Référence CVE CVE-2025-39851 https://www.cve.org/CVERecord?id=CVE-2025-39851 Référence CVE CVE-2025-39859 https://www.cve.org/CVERecord?id=CVE-2025-39859 Référence CVE CVE-2025-39863 https://www.cve.org/CVERecord?id=CVE-2025-39863 Référence CVE CVE-2025-39877 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-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39789 https://www.cve.org/CVERecord?id=CVE-2025-39789 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39850 https://www.cve.org/CVERecord?id=CVE-2025-39850 Référence CVE CVE-2025-39851 https://www.cve.org/CVERecord?id=CVE-2025-39851 Référence CVE CVE-2025-39859 https://www.cve.org/CVERecord?id=CVE-2025-39859 Référence CVE CVE-2025-39863 https://www.cve.org/CVERecord?id=CVE-2025-39863 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39816 https://www.cve.org/CVERecord?id=CVE-2025-39816 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39830 https://www.cve.org/CVERecord?id=CVE-2025-39830 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39834 https://www.cve.org/CVERecord?id=CVE-2025-39834 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39844 https://www.cve.org/CVERecord?id=CVE-2025-39844 Référence CVE CVE-2025-39845 https://www.cve.org/CVERecord?id=CVE-2025-39845 Référence CVE CVE-2025-39846 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39806 https://www.cve.org/CVERecord?id=CVE-2025-39806 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39844 https://www.cve.org/CVERecord?id=CVE-2025-39844 Référence CVE CVE-2025-39845 https://www.cve.org/CVERecord?id=CVE-2025-39845 Référence CVE CVE-2025-39846 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39807 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39816 https://www.cve.org/CVERecord?id=CVE-2025-39816 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39830 https://www.cve.org/CVERecord?id=CVE-2025-39830 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39834 https://www.cve.org/CVERecord?id=CVE-2025-39834 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39807 Référence CVE CVE-2025-39808 https://www.cve.org/CVERecord?id=CVE-2025-39808 Référence CVE CVE-2025-39810 https://www.cve.org/CVERecord?id=CVE-2025-39810 Référence CVE CVE-2025-39811 https://www.cve.org/CVERecord?id=CVE-2025-39811 Référence CVE CVE-2025-39816 https://www.cve.org/CVERecord?id=CVE-2025-39816 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39830 https://www.cve.org/CVERecord?id=CVE-2025-39830 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39834 https://www.cve.org/CVERecord?id=CVE-2025-39834 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39842 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39808 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=CVE-2025-39839 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39842 https://www.cve.org/CVERecord?id=CVE-2025-39842 Référence CVE CVE-2025-39843 https://www.cve.org/CVERecord?id=CVE-2025-39843 Référence CVE CVE-2025-39844 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39815 https://www.cve.org/CVERecord?id=CVE-2025-39815 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39819 https://www.cve.org/CVERecord?id=CVE-2025-39819 Référence CVE CVE-2025-39823 https://www.cve.org/CVERecord?id=CVE-2025-39823 Référence CVE CVE-2025-39824 https://www.cve.org/CVERecord?id=CVE-2025-39824 Référence CVE CVE-2025-39825 https://www.cve.org/CVERecord?id=CVE-2025-39825 Référence CVE CVE-2025-39826 https://www.cve.org/CVERecord?id=CVE-2025-39826 Référence CVE CVE-2025-39827 https://www.cve.org/CVERecord?id=CVE-2025-39827 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39831 https://www.cve.org/CVERecord?id=CVE-2025-39831 Référence CVE CVE-2025-39832 https://www.cve.org/CVERecord?id=CVE-2025-39832 Référence CVE CVE-2025-39835 https://www.cve.org/CVERecord?id=CVE-2025-39835 Référence CVE CVE-2025-39836 https://www.cve.org/CVERecord?id=CVE-2025-39836 Référence CVE CVE-2025-39838 https://www.cve.org/CVERecord?id=CVE-2025-39838 Référence CVE CVE-2025-39839 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。net: rose: rose_neighの参照カウントにノード参照を含めています。現行の実装では、2つの別々の参照カウント機構を維持しています。struct rose_neighの'count'フィールドはrose_node構造体からの参照を追跡し、一方で'use'フィールド（現在はrefcount_t）はrose_sockからの参照を追跡しています。このパッチはこれら2つの参照カウントシステムを'use'フィールドを用いて統合し、適切な参照管理を行います。具体的には、rose_neigh->countが増減するときにrose_neigh->useも増減する処理を追加しています。また、rose_rt_free()、rose_rt_device_down()、rose_clear_route()を修正し、rose_remove_node()によってrose_nodeを解放する前にrose_neighオブジェクトへの参照を適切に解放するようにしています。これらの変更により、rose_neigh構造体はrose_node構造体からの参照を含むすべての参照が解放されて初めて正しく解放されるようになり、Syzbotによって報告されたslab-use-after-freeの問題が解決されました。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple Linux kernel updates, including SUSE Enterprise and Micro versions, address numerous security vulnerabilities such as slab-use-after-free, privilege escalation, denial of service, and information leaks across various subsystems, drivers, and architectures, with notable fixes in AppArmor LSM and AMD Zen microcode verification.

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
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 16 Sept 2025 · Last source change 8 Sept 2026, 08:42 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-29587
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4cce478c3e82a5fc788d72adb2f4c4e983997639; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9c547c8eee9d1cf6e744611d688b9f725cf9a115; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d7563b456ed44151e1a82091d96f60166daea89b; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 384210cceb1873a4c8218b27ba0745444436b728; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < da9c9c877597170b929a6121a68dcd3dd9a80f45; 2.6.12 · Fixed: < 2.6.12; 6.1.150 ≤ 6.1.*; 6.6.104 ≤ 6.6.*; 6.12.45 ≤ 6.12.*; 6.16.5 ≤ 6.16.*; 6.17 ≤ *
    After
    Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4cce478c3e82a5fc788d72adb2f4c4e983997639, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9c547c8eee9d1cf6e744611d688b9f725cf9a115, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d7563b456ed44151e1a82091d96f60166daea89b, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 384210cceb1873a4c8218b27ba0745444436b728, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < da9c9c877597170b929a6121a68dcd3dd9a80f45, 2.6.12 · Fixed: Linux: < 2.6.12, 6.1.150 ≤ 6.1.*, 6.6.104 ≤ 6.6.*, 6.12.45 ≤ 6.12.*, 6.16.5 ≤ 6.16.*, 6.17 ≤ *
    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-29587↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-39827 · cve.blacktree.nl