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

platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it

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 24 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.25% 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 24 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.

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

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2025-21645 · CSAF 2.0 · revision 62 · interimSUSE Product Security TeamCVE-2025-21645
82 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]
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: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]
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-2594

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]

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 24 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: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]

What

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]

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: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]

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

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250122Security Bulletin 22 Jan 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jan 2025, published on 22 January 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

ou égales à 3.1.6 pour les vulnérabilités CVE-2021-41617, CVE-2023-28531, CVE-2023-51384, CVE-2023-52927, CVE-2024-26783, CVE-2024-27056, CVE-2024-28956, CVE-2024-36903, CVE-2024-36927, CVE-2024-42079, CVE-2024-46786, CVE-2024-47736, CVE-2024-47809, CVE-2024-49968, CVE-2024-49994, CVE-2024-49998, CVE-2024-50014, CVE-2024-50063, CVE-2024-50164, CVE-2024-50298, CVE-2024-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-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

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

d?id=CVE-2025-14831 Référence CVE CVE-2025-15079 https://www.cve.org/CVERecord?id=CVE-2025-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-2025-15224 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21634 https://www.cve.org/CVERecord?id=CVE-2025-21634 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=CVE-2025-21656 Référence CVE CVE-2025-21658 https://www.cve.org/CVERecord?id=CVE-2025-21658 Référence CVE CVE-2025-21667 https://www.cve.org/CVERecord?id=CVE-2025-21667 Référence CVE CVE-2025-21672 https://www.cve.org/CVERecord?id=CVE-2025-21672 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=CVE-2025-21673 Référence CVE CVE-2025-21682 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-14831 Référence CVE CVE-2025-15079 https://www.cve.org/CVERecord?id=CVE-2025-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-2025-15224 Référence CVE CVE-2025-15467 https://www.cve.org/CVERecord?id=CVE-2025-15467 Référence CVE CVE-2025-15468 https://www.cve.org/CVERecord?id=CVE-2025-15468 Référence CVE CVE-2025-15469 https://www.cve.org/CVERecord?id=CVE-2025-15469 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21634 https://www.cve.org/CVERecord?id=CVE-2025-21634 Référence CVE CVE-2025-21635 https://www.cve.org/CVERecord?id=CVE-2025-21635 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=CVE-2025-21656 Référence CVE CVE-2025-21658 https://www.cve.org/CVERecord?id=CVE-2025-21658 Référence CVE CVE-2025-21667 https://www.cve.org/CVERecord?id=CVE-2025-21667 Référence CVE CVE-2025-21672 https://www.cve.org/CVERecord?id=CVE-2025-21672 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=CVE-2025-21673 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=

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

ve.org/CVERecord?id=CVE-2025-1352 Référence CVE CVE-2025-1365 https://www.cve.org/CVERecord?id=CVE-2025-1365 Référence CVE CVE-2025-1371 https://www.cve.org/CVERecord?id=CVE-2025-1371 Référence CVE CVE-2025-1372 https://www.cve.org/CVERecord?id=CVE-2025-1372 Référence CVE CVE-2025-1376 https://www.cve.org/CVERecord?id=CVE-2025-1376 Référence CVE CVE-2025-1377 https://www.cve.org/CVERecord?id=CVE-2025-1377 Référence CVE CVE-2025-1390 https://www.cve.org/CVERecord?id=CVE-2025-1390 Référence CVE CVE-2025-1795 https://www.cve.org/CVERecord?id=CVE-2025-1795 Référence CVE CVE-2025-21644 https://www.cve.org/CVERecord?id=CVE-2025-21644 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21647 https://www.cve.org/CVERecord?id=CVE-2025-21647 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21659 https://www.cve.org/CVERecord?id=CVE-2025-21659 Référence CVE CVE-2025-21663 https://www.cve.org/CVERecord?id=CVE-2025-21663 Référence CVE CVE-2025-21668 https://www.cve.org/CVERecord?id=CVE-2025-21668 Référence CVE CVE-2025-21670 https://www.cve.org/CVERecord?id=CVE-2025-21670 Référence CVE CVE-2025-21671 https://www.cve.org/CVERecord?id=CVE-2025-21671 Référence CVE CVE-2025-21673 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0899Multiples vulnérabilités dans les produits Microsoft

