UBUNTU-CVE-2025-32022 (CVE-2025-32022)

Vulnerability from osv_ubuntu – Published: 2025-05-06 17:16 – Updated: 2026-10-17 09:31 – Source website
VLAI
Details

Finit provides fast init for Linux systems. Finit's urandom plugin has a heap buffer overwrite vulnerability at boot which leads to it overwriting other parts of the heap, possibly causing random instabilities and undefined behavior. The urandom plugin is enabled by default, so this bug affects everyone using Finit 4.2 or later that do not explicitly disable the plugin at build time. This bug is fixed in Finit 4.12. Those who cannot upgrade or backport the fix to urandom.c are strongly recommended to disable the plugin in the call to the configure script.

Upstream
Impacted products
Ecosystem Package Version
Ubuntu:22.04:LTS finit
pkg:deb/ubuntu/finit@4.2-1?arch=source&distro=jammy
Affected: All versions (ecosystem)
4.1-14.2-1
Ubuntu:24.04:LTS finit
pkg:deb/ubuntu/finit@4.7-1build2?arch=source&distro=noble
Affected: All versions (ecosystem)
4.2-14.7-14.7-1build14.7-1build2
Ubuntu:25.10 finit
pkg:deb/ubuntu/finit@4.12-1?arch=source&distro=questing
Affected: All versions (ecosystem)
4.7-34.11-14.12-1
Ubuntu:26.10 finit
pkg:deb/ubuntu/finit@4.14-1?arch=source&distro=stonking
Affected: All versions (ecosystem)
4.14-1
Ubuntu:26.04:LTS finit
pkg:deb/ubuntu/finit@4.14-1?arch=source&distro=resolute
Affected: All versions (ecosystem)
4.12-14.14-1

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "finit",
            "binary_version": "4.2-1"
          },
          {
            "binary_name": "finit-plugins",
            "binary_version": "4.2-1"
          },
          {
            "binary_name": "finit-sysv",
            "binary_version": "4.2-1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "finit",
        "purl": "pkg:deb/ubuntu/finit@4.2-1?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.1-1",
        "4.2-1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "finit",
            "binary_version": "4.7-1build2"
          },
          {
            "binary_name": "finit-plugins",
            "binary_version": "4.7-1build2"
          },
          {
            "binary_name": "finit-sysv",
            "binary_version": "4.7-1build2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "finit",
        "purl": "pkg:deb/ubuntu/finit@4.7-1build2?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.2-1",
        "4.7-1",
        "4.7-1build1",
        "4.7-1build2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "finit",
            "binary_version": "4.12-1"
          },
          {
            "binary_name": "finit-plugins",
            "binary_version": "4.12-1"
          },
          {
            "binary_name": "finit-sysv",
            "binary_version": "4.12-1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:25.10",
        "name": "finit",
        "purl": "pkg:deb/ubuntu/finit@4.12-1?arch=source\u0026distro=questing"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.7-3",
        "4.11-1",
        "4.12-1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "finit",
            "binary_version": "4.14-1"
          },
          {
            "binary_name": "finit-plugins",
            "binary_version": "4.14-1"
          },
          {
            "binary_name": "finit-sysv",
            "binary_version": "4.14-1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.10",
        "name": "finit",
        "purl": "pkg:deb/ubuntu/finit@4.14-1?arch=source\u0026distro=stonking"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.14-1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "finit",
            "binary_version": "4.14-1"
          },
          {
            "binary_name": "finit-plugins",
            "binary_version": "4.14-1"
          },
          {
            "binary_name": "finit-sysv",
            "binary_version": "4.14-1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.04:LTS",
        "name": "finit",
        "purl": "pkg:deb/ubuntu/finit@4.14-1?arch=source\u0026distro=resolute"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.12-1",
        "4.14-1"
      ]
    }
  ],
  "aliases": [],
  "details": "Finit provides fast init for Linux systems. Finit\u0027s urandom plugin has a heap buffer overwrite vulnerability at boot which leads to it overwriting other parts of the heap, possibly causing random instabilities and undefined behavior. The urandom plugin is enabled by default, so this bug affects everyone using Finit 4.2 or later that do not explicitly disable the plugin at build time. This bug is fixed in Finit 4.12. Those who cannot upgrade or backport the fix to urandom.c are strongly recommended to disable the plugin in the call to the `configure` script.",
  "id": "UBUNTU-CVE-2025-32022",
  "modified": "2026-10-17T09:31:46Z",
  "published": "2025-05-06T17:16:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2025-32022"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-32022"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/troglobit/finit/security/advisories/GHSA-fv6v-vw8h-9x79"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/troglobit/finit/commit/3feff37ba51fa0a6a0a06f59682a0918aa5b04de"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:H/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2025-32022"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.