osv-2026-795
Vulnerability from osv_ossfuzz
Published
2026-05-22 00:16
Modified
2026-05-22 00:16
Summary
Stack-buffer-underflow in probe_dasd_pt
Details

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=514896889

Crash type: Stack-buffer-underflow READ 1
Crash state:
probe_dasd_pt
idinfo_probe
partitions_probe

{
  "affected": [
    {
      "database_specific": {
        "fixed_range": "5683ed6320e00205146cbb3d0c76462733530eca:eee2e7f2cfb158599609fad8d831105d68a6ed8d",
        "introduced_range": "fe5eaa3caa48ec4ac917d2d2c18fccc2d388b291:e2687bcc0fcf412e5fa2424e3a4348c052e8684c"
      },
      "ecosystem_specific": {
        "severity": null
      },
      "package": {
        "ecosystem": "OSS-Fuzz",
        "name": "util-linux",
        "purl": "pkg:generic/util-linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "c408b657283fdedcdf3d4961c007805077b72bc9"
            },
            {
              "fixed": "eee2e7f2cfb158599609fad8d831105d68a6ed8d"
            }
          ],
          "repo": "https://github.com/util-linux/util-linux",
          "type": "GIT"
        }
      ],
      "versions": []
    }
  ],
  "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=514896889\n\n```\nCrash type: Stack-buffer-underflow READ 1\nCrash state:\nprobe_dasd_pt\nidinfo_probe\npartitions_probe\n```\n",
  "id": "OSV-2026-795",
  "modified": "2026-05-22T00:16:21.905075Z",
  "published": "2026-05-22T00:16:21.904778Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=514896889"
    }
  ],
  "schema_version": "1.7.5",
  "summary": "Stack-buffer-underflow in probe_dasd_pt"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…