ubuntu-cve-2025-34297
Vulnerability from osv_ubuntu
Published
2025-12-01 19:15
Modified
2026-05-20 15:17
Summary
Details
KissFFT versions prior to the fix commit 1b083165 contain an integer overflow in kiss_fft_alloc() in kiss_fft.c on platforms where size_t is 32-bit. The nfft parameter is not validated before being used in a size calculation (sizeof(kiss_fft_cpx) * (nfft - 1)), which can wrap to a small value when nfft is large. As a result, malloc() allocates an undersized buffer and the subsequent twiddle-factor initialization loop writes nfft elements, causing a heap buffer overflow. This vulnerability only affects 32-bit architectures.
Severity
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kissfft-tools",
"binary_version": "131.1.0-2"
},
{
"binary_name": "libkissfft-float131",
"binary_version": "131.1.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "kissfft",
"purl": "pkg:deb/ubuntu/kissfft@131.1.0-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"131.1.0-1",
"131.1.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kissfft-tools",
"binary_version": "131.1.0-3build2"
},
{
"binary_name": "libkissfft-float131",
"binary_version": "131.1.0-3build2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "kissfft",
"purl": "pkg:deb/ubuntu/kissfft@131.1.0-3build2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"131.1.0-3",
"131.1.0-3build1",
"131.1.0-3build2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kissfft-tools",
"binary_version": "131.1.0-3build2"
},
{
"binary_name": "libkissfft-float131",
"binary_version": "131.1.0-3build2"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "kissfft",
"purl": "pkg:deb/ubuntu/kissfft@131.1.0-3build2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"131.1.0-3build2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kissfft-tools",
"binary_version": "131.1.0-4"
},
{
"binary_name": "libkissfft-float131",
"binary_version": "131.1.0-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "kissfft",
"purl": "pkg:deb/ubuntu/kissfft@131.1.0-4?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"131.1.0-3build2",
"131.1.0-4"
]
}
],
"aliases": [],
"details": "KissFFT versions prior to the fix commit 1b083165 contain an integer overflow in kiss_fft_alloc() in kiss_fft.c on platforms where size_t is 32-bit. The nfft parameter is not validated before being used in a size calculation (sizeof(kiss_fft_cpx) * (nfft - 1)), which can wrap to a small value when nfft is large. As a result, malloc() allocates an undersized buffer and the subsequent twiddle-factor initialization loop writes nfft elements, causing a heap buffer overflow. This vulnerability only affects 32-bit architectures.",
"id": "UBUNTU-CVE-2025-34297",
"modified": "2026-05-20T15:17:33Z",
"published": "2025-12-01T19:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2025-34297"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-34297"
},
{
"type": "REPORT",
"url": "https://github.com/mborgerding/kissfft/issues/120"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2025-34297"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…