GHSA-2Q2H-4P8V-3772
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
media: ipu6: Do not free aux device pdata after init
ipu6_bus_initialize_device() stores the isys/psys pdata pointer in struct ipu6_bus_device and initializes the auxiliary device. After that point, error unwinding must drop the auxiliary device reference and let ipu6_bus_release() free both the bus device and adev->pdata.
The isys and psys init paths already call put_device() when MMU initialization fails, and ipu6_bus_add_device() calls auxiliary_device_uninit() on auxiliary_device_add() failure. Both paths therefore run the bus release callback. The extra kfree(pdata) in the callers can release the same object a second time.
Remove the manual pdata frees after the auxiliary device has been initialized.
This issue was found by a static analysis checker and confirmed by manual source review.
{
"affected": [],
"aliases": [
"CVE-2026-93070"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:00Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ipu6: Do not free aux device pdata after init\n\nipu6_bus_initialize_device() stores the isys/psys pdata pointer in\nstruct ipu6_bus_device and initializes the auxiliary device. After that\npoint, error unwinding must drop the auxiliary device reference and let\nipu6_bus_release() free both the bus device and adev-\u003epdata.\n\nThe isys and psys init paths already call put_device() when MMU\ninitialization fails, and ipu6_bus_add_device() calls\nauxiliary_device_uninit() on auxiliary_device_add() failure. Both paths\ntherefore run the bus release callback. The extra kfree(pdata) in the\ncallers can release the same object a second time.\n\nRemove the manual pdata frees after the auxiliary device has been\ninitialized.\n\nThis issue was found by a static analysis checker and confirmed by\nmanual source review.",
"id": "GHSA-2q2h-4p8v-3772",
"modified": "2026-09-17T18:32:09Z",
"published": "2026-09-17T18:32:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93070"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5323ed5a7bb2568191ec676b2035b0396105aa05"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7d102d1f0631807a491a140f67c9628dea85dfd2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9be07216af4cfc4813e1a46ce26407d31ea845de"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/faa1eb97f0e66bf122f44b62be6b323f86333e9f"
}
],
"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.