Security readout for executives and security teams
Plain-English summary
CVE-2025-34297 is a memory corruption flaw in KissFFT on 32-bit platforms. A very large FFT size can make allocation math wrap, creating a too-small heap buffer that later gets overwritten. This matters most where KissFFT is embedded in products processing attacker-influenced signal, audio, or scientific data sizes.
Executive priority
Prioritize remediation for 32-bit products or appliances that process user-supplied data through KissFFT. Deprioritize confirmed 64-bit-only deployments, but still inventory vendored copies because downstream packaging may obscure exposure.
Technical view
In kiss_fft_alloc(), nfft is not validated before sizeof(kiss_fft_cpx) * (nfft - 1). On 32-bit size_t platforms, large nfft values can overflow allocation sizing. malloc() can return an undersized buffer, while twiddle initialization writes nfft elements, causing heap overflow. Sources identify fix commit 1b083165.
Likely exposure
Exposure appears limited to 32-bit architectures using KissFFT versions before commit 1b083165, especially applications that let local users or input files influence nfft. The provided data does not identify specific downstream products, packages, or release versions beyond the upstream repository.
Exploitation context
The CVSS vector is local, low complexity, no privileges, and no user interaction. The source bundle says KEV is false and provides no evidence of active exploitation. Treat exploitation status as unconfirmed, not actively exploited.
Researcher notes
The key condition is 32-bit size_t plus attacker-influenced large nfft. The affected-version data in the bundle is sparse, so avoid assuming package names or release ranges. Analysis should focus on commit presence, architecture, and call paths into kiss_fft_alloc().
Mitigation direction
- Update KissFFT to include commit 1b083165 or a vendor release containing it.
- Inventory embedded or vendored KissFFT copies in 32-bit builds.
- Check vendor guidance for downstream packages using KissFFT.
- Restrict untrusted control over FFT sizes where immediate updating is unavailable.
Validation and detection
- Confirm whether any deployed build uses 32-bit size_t.
- Search source and dependencies for vendored mborgerding/kissfft copies.
- Verify kiss_fft_alloc() includes the upstream bounds fix from commit 1b083165.
- Review tests or callers that pass untrusted nfft values into KissFFT.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-34297 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.6HighVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/mborgerding/kissfft/commit/1b08316582049c3716154caefc0deab8758506e3CVE reference, VulnCheck · patch
- https://github.com/mborgerding/kissfft/issues/120CVE reference, VulnCheck · issue-tracking
- https://www.vulncheck.com/advisories/kissfft-integer-overflow-heap-buffer-overflowCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.