CVE-2026-99468 (GCVE-0-2026-99468)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:42 – Updated: 2026-11-19 14:42| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
cfed9632ca8e8bdf0128745ae2400b72c4292886 , < 77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341
(git)
Affected: cfed9632ca8e8bdf0128745ae2400b72c4292886 , < 49a0623994a10d3d333d48c304f89d816495f332 (git) Affected: cfed9632ca8e8bdf0128745ae2400b72c4292886 , < 9e393784a902bb4eb00a21e46d389a32c7ea61b0 (git) Affected: cfed9632ca8e8bdf0128745ae2400b72c4292886 , < 78fdfbf117c409273eecbfa7a528ef42358a0e38 (git) Affected: 1f3367fa4210f37417cd55622b3872ababd2f06d (git) Affected: 6.1.143 , < 6.2 (semver) |
guessed | |
| Linux | Linux |
Affected:
6.2
Unaffected: 0 , < 6.2 (semver) Unaffected: 6.12.117 , ≤ 6.12.* (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/media/platform/nxp/imx-jpeg/mxc-jpeg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"lessThan": "49a0623994a10d3d333d48c304f89d816495f332",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"lessThan": "9e393784a902bb4eb00a21e46d389a32c7ea61b0",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"lessThan": "78fdfbf117c409273eecbfa7a528ef42358a0e38",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"status": "affected",
"version": "1f3367fa4210f37417cd55622b3872ababd2f06d",
"versionType": "git"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.143",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.2"
},
{
"lessThan": "6.2",
"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"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.117",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.1.143",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imx-jpeg: cancel timeout worker when streaming stops\n\nEach per-fd context ctx owns a delayed_work (ctx-\u003etask_timer, callback\nmxc_jpeg_device_run_timeout) armed via schedule_delayed_work() at the end\nof mxc_jpeg_device_run() to recover a stalled encode/decode job. The only\nexisting cancellation is cancel_delayed_work() in the frame-done IRQ\nhandler, which de-queues a pending work item but does not wait for a\ncallback that has already started, and it only runs when a frame completes.\n\nWhen the fd is closed while a job is in flight (the frame-done IRQ has not\nfired yet), nothing syncs the worker before mxc_jpeg_release() frees ctx\nwith kfree() after v4l2_m2m_ctx_release(). A queued or executing\nmxc_jpeg_device_run_timeout() can then recover ctx through\ncontainer_of(\u0026ctx-\u003etask_timer) and dereference it (ctx-\u003emxc_jpeg,\nslot_data, dev_warn) after ctx has been freed.\n\nCancel the worker from mxc_jpeg_stop_streaming(). The cancel cannot live\nin mxc_jpeg_release(): mxc_jpeg_device_run() arms the timer while holding\nonly hw_lock, not the mxc_jpeg-\u003elock mutex that release holds, so a cancel\nin release could still race a concurrent mxc_jpeg_device_run() that\nre-arms the timer afterwards. mxc_jpeg_stop_streaming() instead runs inside\nv4l2_m2m_ctx_release() -\u003e vb2_queue_release(), i.e. after\nv4l2_m2m_cancel_job() has set TRANS_ABORT and waited for any in-flight job\nto finish (so __v4l2_m2m_try_queue() will not queue and v4l2_m2m_try_run()\nwill not run any further job for this context, which prevents\nmxc_jpeg_device_run() from re-arming the timer) and before the m2m context\nis freed. cancel_delayed_work_sync() removes a pending work item and waits\nfor a running callback, so the worker can no longer race with the\nsubsequent kfree(). The cancel is placed before the buffer-release loop so\na concurrently running timeout callback cannot race with it over the same\nbuffers. If the frame-done IRQ canceled a still-pending timer, this cancel\nis a no-op; if the timeout callback has already started, it waits for the\ncallback to finish. The same mxc_jpeg_stop_streaming() call is also\nreached from VIDIOC_STREAMOFF, which drains the worker early, although\nSTREAMOFF itself does not free ctx -- the use-after-free arises only\nwhen the fd is later closed.\n\nThis bug was found by static analysis."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:42:54.426Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341"
},
{
"url": "https://git.kernel.org/stable/c/49a0623994a10d3d333d48c304f89d816495f332"
},
{
"url": "https://git.kernel.org/stable/c/9e393784a902bb4eb00a21e46d389a32c7ea61b0"
},
{
"url": "https://git.kernel.org/stable/c/78fdfbf117c409273eecbfa7a528ef42358a0e38"
}
],
"title": "media: imx-jpeg: cancel timeout worker when streaming stops",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99468",
"datePublished": "2026-11-19T14:42:54.426Z",
"dateReserved": "2026-09-25T10:25:14.417Z",
"dateUpdated": "2026-11-19T14:42:54.426Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"lessThan": "49a0623994a10d3d333d48c304f89d816495f332",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"lessThan": "9e393784a902bb4eb00a21e46d389a32c7ea61b0",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"lessThan": "78fdfbf117c409273eecbfa7a528ef42358a0e38",
"status": "affected",
"version": "cfed9632ca8e8bdf0128745ae2400b72c4292886",
"versionType": "git"
},
{
"status": "affected",
"version": "1f3367fa4210f37417cd55622b3872ababd2f06d",
"versionType": "git"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.143",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.2"
},
{
"lessThan": "6.2",
"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\nmedia: imx-jpeg: cancel timeout worker when streaming stops\n\nEach per-fd context ctx owns a delayed_work (ctx-\u003etask_timer, callback\nmxc_jpeg_device_run_timeout) armed via schedule_delayed_work() at the end\nof mxc_jpeg_device_run() to recover a stalled encode/decode job. The only\nexisting cancellation is cancel_delayed_work() in the frame-done IRQ\nhandler, which de-queues a pending work item but does not wait for a\ncallback that has already started, and it only runs when a frame completes.\n\nWhen the fd is closed while a job is in flight (the frame-done IRQ has not\nfired yet), nothing syncs the worker before mxc_jpeg_release() frees ctx\nwith kfree() after v4l2_m2m_ctx_release(). A queued or executing\nmxc_jpeg_device_run_timeout() can then recover ctx through\ncontainer_of(\u0026ctx-\u003etask_timer) and dereference it (ctx-\u003emxc_jpeg,\nslot_data, dev_warn) after ctx has been freed.\n\nCancel the worker from mxc_jpeg_stop_streaming(). The cancel cannot live\nin mxc_jpeg_release(): mxc_jpeg_device_run() arms the timer while holding\nonly hw_lock, not the mxc_jpeg-\u003elock mutex that release holds, so a cancel\nin release could still race a concurrent mxc_jpeg_device_run() that\nre-arms the timer afterwards. mxc_jpeg_stop_streaming() instead runs inside\nv4l2_m2m_ctx_release() -\u003e vb2_queue_release(), i.e. after\nv4l2_m2m_cancel_job() has set TRANS_ABORT and waited for any in-flight job\nto finish (so __v4l2_m2m_try_queue() will not queue and v4l2_m2m_try_run()\nwill not run any further job for this context, which prevents\nmxc_jpeg_device_run() from re-arming the timer) and before the m2m context\nis freed. cancel_delayed_work_sync() removes a pending work item and waits\nfor a running callback, so the worker can no longer race with the\nsubsequent kfree(). The cancel is placed before the buffer-release loop so\na concurrently running timeout callback cannot race with it over the same\nbuffers. If the frame-done IRQ canceled a still-pending timer, this cancel\nis a no-op; if the timeout callback has already started, it waits for the\ncallback to finish. The same mxc_jpeg_stop_streaming() call is also\nreached from VIDIOC_STREAMOFF, which drains the worker early, although\nSTREAMOFF itself does not free ctx -- the use-after-free arises only\nwhen the fd is later closed.\n\nThis bug was found by static analysis."
}
],
"id": "CVE-2026-99468",
"lastModified": "2026-11-19T15:18:01.110",
"metrics": {},
"published": "2026-11-19T15:18:01.110",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/49a0623994a10d3d333d48c304f89d816495f332"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/78fdfbf117c409273eecbfa7a528ef42358a0e38"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9e393784a902bb4eb00a21e46d389a32c7ea61b0"
}
],
"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.