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

dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue()

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 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.10% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.18.10-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-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.

2 current
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: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) access sw->desc 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.
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: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) access sw->desc 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2025-206989

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) <- FREED! -> access sw->desc <- UAF! This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan > 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 30 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: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) <- FREED! -> access sw->desc <- UAF! This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan > 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.

What

In the Linux kernel, the following vulnerability has been resolved: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) <- FREED! -> access sw->desc <- UAF! This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan > 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) <- FREED! -> access sw->desc <- UAF! This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan > 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-362
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-206989Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue() Add proper locking in mmp_pdma_residue() to prevent use-after-free when accessing descriptor list and descriptor contents. The race occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors: CPU 0 CPU 1 ----- ----- mmp_pdma_tx_status() mmp_pdma_residue() -> NO LOCK held list_for_each_entry(sw, ..) DMA interrupt dma_do_tasklet() -> spin_lock(&desc_lock) list_move(sw->node, ...) spin_unlock(&desc_lock) | dma_pool_free(sw) <- FREED! -> access sw->desc <- UAF! This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan > 1). Fix by protecting the chain_running list iteration and descriptor access with the chan->desc_lock spinlock.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0421Linux Kernel: Mehrere Schwachstellen

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260218Security Bulletin 18 Feb 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 18 Feb 2026, published on 18 February 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2025-71239 https://www.cve.org/CVERecord?id=CVE-2025-71239 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71193 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71195 https://www.cve.org/CVERecord?id=CVE-2025-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71201 https://www.cve.org/CVERecord?id=CVE-2025-71201 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2025-71239 https://www.cve.org/CVERecord?id=CVE-2025-71239 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-54518 Référence CVE CVE-2025-62626 https://www.cve.org/CVERecord?id=CVE-2025-62626 Référence CVE CVE-2025-68175 https://www.cve.org/CVERecord?id=CVE-2025-68175 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71203 https://www.cve.org/CVERecord?id=CVE-2025-71203 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2025-71287 https://www.cve.org/CVERecord?id=CVE-2025-71287 Référence CVE CVE-2025-71288 https://www.cve.org/CVERecord?id=CVE-2025-71288 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22993 https://www.cve.org/CVERecord?id=CVE-2026-22993 Référence CVE CVE-2026-23004 https://www.cve.org/CVERecord?id=CVE-2026-23004 Référence CVE CVE-2026-23066 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68358 https://www.cve.org/CVERecord?id=CVE-2025-68358 Référence CVE CVE-2025-71150 https://www.cve.org/CVERecord?id=CVE-2025-71150 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2025-71239 https://www.cve.org/CVERecord?id=CVE-2025-71239 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71201 https://www.cve.org/CVERecord?id=CVE-2025-71201 Référence CVE CVE-2025-71203 https://www.cve.org/CVERecord?id=CVE-2025-71203 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71229 https://www.cve.org/CVERecord?id=CVE-2025-71229 Référence CVE CVE-2025-71231 https://www.cve.org/CVERecord?id=CVE-2025-71231 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71194 Référence CVE CVE-2025-71195 https://www.cve.org/CVERecord?id=CVE-2025-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71201 https://www.cve.org/CVERecord?id=CVE-2025-71201 Référence CVE CVE-2025-71203 https://www.cve.org/CVERecord?id=CVE-2025-71203 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=CVE-2025-71233 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-71237 https://www.cve.org/CVERecord?id=CVE-2025-71237 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2025-71239 https://www.cve.org/CVERecord?id=CVE-2025-71239 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=

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

25-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025-71095, CVE-2025-71097, CVE-2025-71098, CVE-2025-71104, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71197, CVE-2025-71221, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2026-3497, CVE-2026-22977, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-22992, CVE-2026-22994, CVE-2026-23003, CVE-2026-23005, CVE-2026-23010, CVE-2026-23011, CVE-2026-23019, CVE-2026-23026, CVE-2026-23038, CVE-2026-23054, CVE-2026-23060, CVE-2026-23083, CVE-2026-23084, CVE-2026-23086, CVE-2026-23087, CVE-2026-23095, CVE-2026-23100, CVE-2026-23103, CVE-2026-23110, CVE-2026-23111, CVE-2026-23113, CVE-2026-23154, CVE-2026-23204, CVE-2026-23231, CVE-2026-23242, CVE-2026-23243, CVE-2026-23245, CVE-2026-23270, CVE-2026-23271, CVE-2026-23273, CVE-2026-23274, CVE-2026-23277, CVE-2026-

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

