# CVE-2024-39292: um: Add winch to winch_handlers before registering winch IRQ

> A race condition in the Linux kernel UML subsystem can cause a system panic when a winch IRQ is registered before the handler is added to the list.

- **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:** 24 Jun 2024
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-42889, AZL-42937, BELL-CVE-2024-39292, DEBIAN-CVE-2024-39292, GHSA-9338-v6x4-3wv5, UBUNTU-CVE-2024-39292

## What is CVE-2024-39292?

CVE-2024-39292 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2024. 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:

um: Add winch to winch_handlers before registering winch IRQ

Registering a winch IRQ is racy, an interrupt may occur before the winch is
added to the winch_handlers list.

If that happens, register_winch_irq() adds to that list a winch that is
scheduled to be (or has already been) freed, causing a panic later in
winch_cleanup().

Avoid the race by adding the winch to the winch_handlers list before
registering the IRQ, and rolling back if um_request_irq() fails.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2024-39292?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-39292?

Apply the vendor's patch.

## Is CVE-2024-39292 being exploited?

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

What it is: CVE-2024-39292 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2024. 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-2024-39292 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-2024-39292/ (Markdown: https://insights.sbomify.com/CVE-2024-39292/index.md)
```

## Sources

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

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