TOCTOU race between sound(4) buffer resizing and mmap
CVSS score
—
EPSS probability
—
Risk score
—
Published
2 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
CVE AI research
DayBreach AI Explanation
Verified against sourcesSources read
2
Source agreement
Tam uyum
Evidence confidence
%63
Short explanation
A TOCTOU race condition exists between the sound(4) driver buffer resizing process and the mmap(2) call. A local user can trigger a use-after-free in the kernel with potential privilege escalation.
An unprivileged local user with sound device access triggering a use-after-free in the kernel can potentially escalate privileges and compromise system security.
What should be done?
- Follow the provided official vendor advisory
- Monitor vendor channels for update and patch status details
- Restrict local user access permissions to sound devices
Chain of evidence and sources
sound(4) sürücüsündeki arabellek yeniden boyutlandırma ve mmap işlemleri arasında bir TOCTOU yarış durumu mevcuttur.
Yetkisiz bir yerel kullanıcı bu yarış durumunu kullanarak çekirdekte bir use-after-free tetikleyebilir ve potansiyel olarak ayrıcalıkları yükseltebilir.
Etkilenen ürünler arasında belirli FreeBSD 15.1, 14.5 ve 14.4 sürümleri yer almaktadır.
Show the technical text from the sources
When an audio channel's buffer needs to be resized, the sound(4) driver checks that the buffer is not memory-mapped and then drops the channel lock to allocate a new buffer. An mmap(2) call on another thread can complete during this window, after which the resize path frees the now-mapped buffer without rechecking. An unprivileged local user with access to a sound device can exploit this race to trigger a use-after-free in the kernel, potentially escalating privileges.
CWE: CWE-367
Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-101308 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | freebsd | freebsd | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-101308 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-101308 weaknesses.
Official Sources and Advisories
Similar Vulnerabilities
Openssh: regresshion - race condition in ssh allows rce/dos
Vulnerability in N/a
Segmentation fault in SSL_check_chain
NULL pointer deref in signature_algorithms processing
Path traversal in N/a
CA certificate check bypass with X509_V_FLAG_X509_STRICT
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-101308"