GHSA-RMQV-GXQC-VFX4
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In the Linux kernel, the following vulnerability has been resolved:
media: v4l2-async: avoid deleting unlinked ASC entry on link error
v4l2_async_match_notify() creates ancillary media links before adding asc->asc_subdev_entry to sd->asc_list.
If ancillary link creation fails, the function jumps to err_call_unbind while asc_subdev_entry has not been linked yet. Async connections are zero-allocated, so the list entry still has NULL next and prev pointers on this path. Calling list_del() on it can therefore dereference NULL instead of returning the original link creation error.
Do not delete asc_subdev_entry from err_call_unbind. There is no list insertion to undo on this path; the bound callback and sub-device registration are the operations that need to be rolled back.
{
"affected": [],
"aliases": [
"CVE-2026-89874"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:55Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l2-async: avoid deleting unlinked ASC entry on link error\n\nv4l2_async_match_notify() creates ancillary media links before adding\nasc-\u003easc_subdev_entry to sd-\u003easc_list.\n\nIf ancillary link creation fails, the function jumps to\nerr_call_unbind while asc_subdev_entry has not been linked yet. Async\nconnections are zero-allocated, so the list entry still has NULL next\nand prev pointers on this path. Calling list_del() on it can therefore\ndereference NULL instead of returning the original link creation error.\n\nDo not delete asc_subdev_entry from err_call_unbind. There is no list\ninsertion to undo on this path; the bound callback and sub-device\nregistration are the operations that need to be rolled back.",
"id": "GHSA-rmqv-gxqc-vfx4",
"modified": "2026-09-16T12:30:39Z",
"published": "2026-09-16T12:30:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89874"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3345746e0957bce6c53644838e4955710a82a962"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/47d82b605351c0e04f6365e42c8ffe2fcfdba615"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a57d94026cb4fd7b3d258f0db2ad391cbccfaba5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/caac13f518d83974e9884d1eeda3d4cc3bb92978"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d273571e531405426983c6a45ec635c7d0415eed"
}
],
"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.