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

netfilter: ctnetlink: fix refcount leak on table dump

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 32 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% 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: No default targetRemediation target: Normal maintenance

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

Distribution package intelligence

Release-specific package status

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

25 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

4 current
CVE-2025-38721 · CSAF 2.0 · revision 67 · interimSUSE Product Security TeamCVE-2025-38721
407 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.
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: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
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.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.
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: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.
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-26748

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 32 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: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.

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: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-26748Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE cb->args[1] = (unsigned long)ct; ... While its very unlikely, its possible that ct == last. If this happens, then the refcount of ct was already incremented. This 2nd increment is never undone. This prevents the conntrack object from being released, which in turn keeps prevents cnet->count from dropping back to 0. This will then block the netns dismantle (or conntrack rmmod) as nf_conntrack_cleanup_net_list() will wait forever. This can be reproduced by running conntrack_resize.sh selftest in a loop. It takes ~20 minutes for me on a preemptible kernel on average before I see a runaway kworker spinning in nf_conntrack_cleanup_net_list. One fix would to change this to: if (res < 0) { if (ct != last) nf_conntrack_get(&ct->ct_general); But this reference counting isn't needed in the first place. We can just store a cookie value instead. A followup patch will do the same for ctnetlink_exp_dump_table, it looks to me as if this has the same problem and like ctnetlink_dump_table, we only need a 'skip hint', not the actual object so we can apply the same cookie strategy there as well.

Official EUVD record ↗
BSI · German · WID-SEC-2025-1976Linux 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 andere nicht spezifizierte Angriffe durchzuführen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 SEP 2025, published on 10 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-21867, CVE-2025-21875, CVE-2025-21887, CVE-2025-21913, CVE-2025-21919, CVE-2025-21925, CVE-2025-21926, CVE-2025-21938, CVE-2025-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-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

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

d?id=CVE-2025-38702 Référence CVE CVE-2025-38706 https://www.cve.org/CVERecord?id=CVE-2025-38706 Référence CVE CVE-2025-38707 https://www.cve.org/CVERecord?id=CVE-2025-38707 Référence CVE CVE-2025-38708 https://www.cve.org/CVERecord?id=CVE-2025-38708 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38723 https://www.cve.org/CVERecord?id=CVE-2025-38723 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38735 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38708 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38716 https://www.cve.org/CVERecord?id=CVE-2025-38716 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 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-38708 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38716 https://www.cve.org/CVERecord?id=CVE-2025-38716 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38708 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38716 https://www.cve.org/CVERecord?id=CVE-2025-38716 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 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-38708 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38716 https://www.cve.org/CVERecord?id=CVE-2025-38716 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 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-38708 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38716 https://www.cve.org/CVERecord?id=CVE-2025-38716 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38706 Référence CVE CVE-2025-38707 https://www.cve.org/CVERecord?id=CVE-2025-38707 Référence CVE CVE-2025-38708 https://www.cve.org/CVERecord?id=CVE-2025-38708 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 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-38702 Référence CVE CVE-2025-38703 https://www.cve.org/CVERecord?id=CVE-2025-38703 Référence CVE CVE-2025-38705 https://www.cve.org/CVERecord?id=CVE-2025-38705 Référence CVE CVE-2025-38706 https://www.cve.org/CVERecord?id=CVE-2025-38706 Référence CVE CVE-2025-38709 https://www.cve.org/CVERecord?id=CVE-2025-38709 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38717 https://www.cve.org/CVERecord?id=CVE-2025-38717 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38733 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38706 Référence CVE CVE-2025-38707 https://www.cve.org/CVERecord?id=CVE-2025-38707 Référence CVE CVE-2025-38708 https://www.cve.org/CVERecord?id=CVE-2025-38708 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39675 https://www.cve.org/CVERecord?id=CVE-2025-39675 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39681 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-38703 Référence CVE CVE-2025-38705 https://www.cve.org/CVERecord?id=CVE-2025-38705 Référence CVE CVE-2025-38706 https://www.cve.org/CVERecord?id=CVE-2025-38706 Référence CVE CVE-2025-38709 https://www.cve.org/CVERecord?id=CVE-2025-38709 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 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-38703 Référence CVE CVE-2025-38705 https://www.cve.org/CVERecord?id=CVE-2025-38705 Référence CVE CVE-2025-38706 https://www.cve.org/CVERecord?id=CVE-2025-38706 Référence CVE CVE-2025-38709 https://www.cve.org/CVERecord?id=CVE-2025-38709 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38722 https://www.cve.org/CVERecord?id=CVE-2025-38722 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38734 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-38706 Référence CVE CVE-2025-38707 https://www.cve.org/CVERecord?id=CVE-2025-38707 Référence CVE CVE-2025-38708 https://www.cve.org/CVERecord?id=CVE-2025-38708 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38723 https://www.cve.org/CVERecord?id=CVE-2025-38723 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=CVE-2025-38732 Référence CVE CVE-2025-38735 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-38702 Référence CVE CVE-2025-38706 https://www.cve.org/CVERecord?id=CVE-2025-38706 Référence CVE CVE-2025-38707 https://www.cve.org/CVERecord?id=CVE-2025-38707 Référence CVE CVE-2025-38708 https://www.cve.org/CVERecord?id=CVE-2025-38708 Référence CVE CVE-2025-38711 https://www.cve.org/CVERecord?id=CVE-2025-38711 Référence CVE CVE-2025-38712 https://www.cve.org/CVERecord?id=CVE-2025-38712 Référence CVE CVE-2025-38713 https://www.cve.org/CVERecord?id=CVE-2025-38713 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38715 https://www.cve.org/CVERecord?id=CVE-2025-38715 Référence CVE CVE-2025-38721 https://www.cve.org/CVERecord?id=CVE-2025-38721 Référence CVE CVE-2025-38723 https://www.cve.org/CVERecord?id=CVE-2025-38723 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-38725 https://www.cve.org/CVERecord?id=CVE-2025-38725 Référence CVE CVE-2025-38727 https://www.cve.org/CVERecord?id=CVE-2025-38727 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-38729 https://www.cve.org/CVERecord?id=CVE-2025-38729 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-38732 https://www.cve.org/CVERecord?id=

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

Linuxカーネルのnetfilterサブシステムにおいて、ctnetlinkによるテーブルダンプ処理で参照カウントリークが発生する脆弱性が修正されました。まれにconntrackオブジェクトの参照カウントが適切に解放されないことで、カーネルのリソースが枯渇したり、netnsの解体やモジュールの取り外し処理が停止する可能性があります。この問題には、参照カウント処理を削除し、クッキー値を保存することで対処しています。また、ctnetlink_exp_dump_tableにも同様の修正が今後適用される予定です。

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

Multiple security vulnerabilities including a refcount leak in netfilter, CPU cache initialization flaws, AMD processor data leakage, and the VMSCAPE branch predictor isolation issue were fixed across various Linux kernel versions and SUSE Enterprise products.

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: < 2.6.18, 5.4.297 ≤ 5.4.*, 5.10.241 ≤ 5.10.*, 5.15.190 ≤ 5.15.*, 6.1.149 ≤ 6.1.*, 6.6.103 ≤ 6.6.*, 6.12.43 ≤ 6.12.*, 6.15.11 ≤ 6.15.*, 6.16.2 ≤ 6.16.*, 6.17 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 4 Sept 2025 · Last source change 8 Sept 2026, 08:41 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-26748
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
    d205dc40798d97d63ad348bfaf7394f445d152d4 < 586892e341fbf698e7cbaca293e1353957db725a; d205dc40798d97d63ad348bfaf7394f445d152d4 < 962518c6ca9f9a13df099cafa429f72f68ad61f0; d205dc40798d97d63ad348bfaf7394f445d152d4 < 19b909a4b1452fb97e477d2f08b97f8d04095619; d205dc40798d97d63ad348bfaf7394f445d152d4 < 41462f4cfc583513833f87f9ee55d12da651a7e3; d205dc40798d97d63ad348bfaf7394f445d152d4 < 30cf811058552b8cd0e98dff677ef3f89d6d34ce; d205dc40798d97d63ad348bfaf7394f445d152d4 < a2cb4df7872de069f809de2f076ec8e54d649fe3; d205dc40798d97d63ad348bfaf7394f445d152d4 < e14f72aa66c029db106921d621edcedef68e065b; d205dc40798d97d63ad348bfaf7394f445d152d4 < a62d6aa3f31f216b637a4c71b7a8bfc7c57f049b · Fixed: < 2.6.18; 5.4.297 ≤ 5.4.*; 5.10.241 ≤ 5.10.*; 5.15.190 ≤ 5.15.*; 6.1.149 ≤ 6.1.*; 6.6.103 ≤ 6.6.*; 6.12.43 ≤ 6.12.*; 6.15.11 ≤ 6.15.*
    After
    Linux: d205dc40798d97d63ad348bfaf7394f445d152d4 < 586892e341fbf698e7cbaca293e1353957db725a, d205dc40798d97d63ad348bfaf7394f445d152d4 < 962518c6ca9f9a13df099cafa429f72f68ad61f0, d205dc40798d97d63ad348bfaf7394f445d152d4 < 19b909a4b1452fb97e477d2f08b97f8d04095619, d205dc40798d97d63ad348bfaf7394f445d152d4 < 41462f4cfc583513833f87f9ee55d12da651a7e3, d205dc40798d97d63ad348bfaf7394f445d152d4 < 30cf811058552b8cd0e98dff677ef3f89d6d34ce, d205dc40798d97d63ad348bfaf7394f445d152d4 < a2cb4df7872de069f809de2f076ec8e54d649fe3, d205dc40798d97d63ad348bfaf7394f445d152d4 < e14f72aa66c029db106921d621edcedef68e065b, d205dc40798d97d63ad348bfaf7394f445d152d4 < a62d6aa3f31f216b637a4c71b7a8bfc7c57f049b, d205dc40798d97d63ad348bfaf7394f445d152d4 < de788b2e6227462b6dcd0e07474e72c089008f74, 2.6.18 · Fixed: Linux: < 2.6.18, 5.4.297 ≤ 5.4.*, 5.10.241 ≤ 5.10.*, 5.15.190 ≤ 5.15.*, 6.1.149 ≤ 6.1.*, 6.6.103 ≤ 6.6.*, 6.12.43 ≤ 6.12.*, 6.15.11 ≤ 6.15.*, 6.16.2 ≤ 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-26748↗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-38721 · cve.blacktree.nl