GHSA-W3G9-F95X-PWMF
Vulnerability from github – Published: 2025-12-24 15:30 – Updated: 2025-12-24 15:30In the Linux kernel, the following vulnerability has been resolved:
media: mtk-jpeg: Fix use after free bug due to uncanceled work
In mtk_jpeg_probe, &jpeg->job_timeout_work is bound with mtk_jpeg_job_timeout_work. Then mtk_jpeg_dec_device_run and mtk_jpeg_enc_device_run may be called to start the work. If we remove the module which will call mtk_jpeg_remove to make cleanup, there may be a unfinished work. The possible sequence is as follows, which will cause a typical UAF bug.
Fix it by canceling the work before cleanup in the mtk_jpeg_remove
CPU0 CPU1
|mtk_jpeg_job_timeout_work
mtk_jpeg_remove | v4l2_m2m_release | kfree(m2m_dev); | | | v4l2_m2m_get_curr_priv | m2m_dev->curr_ctx //use
{
"affected": [],
"aliases": [
"CVE-2023-54103"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-24T13:16:12Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: mtk-jpeg: Fix use after free bug due to uncanceled work\n\nIn mtk_jpeg_probe, \u0026jpeg-\u003ejob_timeout_work is bound with\nmtk_jpeg_job_timeout_work. Then mtk_jpeg_dec_device_run\nand mtk_jpeg_enc_device_run may be called to start the\nwork.\nIf we remove the module which will call mtk_jpeg_remove\nto make cleanup, there may be a unfinished work. The\npossible sequence is as follows, which will cause a\ntypical UAF bug.\n\nFix it by canceling the work before cleanup in the mtk_jpeg_remove\n\nCPU0 CPU1\n\n |mtk_jpeg_job_timeout_work\nmtk_jpeg_remove |\n v4l2_m2m_release |\n kfree(m2m_dev); |\n |\n | v4l2_m2m_get_curr_priv\n | m2m_dev-\u003ecurr_ctx //use",
"id": "GHSA-w3g9-f95x-pwmf",
"modified": "2025-12-24T15:30:38Z",
"published": "2025-12-24T15:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54103"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2fc20f8bcc2b4d31c808a5320506c31aa2cf3834"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/715c0200b4809396998e562ce5cd0284e7314cc1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8977d9924843823f46696d7d9432ea4b2499ed14"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c677d7ae83141d390d1253abebafa49c962afb52"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d346a2ef6b1ebb77d740890cfaf8478c5b286380"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d56dbfe750a8f96789cc86a911864f663e63bc5d"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.