CVE-2026-99499 (GCVE-0-2026-99499)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:43 – Updated: 2026-11-19 14:43| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
f770950a4709af290f314e691897ec0003fbd8ae , < da15d34d6cb9cdca309c59d1ae0f155da31ed2c2
(git)
Affected: f770950a4709af290f314e691897ec0003fbd8ae , < 422d75ad5bc96b8eb9cb3cfd9d68fc685a0a9b75 (git) |
guessed | |
| Linux | Linux |
Affected:
6.19
Unaffected: 0 , < 6.19 (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": [
"arch/s390/pci/pci_irq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "da15d34d6cb9cdca309c59d1ae0f155da31ed2c2",
"status": "affected",
"version": "f770950a4709af290f314e691897ec0003fbd8ae",
"versionType": "git"
},
{
"lessThan": "422d75ad5bc96b8eb9cb3cfd9d68fc685a0a9b75",
"status": "affected",
"version": "f770950a4709af290f314e691897ec0003fbd8ae",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/s390/pci/pci_irq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"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": "7.3.2",
"versionStartIncluding": "6.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/pci: Fix use-after-free race in zpci floating interrupt cleanup\n\nzpci_clear_irq() stops the adapter from raising new interrupts for the\nfunction, but a zpci_floating_irq_handler() already running on another CPU\ncan still be scanning zdev-\u003eaibv when zpci_msi_teardown_floating() releases\nit.\n\nClear the zpci_ibv[] entry so no further handler picks the vector up, then\nwait for a grace period before releasing it. The handler runs inside the\nrcu_read_lock() section that do_airq_interrupt() holds across\nairq-\u003ehandler(), so synchronize_rcu() drains any handler still in flight.\nRelease the vector and free the summary bit only after the grace period, so\nneither can be reused while a reader still holds the old pointer.\n\nzpci_ibv served both delivery modes, indexed by function under\nFLOATING and by cpu under DIRECTED. Only the floating vectors are\npublished to and torn down under the interrupt handler, so split the\ndirected vectors out into zpci_dibv and annotate zpci_ibv __rcu, which\nlets sparse check the accessors above."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:43:47.226Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/da15d34d6cb9cdca309c59d1ae0f155da31ed2c2"
},
{
"url": "https://git.kernel.org/stable/c/422d75ad5bc96b8eb9cb3cfd9d68fc685a0a9b75"
}
],
"title": "s390/pci: Fix use-after-free race in zpci floating interrupt cleanup",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99499",
"datePublished": "2026-11-19T14:43:47.226Z",
"dateReserved": "2026-09-25T10:25:14.418Z",
"dateUpdated": "2026-11-19T14:43:47.226Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/s390/pci/pci_irq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "da15d34d6cb9cdca309c59d1ae0f155da31ed2c2",
"status": "affected",
"version": "f770950a4709af290f314e691897ec0003fbd8ae",
"versionType": "git"
},
{
"lessThan": "422d75ad5bc96b8eb9cb3cfd9d68fc685a0a9b75",
"status": "affected",
"version": "f770950a4709af290f314e691897ec0003fbd8ae",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/s390/pci/pci_irq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.19"
},
{
"lessThan": "6.19",
"status": "unaffected",
"version": "0",
"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\ns390/pci: Fix use-after-free race in zpci floating interrupt cleanup\n\nzpci_clear_irq() stops the adapter from raising new interrupts for the\nfunction, but a zpci_floating_irq_handler() already running on another CPU\ncan still be scanning zdev-\u003eaibv when zpci_msi_teardown_floating() releases\nit.\n\nClear the zpci_ibv[] entry so no further handler picks the vector up, then\nwait for a grace period before releasing it. The handler runs inside the\nrcu_read_lock() section that do_airq_interrupt() holds across\nairq-\u003ehandler(), so synchronize_rcu() drains any handler still in flight.\nRelease the vector and free the summary bit only after the grace period, so\nneither can be reused while a reader still holds the old pointer.\n\nzpci_ibv served both delivery modes, indexed by function under\nFLOATING and by cpu under DIRECTED. Only the floating vectors are\npublished to and torn down under the interrupt handler, so split the\ndirected vectors out into zpci_dibv and annotate zpci_ibv __rcu, which\nlets sparse check the accessors above."
}
],
"id": "CVE-2026-99499",
"lastModified": "2026-11-19T15:18:04.983",
"metrics": {},
"published": "2026-11-19T15:18:04.983",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/422d75ad5bc96b8eb9cb3cfd9d68fc685a0a9b75"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/da15d34d6cb9cdca309c59d1ae0f155da31ed2c2"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:52:59+00:00",
"cve": "CVE-2026-99499",
"id": "CVE-2026-99499",
"initial_release_date": "2026-11-19T14:43:47.226000+00:00",
"product_status:known_not_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: s390/pci: denial of service via use-after-free in floating interrupt cleanup",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99499.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.