GHSA-8263-VR49-MGCG
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:31In the Linux kernel, the following vulnerability has been resolved:
media: cx23885: cancel NetUP CI work before teardown
netup_ci_exit() frees a netup_ci_state while its work item, netup_read_ci_status(), may still be pending or running on the system workqueue. The worker obtains the state with container_of() and dereferences it, so it must not outlive the state.
netup_ci_init() queues the initial status read, and CI GPIO interrupts subsequently queue the same work from netup_ci_slot_status(). During remove, cx23885_finidev() calls free_irq() before the CI device is unregistered. free_irq() prevents further IRQ handlers from running, but does not drain work queued previously, so the worker can run after netup_ci_exit() frees the state.
Call cancel_work_sync() before dvb_ca_en50221_release() and kfree().
This issue was found by an in-house static analysis tool.
{
"affected": [],
"aliases": [
"CVE-2026-89893"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:58Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: cx23885: cancel NetUP CI work before teardown\n\nnetup_ci_exit() frees a netup_ci_state while its work item,\nnetup_read_ci_status(), may still be pending or running on the system\nworkqueue. The worker obtains the state with container_of() and\ndereferences it, so it must not outlive the state.\n\nnetup_ci_init() queues the initial status read, and CI GPIO interrupts\nsubsequently queue the same work from netup_ci_slot_status(). During\nremove, cx23885_finidev() calls free_irq() before the CI device is\nunregistered. free_irq() prevents further IRQ handlers from running,\nbut does not drain work queued previously, so the worker can run after\nnetup_ci_exit() frees the state.\n\nCall cancel_work_sync() before dvb_ca_en50221_release() and kfree().\n\nThis issue was found by an in-house static analysis tool.",
"id": "GHSA-8263-vr49-mgcg",
"modified": "2026-09-16T15:31:00Z",
"published": "2026-09-16T12:30:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89893"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/140ecbcbf978fbe60f83f8d4f8b1199029a5c763"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4e143d662ca94888b494b2427fc9e34494eb933a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5deec890ecfa04d21cfa9bb9a2fe5e9dc98db5c5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/99cd62b9b1c818d6d01a87be9a8e5796314150a2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aaf76794b870b0f391eff339252a2e2e22f33a4a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bf3f49273d5bf6acbdad18ff44c01ffcf7a7a146"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ec82b0cf7f75fd95802592dcc9560fc7f529bba4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f7ff5adb63c1b277565afa54ccc0924d841b4a52"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.