{
  "schemaVersion": 1,
  "attribution": [
    {
      "source": "CISA Known Exploited Vulnerabilities",
      "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
      "licence": "US government work"
    },
    {
      "source": "GitHub Advisory Database",
      "url": "https://github.com/advisories",
      "licence": "CC BY 4.0"
    },
    {
      "source": "Have I Been Pwned",
      "url": "https://haveibeenpwned.com/",
      "licence": "CC BY 4.0"
    },
    {
      "source": "CVE Program (CVE records)",
      "url": "https://www.cve.org/Legal/TermsOfUse",
      "licence": "CVE Terms of Use",
      "notice": "Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation.",
      "terms": "CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE™). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy."
    },
    {
      "source": "FIRST EPSS",
      "url": "https://www.first.org/epss/",
      "licence": "free to use; FIRST requests attribution"
    }
  ],
  "record": {
    "id": "CVE-2026-58098",
    "sourceURL": "https://www.cve.org/CVERecord?id=CVE-2026-58098",
    "idYear": 2026,
    "status": "PUBLISHED",
    "publishedAt": "2026-10-15T06:15:44.878Z",
    "updatedAt": "2026-10-16T14:16:45.049Z",
    "importedAt": "2026-10-24T01:58:20.586Z",
    "snapshot": {
      "id": "cve_2026-10-24_midnight_baseline",
      "at": "2026-10-24T00:00:00.000Z",
      "source": "https://github.com/CVEProject/cvelistV5/releases/tag/cve_2026-10-24_0100Z"
    },
    "facts": {
      "title": "Heap out-of-bounds access in semop(2)",
      "summary": "When semop(2) blocks waiting for a semaphore condition, it releases the per-set lock and sleeps.  Upon waking, it checks the sequence number embedded in the semaphore set's IPC identifier to detect whether the set was removed while the caller was asleep.  This sequence number is only 15 bits wide.  If enough semaphore sets are created and destroyed in the same table slot while a caller is blocked, the counter wraps around, and semop(2) may falsely conclude that the original set still exists.  The subsequent access to a semaphore within the set may then be out of bounds.\n\nAn unprivileged local user can trigger an out-of-bounds access on kernel heap memory, potentially leading to privilege escalation.",
      "affected": [
        {
          "vendor": "FreeBSD",
          "product": "FreeBSD",
          "defaultStatus": "unknown",
          "versions": [
            {
              "version": "15.1-RELEASE",
              "status": "affected",
              "versionType": "release",
              "lessThan": "p4"
            },
            {
              "version": "15.0-RELEASE",
              "status": "affected",
              "versionType": "release",
              "lessThan": "p14"
            },
            {
              "version": "14.5-RELEASE",
              "status": "affected",
              "versionType": "release",
              "lessThan": "p1"
            },
            {
              "version": "14.4-RELEASE",
              "status": "affected",
              "versionType": "release",
              "lessThan": "p10"
            }
          ]
        }
      ]
    }
  }
}