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

mm: swap: fix potential buffer overflow in setup_clusters()

Linux · Linux

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 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 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 13 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.

17 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 13 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-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-oem-6.14Affected, 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-oracle-6.14Affected, 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
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-31502

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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 13 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: mm: swap: fix potential buffer overflow in setup_clusters() In setup_swap_map(), we only ensure badpages are in range (0, last_page]. As maxpages might be < last_page, setup_clusters() will encounter a buffer overflow when a badpage is >= maxpages. Only call inc_cluster_info_page() for badpage which is < maxpages to fix the issue.

What

In the Linux kernel, the following vulnerability has been resolved: mm: swap: fix potential buffer overflow in setup_clusters() In setup_swap_map(), we only ensure badpages are in range (0, last_page]. As maxpages might be < last_page, setup_clusters() will encounter a buffer overflow when a badpage is >= maxpages. Only call inc_cluster_info_page() for badpage which is < maxpages to fix the issue.

Why

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

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: mm: swap: fix potential buffer overflow in setup_clusters() In setup_swap_map(), we only ensure badpages are in range (0, last_page]. As maxpages might be < last_page, setup_clusters() will encounter a buffer overflow when a badpage is >= maxpages. Only call inc_cluster_info_page() for badpage which is < maxpages to fix the issue.

Why

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

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 → Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') → 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-120 ↗

CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'). The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

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-120
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1988Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

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-2025-AVI-1135Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39702 Référence CVE CVE-2025-39703 https://www.cve.org/CVERecord?id=CVE-2025-39703 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39725 https://www.cve.org/CVERecord?id=CVE-2025-39725 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39728 https://www.cve.org/CVERecord?id=CVE-2025-39728 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39735 https://www.cve.org/CVERecord?id=CVE-2025-39735 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 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-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39722 https://www.cve.org/CVERecord?id=CVE-2025-39722 Référence CVE CVE-2025-39723 https://www.cve.org/CVERecord?id=CVE-2025-39723 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 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-39702 Référence CVE CVE-2025-39703 https://www.cve.org/CVERecord?id=CVE-2025-39703 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39725 https://www.cve.org/CVERecord?id=CVE-2025-39725 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38666 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38678 https://www.cve.org/CVERecord?id=CVE-2025-38678 Référence CVE CVE-2025-39682 https://www.cve.org/CVERecord?id=CVE-2025-39682 Référence CVE CVE-2025-39725 https://www.cve.org/CVERecord?id=CVE-2025-39725 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39728 https://www.cve.org/CVERecord?id=CVE-2025-39728 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39735 https://www.cve.org/CVERecord?id=CVE-2025-39735 Référence CVE CVE-2025-39809 https://www.cve.org/CVERecord?id=CVE-2025-39809 Référence CVE CVE-2025-39818 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37797 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38550 https://www.cve.org/CVERecord?id=CVE-2025-38550 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38614 https://www.cve.org/CVERecord?id=CVE-2025-38614 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-39697 https://www.cve.org/CVERecord?id=CVE-2025-39697 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=CVE-2025-39751 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39849 https://www.cve.org/CVERecord?id=CVE-2025-39849 Référence CVE CVE-2025-39864 https://www.cve.org/CVERecord?id=CVE-2025-39864 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-020674Linux の 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
Linux: b843786b0bd01ced7fcdbf3b033d68db2f7c61b2 < 91b370800b3f2b3dda244c0ab06719c4971190a5, b843786b0bd01ced7fcdbf3b033d68db2f7c61b2 < 9b01ada580ee84fb319e7ecb5fb5b1f54a9eb799, b843786b0bd01ced7fcdbf3b033d68db2f7c61b2 < 815c528b13f2bb9b3130c13bedeabf2351a68129, b843786b0bd01ced7fcdbf3b033d68db2f7c61b2 < 152c1339dc13ad46f1b136e8693de15980750835, 6.12
Fixed
Linux: < 6.12, 6.12.42 ≤ 6.12.*, 6.15.10 ≤ 6.15.*, 6.16.1 ≤ 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 7 Sept 2025 · Last source change 11 May 2026, 21:35 UTC · CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

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-31502
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-39727 · cve.blacktree.nl