# CVE-2026-90041: HID: sony: clean up device list on probe failure

> A use-after-free vulnerability in the Linux kernel's Sony HID driver allows attackers to cause memory corruption or system crashes via specific device probe failures.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-101606, BELL-CVE-2026-90041, DEBIAN-CVE-2026-90041, GHSA-qh4f-62fc-9qxv, UBUNTU-CVE-2026-90041

## What is CVE-2026-90041?

CVE-2026-90041 is a high-severity use after free vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In 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.

## Which versions are affected by CVE-2026-90041?


## How do I fix CVE-2026-90041?

Apply the vendor's patch.

## Is CVE-2026-90041 being exploited?

There is no known exploitation of CVE-2026-90041 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90041 and fix it if it is affected.

What it is: CVE-2026-90041 is a high-severity use after free vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90041 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90041/ (Markdown: https://insights.sbomify.com/CVE-2026-90041/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90041
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90041
- OSV: https://osv.dev/vulnerability/CVE-2026-90041

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90041/
Summaries are generated and may contain mistakes; the official description above is the record.