FKIE_CVE-2026-99483
Vulnerability from fkie_nvd - Published: 2026-11-19 15:18 - Updated: 2026-11-19 15:18| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"sound/drivers/pcmtest.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "8f8555e03bb2596b0d521c5b95c72cbd76e7d9af",
"status": "affected",
"version": "315a3d57c64c55901d6fe5a5eef3b3e51d215381",
"versionType": "git"
},
{
"lessThan": "5cb07a5941b1e3dbe655110618869a81af68907e",
"status": "affected",
"version": "315a3d57c64c55901d6fe5a5eef3b3e51d215381",
"versionType": "git"
},
{
"lessThan": "76319a56f069bb950d9cebbc1a291cbfa94a1c1f",
"status": "affected",
"version": "315a3d57c64c55901d6fe5a5eef3b3e51d215381",
"versionType": "git"
},
{
"lessThan": "6541871e8e63e721733cd120af4d9cd22c5ef62f",
"status": "affected",
"version": "315a3d57c64c55901d6fe5a5eef3b3e51d215381",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"sound/drivers/pcmtest.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.5"
},
{
"lessThan": "6.5",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: pcmtest: handle multiple wraps in random capture fill\n\nThe random capture helpers assume that the data generated for one timer\ntick wraps the DMA ring at most once. However, b_rw describes 200 ms of\naudio because the timer runs at 5 Hz, so it can be several times larger\nthan a small ring.\n\nFor 48 kHz, S16_LE, four-channel capture with a 512-frame buffer, the DMA\nring is 4096 bytes while one tick generates 76800 bytes. After filling the\n4096-byte tail, the existing code issues a second 72704-byte write from the\nring base, writing 68608 bytes beyond the ring. Both interleaved and\nnon-interleaved capture are affected.\n\nKASAN reports the first write into the adjacent free page as a\nuse-after-free in the random-byte generator. The underlying defect is an\nout-of-bounds write from the live DMA ring, not a stale DMA allocation.\n\nSplit each random write repeatedly at the interleaved ring or per-channel\nblock boundary. Keep the hardware-pointer update exactly once after the\ncomplete logical write.\n\nThe issue reproduced on three of three clean boots. With this change, the\nsame vulnerable geometry completed six times without a sanitizer finding.\nBoundary, pattern-fill, no-timer, open/close, and module-reload controls\nalso completed normally.\n\nsnd-pcmtest is a test driver, and selecting random fill requires an\nadministrator-controlled module parameter. The written values come from the\nkernel random generator; no privilege escalation or attacker-controlled\nwrite primitive was demonstrated."
}
],
"id": "CVE-2026-99483",
"lastModified": "2026-11-19T15:18:03.027",
"metrics": {},
"published": "2026-11-19T15:18:03.027",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5cb07a5941b1e3dbe655110618869a81af68907e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6541871e8e63e721733cd120af4d9cd22c5ef62f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/76319a56f069bb950d9cebbc1a291cbfa94a1c1f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8f8555e03bb2596b0d521c5b95c72cbd76e7d9af"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.