# CVE-2025-71073: Input: lkkbd - disable pending work before freeing device

> A use-after-free vulnerability in the Linux kernel lkkbd driver allows attackers to execute arbitrary code or escalate privileges via race conditions during device disconnection.

- **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:** 13 Jan 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-74354, BELL-CVE-2025-71073, DEBIAN-CVE-2025-71073, GHSA-fh34-wp9w-rw28, ROOT-OS-DEBIAN-11-CVE-2025-71073, ROOT-OS-DEBIAN-12-CVE-2025-71073, ROOT-OS-DEBIAN-13-CVE-2025-71073, ROOT-OS-UBUNTU-2204-CVE-2025-71073, ROOT-OS-UBUNTU-2404-CVE-2025-71073, UBUNTU-CVE-2025-71073

## What is CVE-2025-71073?

CVE-2025-71073 is a high-severity use after free vulnerability in Linux kernel, published on 13 Jan 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:

Input: lkkbd - disable pending work before freeing device

lkkbd_interrupt() schedules lk->tq via schedule_work(), and the work
handler lkkbd_reinit() dereferences the lkkbd structure and its
serio/input_dev fields.

lkkbd_disconnect() and error paths in lkkbd_connect() free the lkkbd
structure without preventing the reinit work from being queued again
until serio_close() returns. This can allow the work handler to run
after the structure has been freed, leading to a potential use-after-free.

Use disable_work_sync() instead of cancel_work_sync() to ensure the
reinit work cannot be re-queued, and call it both in lkkbd_disconnect()
and in lkkbd_connect() error paths after serio_open().

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-71073?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-71073?

Apply the vendor's patch.

## Is CVE-2025-71073 being exploited?

There is no known exploitation of CVE-2025-71073 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-2025-71073 and fix it if it is affected.

What it is: CVE-2025-71073 is a high-severity use after free vulnerability in Linux kernel, published on 13 Jan 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-2025-71073 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-2025-71073/ (Markdown: https://insights.sbomify.com/CVE-2025-71073/index.md)
```

## Sources

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

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