GHSA-X4C4-QFR2-C3VV
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-14 15:32In the Linux kernel, the following vulnerability has been resolved:
Revert "media: v4l2-dev: fix error handling in __video_register_device()"
This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.
The intentions of that patch were good, but it doesn't work.
The idea is that if device_register fails, you have to do a put_device to let the ref counter release resources.
However, the V4L2 API says that if video_register_device() fails, then you have to call video_device_release(), which kfree()s the video_device struct.
But the put_device() will already have freed the struct, so you end up in a double-free scenario.
There is not really a good way of fixing this without breaking video_register_device() into two parts, one that initializes everything, and one that does the actual device_register, and then converting all V4L2 drivers to this new model.
That is a massive job, and it is very unlikely that device_register will fail.
So rather than ending up in a double-free scenario, just revert this patch, and in that case we'll have a small memory leak. Which is a lot more robust.
{
"affected": [],
"aliases": [
"CVE-2026-89741"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:20:04Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"media: v4l2-dev: fix error handling in __video_register_device()\"\n\nThis reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.\n\nThe intentions of that patch were good, but it doesn\u0027t work.\n\nThe idea is that if device_register fails, you have to do a put_device\nto let the ref counter release resources.\n\nHowever, the V4L2 API says that if video_register_device() fails, then\nyou have to call video_device_release(), which kfree()s the video_device\nstruct.\n\nBut the put_device() will already have freed the struct, so you end\nup in a double-free scenario.\n\nThere is not really a good way of fixing this without breaking\nvideo_register_device() into two parts, one that initializes everything,\nand one that does the actual device_register, and then converting all\nV4L2 drivers to this new model.\n\nThat is a massive job, and it is very unlikely that device_register\nwill fail.\n\nSo rather than ending up in a double-free scenario, just revert this\npatch, and in that case we\u0027ll have a small memory leak. Which is a lot\nmore robust.",
"id": "GHSA-x4c4-qfr2-c3vv",
"modified": "2026-09-14T15:32:36Z",
"published": "2026-09-11T21:31:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89741"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2ac009a65d2385e9f0799eaf9d9694a29153a161"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3de14b4f681a1b3c6d375d98d9d37a55ebb85349"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/712ca1cf756de2557a116e0df55791bac0c9f99e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8027f82c0f5474ed72448e160ee9778051fa1f49"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8b998c171ed875e402e1fd1c5cd619e4ca05e9c1"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aad08b5f67d2a8116e1a00bce2611c1513b10bce"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ce792b94e03882108019ba996c1a7c4d4e09be2c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e7600f5cee5de14065f950807931d6e6d40fb2d7"
}
],
"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"
}
]
}
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.