JLSEC-2026-97
- Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-97.md
- Import Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-97.json
- JSON Data
- https://api.osv.dev/v1/vulns/JLSEC-2026-97
- Upstream
- Published
- 2026-04-14T12:58:25.609Z
- Modified
- 2026-04-14T13:00:08.794845Z
- Summary
- [none]
- Details
-
An internal reference count is held on the buffer pool, incremented every time a new buffer is created from the pool. The reference count is maintained as an int; on LP64 systems this can cause the reference count to overflow if the client creates a large number of wlshm buffer objects, or if it can coerce the server to create a large number of external references to the buffer storage. With the reference count overflowing, a use-after-free can be constructed on the wlshm_pool tracking structure, where values may be incremented or decremented; it may also be possible to construct a limited oracle to leak 4 bytes of server-side memory to the attacking client at a time.
- Database specific
{ "license": "CC-BY-4.0", "sources": [ { "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3782", "id": "CVE-2021-3782", "modified": "2025-05-22T19:15:27.303Z", "imported": "2026-04-14T04:05:28.256Z", "published": "2022-09-23T16:15:10.143Z", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2021-3782" } ] }- References