d?id=CVE-2025-40219 Référence CVE CVE-2025-40242 https://www.cve.org/CVERecord?id=CVE-2025-40242 Référence CVE CVE-2025-40261 https://www.cve.org/CVERecord?id=CVE-2025-40261 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-71067 https://www.cve.org/CVERecord?id=CVE-2025-71067 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=CVE-2025-71265 Référence CVE CVE-2025-71266 https://www.cve.org/CVERecord?id=CVE-2025-71266 Référence CVE CVE-2025-71267 https://www.cve.org/CVERecord?id=CVE-2025-71267 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2026-23100 https://www.cve.org/CVERecord?id=CVE-2026-23100 Référence CVE CVE-2026-23113 https://www.cve.org/CVERecord?id=CVE-2026-23113 Référence CVE CVE-2026-23141 https://www.cve.org/CVERecord?id=CVE-2026-23141 Référence CVE CVE-2026-23154 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68175 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68334 https://www.cve.org/CVERecord?id=CVE-2025-68334 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=CVE-2025-68736 Référence CVE CVE-2025-71067 https://www.cve.org/CVERecord?id=CVE-2025-71067 Référence CVE CVE-2025-71152 https://www.cve.org/CVERecord?id=CVE-2025-71152 Référence CVE CVE-2025-71161 https://www.cve.org/CVERecord?id=CVE-2025-71161 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71239 https://www.cve.org/CVERecord?id=CVE-2025-71239 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=CVE-2025-71265 Référence CVE CVE-2025-71266 https://www.cve.org/CVERecord?id=CVE-2025-71266 Référence CVE CVE-2025-71267 https://www.cve.org/CVERecord?id=CVE-2025-71267 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 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-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71202 https://www.cve.org/CVERecord?id=CVE-2025-71202 Référence CVE CVE-2025-71203 https://www.cve.org/CVERecord?id=CVE-2025-71203 Référence CVE CVE-2025-71204 https://www.cve.org/CVERecord?id=CVE-2025-71204 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71223 https://www.cve.org/CVERecord?id=CVE-2025-71223 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71227 https://www.cve.org/CVERecord?id=CVE-2025-71227 Référence CVE CVE-2025-71229 https://www.cve.org/CVERecord?id=CVE-2025-71229 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 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-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71202 https://www.cve.org/CVERecord?id=CVE-2025-71202 Référence CVE CVE-2025-71203 https://www.cve.org/CVERecord?id=CVE-2025-71203 Référence CVE CVE-2025-71204 https://www.cve.org/CVERecord?id=CVE-2025-71204 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71221 https://www.cve.org/CVERecord?id=CVE-2025-71221 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71223 https://www.cve.org/CVERecord?id=CVE-2025-71223 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71227 https://www.cve.org/CVERecord?id=CVE-2025-71227 Référence CVE CVE-2025-71229 https://www.cve.org/CVERecord?id=CVE-2025-71229 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71233 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-008046LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。dmaengineのmmp_pdmaにおけるmmp_pdma_residue()関数のレースコンディションを修正しました。descriptorリストおよびdescriptorの内容にアクセスする際のuse-after-freeを防ぐために、mmp_pdma_residue()に適切なロックを追加しています。複数のスレッドがtx_status()を呼び出し、別のCPU上のタスクレットが完了したdescriptorを解放している間にレースが発生します。CPU 0 と CPU 1 間では、mmp_pdma_tx_status()がmmp_pdma_residue()をノーロックで実行し、list_for_each_entryでswを列挙している間に、CPU 1 がDMA割り込みでdma_do_tasklet()を呼び出し、desc_lockをスピンロックしてsw-nodeをlist_moveし、スピンアンロック後にdma_pool_free(sw)でメモリ解放が発生します。その後CPU 0が解放済みのsw-descにアクセスしてUAFが生じます。この問題は、同一チャネルで複数スレッド(threads_per_chan 1)を使用してdmatestを実行した際に再現可能です。解決策として、chain_runningリストの反復処理およびdescriptorアクセスをchan-desc_lockスピンロックで保護する修正を行いました。

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: < 3.16, 5.15.209 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.130 ≤ 6.6.*, 6.12.78 ≤ 6.12.*, 6.18.10 ≤ 6.18.*, 6.19 ≤ *
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
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 14 Feb 2026 · Last source change 8 Sept 2026, 08:44 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-206989
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1b38da264674d6a0fe26a63996b8f88b88c3da48 < 3f0e0e2d9e752570041e95fd04635e2580097819; 1b38da264674d6a0fe26a63996b8f88b88c3da48 < dfb5e05227745de43b7fd589721817a4337c970d; 1b38da264674d6a0fe26a63996b8f88b88c3da48 < eba0c75670c022cb1f948600db972524bcfe8166; 1b38da264674d6a0fe26a63996b8f88b88c3da48 < fc023b8fab057f0c910856ff36d3e12a30b7af4a; 1b38da264674d6a0fe26a63996b8f88b88c3da48 < 9f665b3c3d9a168410251f27a5d019b7bf93185c; 1b38da264674d6a0fe26a63996b8f88b88c3da48 < a143545855bc2c6e1330f6f57ae375ac44af00a7; 3.16 · Fixed: < 3.16; 5.15.209 ≤ 5.15.*; 6.1.167 ≤ 6.1.*; 6.6.130 ≤ 6.6.*; 6.12.78 ≤ 6.12.*; 6.18.10 ≤ 6.18.*; 6.19 ≤ *
    After
    Linux: 1b38da264674d6a0fe26a63996b8f88b88c3da48 < 3f0e0e2d9e752570041e95fd04635e2580097819, 1b38da264674d6a0fe26a63996b8f88b88c3da48 < dfb5e05227745de43b7fd589721817a4337c970d, 1b38da264674d6a0fe26a63996b8f88b88c3da48 < eba0c75670c022cb1f948600db972524bcfe8166, 1b38da264674d6a0fe26a63996b8f88b88c3da48 < fc023b8fab057f0c910856ff36d3e12a30b7af4a, 1b38da264674d6a0fe26a63996b8f88b88c3da48 < 9f665b3c3d9a168410251f27a5d019b7bf93185c, 1b38da264674d6a0fe26a63996b8f88b88c3da48 < a143545855bc2c6e1330f6f57ae375ac44af00a7, 3.16 · Fixed: Linux: < 3.16, 5.15.209 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.130 ≤ 6.6.*, 6.12.78 ≤ 6.12.*, 6.18.10 ≤ 6.18.*, 6.19 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-71221 · cve.blacktree.nl