GHSA-QH4F-62FC-9QXV
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-10-30 15:33In the Linux kernel, the following vulnerability has been resolved:
HID: sony: clean up device list on probe failure
sony_input_configured() adds some controllers to sony_device_list before HID core registers their input devices. input_register_device() can fail after the callback returns successfully. sony_probe() then observes that HID_CLAIMED_INPUT is clear and unwinds, but only stops the HID hardware. The devres-managed sony_sc is freed while its list node remains linked, so the next matching controller traverses freed memory.
Initialize the list node and device ID to inactive states. Make list removal idempotent and run the driver-private cleanup on every probe failure path. This also makes a second cleanup safe when sony_input_configured() already unwound a partial initialization before sony_probe() handles the missing input claim.
Found by 0sec (https://0sec.ai) using automated source analysis; verified against the HID input registration and probe unwind paths.
{
"affected": [],
"aliases": [
"CVE-2026-90041"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:17:17Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: sony: clean up device list on probe failure\n\nsony_input_configured() adds some controllers to sony_device_list before\nHID core registers their input devices. input_register_device() can fail\nafter the callback returns successfully. sony_probe() then observes that\nHID_CLAIMED_INPUT is clear and unwinds, but only stops the HID hardware.\nThe devres-managed sony_sc is freed while its list node remains linked, so\nthe next matching controller traverses freed memory.\n\nInitialize the list node and device ID to inactive states. Make list\nremoval idempotent and run the driver-private cleanup on every probe\nfailure path. This also makes a second cleanup safe when\nsony_input_configured() already unwound a partial initialization before\nsony_probe() handles the missing input claim.\n\nFound by 0sec (https://0sec.ai) using automated source analysis;\nverified against the HID input registration and probe unwind paths.",
"id": "GHSA-qh4f-62fc-9qxv",
"modified": "2026-10-30T15:33:30Z",
"published": "2026-09-16T12:30:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90041"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3b4709e4864908bb06c48c500cc8db8d3d55d139"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/41d92c2e02788c04663b11335454b094dc4672bc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7c65699a3a311198a07659a614fe64d45924839e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7ee50d42a6d5c8cf3d8afb3285273bcc58452214"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b84544ef00a27e8081498d33af7dac33b6cb8418"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d044d796e2a369c6051c7e83dce88c7baa2494d4"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.