CVE-2026-99447 (GCVE-0-2026-99447)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:41 – Updated: 2026-11-19 14:41| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
9538edeb72c989a4b90964ae4bba107eaf21a791 , < 733552f8c5f5fdce6b2a135dfa2a05ead9f66e91
(git)
Affected: 9538edeb72c989a4b90964ae4bba107eaf21a791 , < d858330e288a7818cf6d52ed1bd62153f4cd35c0 (git) Affected: 9538edeb72c989a4b90964ae4bba107eaf21a791 , < 0b591332a2bdc13d3f9163793131fe3651d1556a (git) |
guessed | |
| Linux | Linux |
Affected:
6.9
Unaffected: 0 , < 6.9 (semver) Unaffected: 6.18.61 , ≤ 6.18.* (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/spi/spi-pci1xxxx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "733552f8c5f5fdce6b2a135dfa2a05ead9f66e91",
"status": "affected",
"version": "9538edeb72c989a4b90964ae4bba107eaf21a791",
"versionType": "git"
},
{
"lessThan": "d858330e288a7818cf6d52ed1bd62153f4cd35c0",
"status": "affected",
"version": "9538edeb72c989a4b90964ae4bba107eaf21a791",
"versionType": "git"
},
{
"lessThan": "0b591332a2bdc13d3f9163793131fe3651d1556a",
"status": "affected",
"version": "9538edeb72c989a4b90964ae4bba107eaf21a791",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/spi/spi-pci1xxxx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.9"
},
{
"lessThan": "6.9",
"status": "unaffected",
"version": "0",
"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"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "6.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "6.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: spi-pci1xxxx: quiesce DMA engines on transfer timeout\n\nIf a DMA-mapped transfer times out waiting for DMA_TERM and neither DMA\nabort interrupt arrived, pci1xxxx_spi_transfer_with_dma() returns\nthrough the error label while both DMA engines are still enabled, the\ndone/abort interrupt status is still armed and the transfer state\n(p-\u003exfer, p-\u003etx_sgl, p-\u003erx_sgl) is still registered.\n\nThe ISRs keep firing afterwards: they reprogram the DMA engines from\np-\u003etx_sgl / p-\u003erx_sgl and signal completion through p-\u003exfer and\np-\u003espi_xfer_done, all of which the SPI core is free to unmap or reuse\nonce transfer_one() has returned, which is a use-after-free. A late\ndone interrupt can also start the next transfer queued behind the\nfailed one.\n\nStop both DMA engines, drain the pending done/abort interrupt status\nand synchronize the DMA IRQs before dropping the in-progress state and\nthe transfer pointers, and re-enable the engines afterwards so that\nsubsequent transfers keep working. The engines are only turned back on\nonce both were confirmed to have stopped: re-enabling an engine that\nfailed to stop would cancel the pending stop request and let it keep\nrunning into buffers the SPI core is about to unmap or free, which is\nexactly the window this patch closes. An engine that failed to stop is\nleft disabled, as the abort paths already do.\n\nThe DMA interrupt status and mask registers are shared between the two\nSPI instances, so the cleanup drains only this instance\u0027s done/abort\nstatus bits instead of masking the interrupt lines, which would also\nsuppress the peer instance\u0027s completion interrupts.\n\nAlso make the DMA ISRs ignore interrupts while no transfer is in\nprogress so that a stray MSI after the cleanup can no longer act on\nthe cleared state.\n\nNo PCI1XXXX hardware was available for testing and QEMU has no model\nof this PCIe part, so the timeout path was exercised with a userspace\nreplica of the timeout branch and the DMA ISRs, with the register and\ninterrupt accesses mocked: on the unfixed code both a wedged engine\nthat clears after the timeout and a late done interrupt touch the\nfreed transfer state, while with this fix applied neither does and an\nengine that failed to stop is left disabled. The module was also\nloaded and unloaded in a QEMU x86_64 guest running a kernel with this\nfix applied."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:41:36.666Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/733552f8c5f5fdce6b2a135dfa2a05ead9f66e91"
},
{
"url": "https://git.kernel.org/stable/c/d858330e288a7818cf6d52ed1bd62153f4cd35c0"
},
{
"url": "https://git.kernel.org/stable/c/0b591332a2bdc13d3f9163793131fe3651d1556a"
}
],
"title": "spi: spi-pci1xxxx: quiesce DMA engines on transfer timeout",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99447",
"datePublished": "2026-11-19T14:41:36.666Z",
"dateReserved": "2026-09-25T10:25:14.415Z",
"dateUpdated": "2026-11-19T14:41:36.666Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99447",
"date": "2026-11-20",
"epss": "0.00174",
"percentile": "0.07039"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/spi/spi-pci1xxxx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "733552f8c5f5fdce6b2a135dfa2a05ead9f66e91",
"status": "affected",
"version": "9538edeb72c989a4b90964ae4bba107eaf21a791",
"versionType": "git"
},
{
"lessThan": "d858330e288a7818cf6d52ed1bd62153f4cd35c0",
"status": "affected",
"version": "9538edeb72c989a4b90964ae4bba107eaf21a791",
"versionType": "git"
},
{
"lessThan": "0b591332a2bdc13d3f9163793131fe3651d1556a",
"status": "affected",
"version": "9538edeb72c989a4b90964ae4bba107eaf21a791",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/spi/spi-pci1xxxx.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.9"
},
{
"lessThan": "6.9",
"status": "unaffected",
"version": "0",
"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\nspi: spi-pci1xxxx: quiesce DMA engines on transfer timeout\n\nIf a DMA-mapped transfer times out waiting for DMA_TERM and neither DMA\nabort interrupt arrived, pci1xxxx_spi_transfer_with_dma() returns\nthrough the error label while both DMA engines are still enabled, the\ndone/abort interrupt status is still armed and the transfer state\n(p-\u003exfer, p-\u003etx_sgl, p-\u003erx_sgl) is still registered.\n\nThe ISRs keep firing afterwards: they reprogram the DMA engines from\np-\u003etx_sgl / p-\u003erx_sgl and signal completion through p-\u003exfer and\np-\u003espi_xfer_done, all of which the SPI core is free to unmap or reuse\nonce transfer_one() has returned, which is a use-after-free. A late\ndone interrupt can also start the next transfer queued behind the\nfailed one.\n\nStop both DMA engines, drain the pending done/abort interrupt status\nand synchronize the DMA IRQs before dropping the in-progress state and\nthe transfer pointers, and re-enable the engines afterwards so that\nsubsequent transfers keep working. The engines are only turned back on\nonce both were confirmed to have stopped: re-enabling an engine that\nfailed to stop would cancel the pending stop request and let it keep\nrunning into buffers the SPI core is about to unmap or free, which is\nexactly the window this patch closes. An engine that failed to stop is\nleft disabled, as the abort paths already do.\n\nThe DMA interrupt status and mask registers are shared between the two\nSPI instances, so the cleanup drains only this instance\u0027s done/abort\nstatus bits instead of masking the interrupt lines, which would also\nsuppress the peer instance\u0027s completion interrupts.\n\nAlso make the DMA ISRs ignore interrupts while no transfer is in\nprogress so that a stray MSI after the cleanup can no longer act on\nthe cleared state.\n\nNo PCI1XXXX hardware was available for testing and QEMU has no model\nof this PCIe part, so the timeout path was exercised with a userspace\nreplica of the timeout branch and the DMA ISRs, with the register and\ninterrupt accesses mocked: on the unfixed code both a wedged engine\nthat clears after the timeout and a late done interrupt touch the\nfreed transfer state, while with this fix applied neither does and an\nengine that failed to stop is left disabled. The module was also\nloaded and unloaded in a QEMU x86_64 guest running a kernel with this\nfix applied."
}
],
"id": "CVE-2026-99447",
"lastModified": "2026-11-19T15:17:58.400",
"metrics": {},
"published": "2026-11-19T15:17:58.400",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0b591332a2bdc13d3f9163793131fe3651d1556a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/733552f8c5f5fdce6b2a135dfa2a05ead9f66e91"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d858330e288a7818cf6d52ed1bd62153f4cd35c0"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:51:37+00:00",
"cve": "CVE-2026-99447",
"id": "CVE-2026-99447",
"initial_release_date": "2026-11-19T14:41:36.666000+00:00",
"product_status:known_affected": "2",
"product_status:known_not_affected": "202",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via use-after-free in PCI1xxxx SPI driver upon transfer timeout",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99447.json",
"version": "3"
}
}
}
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.