CVE-2025-39987 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39990 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39994 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-39998 du 16 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49124 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2022-49133 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-49568 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-53687 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2024-56709 du 17 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-21629 du 18 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-21645 du 18 octobre 2025 Une gestion de version détaillée se trouve à la fin de ce document. Risques Atteinte à la confidentialité des données Contournement de la politique de sécurité Déni de service Exécution de code arbitraire à distance Non spécifié par l'éditeur Systèmes affectés azl3 binutils 2.41-7 azl3 kernel 6.6.104.2-1 azl3 kernel 6.6.96.2-2 azl3 openssh 9.8p1-4 azl3 python3 3.12.9-4 versions antérieures à 3.12.9-5 azl3 pytorch 2.2.2-7 azl3 qemu 8.2.0-19 azl3 qtsvg 6.6.1-2 versions antérieures à 6.6.1-3 azl3 ruby 3.3.5-5 azl3 rubygem-elasticsearch 8.9.0-1 azl3 valkey 8.0.4-1 azl3 valkey 8.0.4-1 versions antérieures à 8.0.6-1 cbl2 binutil

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

d?id=CVE-2024-28956 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-43840 https://www.cve.org/CVERecord?id=CVE-2024-43840 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-57945 https://www.cve.org/CVERecord?id=CVE-2024-57945 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-37819 https://www.cve.org/CVERecord?id=CVE-2025-37819 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-37897 https://www.cve.org/CVERecord?id=CVE-2025-37897 Référence CVE CVE-2025-37901 https://www.cve.org/CVERecord?id=CVE-2025-37901 Référence CVE CVE-2025-37903 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-28956 Référence CVE CVE-2024-35790 https://www.cve.org/CVERecord?id=CVE-2024-35790 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-43840 https://www.cve.org/CVERecord?id=CVE-2024-43840 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-53203 https://www.cve.org/CVERecord?id=CVE-2024-53203 Référence CVE CVE-2024-53209 https://www.cve.org/CVERecord?id=CVE-2024-53209 Référence CVE CVE-2024-57945 https://www.cve.org/CVERecord?id=CVE-2024-57945 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-37819 https://www.cve.org/CVERecord?id=CVE-2025-37819 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-37897 https://www.cve.org/CVERecord?id=CVE-2025-37897 Référence CVE CVE-2025-37901 https://www.cve.org/CVERecord?id=CVE-2025-37901 Référence CVE CVE-2025-37902 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21635 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CVE-2025-21639 Référence CVE CVE-2025-21640 https://www.cve.org/CVERecord?id=CVE-2025-21640 Référence CVE CVE-2025-21642 https://www.cve.org/CVERecord?id=CVE-2025-21642 Référence CVE CVE-2025-21643 https://www.cve.org/CVERecord?id=CVE-2025-21643 Référence CVE CVE-2025-21644 https://www.cve.org/CVERecord?id=CVE-2025-21644 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21646 https://www.cve.org/CVERecord?id=CVE-2025-21646 Référence CVE CVE-2025-21647 https://www.cve.org/CVERecord?id=CVE-2025-21647 Référence CVE CVE-2025-21648 https://www.cve.org/CVERecord?id=CVE-2025-21648 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21650 https://www.cve.org/CVERecord?id=CVE-2025-21650 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21652 https://www.cve.org/CVERecord?id=CVE-2025-21652 Référence CVE CVE-2025-21653 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2024-57932 Référence CVE CVE-2024-57933 https://www.cve.org/CVERecord?id=CVE-2024-57933 Référence CVE CVE-2024-57935 https://www.cve.org/CVERecord?id=CVE-2024-57935 Référence CVE CVE-2024-57936 https://www.cve.org/CVERecord?id=CVE-2024-57936 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2025-21632 https://www.cve.org/CVERecord?id=CVE-2025-21632 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21646 https://www.cve.org/CVERecord?id=CVE-2025-21646 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21650 https://www.cve.org/CVERecord?id=CVE-2025-21650 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21652 https://www.cve.org/CVERecord?id=CVE-2025-21652 Référence CVE CVE-2025-21653 https://www.cve.org/CVERecord?id=CVE-2025-21653 Référence CVE CVE-2025-21655 https://www.cve.org/CVERecord?id=CVE-2025-21655 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57931 Référence CVE CVE-2024-57932 https://www.cve.org/CVERecord?id=CVE-2024-57932 Référence CVE CVE-2024-57933 https://www.cve.org/CVERecord?id=CVE-2024-57933 Référence CVE CVE-2024-57935 https://www.cve.org/CVERecord?id=CVE-2024-57935 Référence CVE CVE-2024-57936 https://www.cve.org/CVERecord?id=CVE-2024-57936 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2025-21632 https://www.cve.org/CVERecord?id=CVE-2025-21632 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21646 https://www.cve.org/CVERecord?id=CVE-2025-21646 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21650 https://www.cve.org/CVERecord?id=CVE-2025-21650 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21652 https://www.cve.org/CVERecord?id=CVE-2025-21652 Référence CVE CVE-2025-21653 https://www.cve.org/CVERecord?id=CVE-2025-21653 Référence CVE CVE-2025-21655 https://www.cve.org/CVERecord?id=CVE-2025-21655 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2024-57926 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57932 https://www.cve.org/CVERecord?id=CVE-2024-57932 Référence CVE CVE-2024-57933 https://www.cve.org/CVERecord?id=CVE-2024-57933 Référence CVE CVE-2024-57935 https://www.cve.org/CVERecord?id=CVE-2024-57935 Référence CVE CVE-2024-57936 https://www.cve.org/CVERecord?id=CVE-2024-57936 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2025-21632 https://www.cve.org/CVERecord?id=CVE-2025-21632 Référence CVE CVE-2025-21645 https://www.cve.org/CVERecord?id=CVE-2025-21645 Référence CVE CVE-2025-21646 https://www.cve.org/CVERecord?id=CVE-2025-21646 Référence CVE CVE-2025-21649 https://www.cve.org/CVERecord?id=CVE-2025-21649 Référence CVE CVE-2025-21650 https://www.cve.org/CVERecord?id=CVE-2025-21650 Référence CVE CVE-2025-21651 https://www.cve.org/CVERecord?id=CVE-2025-21651 Référence CVE CVE-2025-21656 https://www.cve.org/CVERecord?id=CVE-2025-21656 Référence CVE CVE-2025-21662 https://www.cve.org/CVERecord?id=CVE-2025-21662 Gestion détaillée du document le 31 janvier 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-016861Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

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: < 6.2, 6.1.140 ≤ 6.1.*, 6.6.72 ≤ 6.6.*, 6.12.10 ≤ 6.12.*, 6.13 ≤ *
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 19 Jan 2025 · Last source change 8 Sept 2026, 08:40 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-2594
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
    72e5a83b7c8401856cc3732150af24e43726717a < ab47d72b736e78d3c2370b26e0bfc46eb0918391; 8e60615e8932167057b363c11a7835da7f007106 < 5cc621085e2b7a9b1905a98f8e5a86bb4aea2016; 8e60615e8932167057b363c11a7835da7f007106 < b25778c87a6bce40c31e92364f08aa6240309e25; 8e60615e8932167057b363c11a7835da7f007106 < dd410d784402c5775f66faf8b624e85e41c38aaf; 3fc9dc0340e0b5df8059313537b55f82c1e84e94; 6.1.11 < 6.1.140; 5.15.95 < 5.16; 6.2 · Fixed: < 6.2; 6.1.140 ≤ 6.1.*; 6.6.72 ≤ 6.6.*; 6.12.10 ≤ 6.12.*; 6.13 ≤ *
    After
    Linux: 72e5a83b7c8401856cc3732150af24e43726717a < ab47d72b736e78d3c2370b26e0bfc46eb0918391, 8e60615e8932167057b363c11a7835da7f007106 < 5cc621085e2b7a9b1905a98f8e5a86bb4aea2016, 8e60615e8932167057b363c11a7835da7f007106 < b25778c87a6bce40c31e92364f08aa6240309e25, 8e60615e8932167057b363c11a7835da7f007106 < dd410d784402c5775f66faf8b624e85e41c38aaf, 3fc9dc0340e0b5df8059313537b55f82c1e84e94, 6.1.11 < 6.1.140, 5.15.95 < 5.16, 6.2 · Fixed: Linux: < 6.2, 6.1.140 ≤ 6.1.*, 6.6.72 ≤ 6.6.*, 6.12.10 ≤ 6.12.*, 6.13 ≤ *
    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-2594↗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-21645 · cve.blacktree.nl