{"api_version":"1","generated_at":"2026-10-16T08:09:30+00:00","cve":"CVE-2026-58098","urls":{"html":"https://cve.report/CVE-2026-58098","api":"https://cve.report/api/cve/CVE-2026-58098.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-58098","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-58098"},"summary":{"title":"Heap out-of-bounds access in semop(2)","description":"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.","state":"PUBLISHED","assigner":"freebsd","published_at":"2026-10-15 07:18:02","updated_at":"2026-10-16 04:18:32"},"problem_types":["CWE-787","CWE-787 CWE-787: Out-of-bounds Write"],"metrics":[],"references":[{"url":"https://security.freebsd.org/advisories/FreeBSD-SA-26:64.sysvsem.asc","name":"https://security.freebsd.org/advisories/FreeBSD-SA-26:64.sysvsem.asc","refsource":"secteam@freebsd.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-58098","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-58098","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 15.1-RELEASE p4 release","platforms":[]},{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 15.0-RELEASE p14 release","platforms":[]},{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 14.5-RELEASE p1 release","platforms":[]},{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 14.4-RELEASE p10 release","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Reo Shiseki","lang":"en"},{"source":"CNA","value":"Andrew Griffiths","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-58098","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-10-15T00:00:00+00:00","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-10-16T03:56:54.414Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"defaultStatus":"unknown","modules":["sysvsem"],"product":"FreeBSD","vendor":"FreeBSD","versions":[{"lessThan":"p4","status":"affected","version":"15.1-RELEASE","versionType":"release"},{"lessThan":"p14","status":"affected","version":"15.0-RELEASE","versionType":"release"},{"lessThan":"p1","status":"affected","version":"14.5-RELEASE","versionType":"release"},{"lessThan":"p10","status":"affected","version":"14.4-RELEASE","versionType":"release"}]}],"credits":[{"lang":"en","type":"finder","value":"Reo Shiseki"},{"lang":"en","type":"finder","value":"Andrew Griffiths"}],"datePublic":"2026-09-29T20:30:00.000Z","descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-787","description":"CWE-787: Out-of-bounds Write","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-15T06:15:44.878Z","orgId":"63664ac6-956c-4cba-a5d0-f46076e16109","shortName":"freebsd"},"references":[{"tags":["vendor-advisory"],"url":"https://security.freebsd.org/advisories/FreeBSD-SA-26:64.sysvsem.asc"}],"title":"Heap out-of-bounds access in semop(2)","x_generator":{"engine":"cvelib 1.8.0"}}},"cveMetadata":{"assignerOrgId":"63664ac6-956c-4cba-a5d0-f46076e16109","assignerShortName":"freebsd","cveId":"CVE-2026-58098","datePublished":"2026-10-15T06:15:44.878Z","dateReserved":"2026-06-29T01:40:17.499Z","dateUpdated":"2026-10-16T03:56:54.414Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-15 07:18:02","lastModifiedDate":"2026-10-16 04:18:32","problem_types":["CWE-787","CWE-787 CWE-787: Out-of-bounds Write"],"metrics":{"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-10-15T00:00:00+00:00","id":"CVE-2026-58098","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"58098","Ordinal":"1","Title":"Heap out-of-bounds access in semop(2)","CVE":"CVE-2026-58098","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"58098","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Heap out-of-bounds access in semop(2)"}]}}}