# CVE-2026-43049: HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure

> A use-after-free vulnerability in the Linux kernel Logitech HID driver allows local attackers to execute code or escalate privileges via a specific device initialization failure.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 May 2026
- **Updated:** 21 Oct 2026
- **Also known as:** A-482992246, ASB-A-482992246, AZL-85371, BELL-CVE-2026-43049, DEBIAN-CVE-2026-43049, GHSA-249v-wmcw-xvgm, ROOT-OS-DEBIAN-11-CVE-2026-43049, ROOT-OS-DEBIAN-12-CVE-2026-43049, ROOT-OS-UBUNTU-2204-CVE-2026-43049, ROOT-OS-UBUNTU-2404-CVE-2026-43049, UBUNTU-CVE-2026-43049

## What is CVE-2026-43049?

CVE-2026-43049 is a high-severity use after free vulnerability in Linux kernel, published on 1 May 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: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure

Presently, if the force feedback initialisation fails when probing the
Logitech G920 Driving Force Racing Wheel for Xbox One, an error number
will be returned and propagated before the userspace infrastructure
(sysfs and /dev/input) has been torn down.  If userspace ignores the
errors and continues to use its references to these dangling entities, a
UAF will promptly follow.

We have 2 options; continue to return the error, but ensure that all of
the infrastructure is torn down accordingly or continue to treat this
condition as a warning by emitting the message but returning success.
It is thought that the original author's intention was to emit the
warning but keep the device functional, less the force feedback feature,
so let's go with that.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-43049 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-43049 is a high-severity use after free vulnerability in Linux kernel, published on 1 May 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-43049 in the wild and no public exploit code.

Affected product: Linux kernel. 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-43049/ (Markdown: https://insights.sbomify.com/CVE-2026-43049/index.md)
```

## Sources

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

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