GHSA-MXR7-7P5M-M8XR

Vulnerability from github – Published: 2026-05-08 15:31 – Updated: 2026-05-11 09:30
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

xprtrdma: Decrement re_receiving on the early exit paths

In the event that rpcrdma_post_recvs() fails to create a work request (due to memory allocation failure, say) or otherwise exits early, we should decrement ep->re_receiving before returning. Otherwise we will hang in rpcrdma_xprt_drain() as re_receiving will never reach zero and the completion will never be triggered.

On a system with high memory pressure, this can appear as the following hung task:

INFO: task kworker/u385:17:8393 blocked for more than 122 seconds.
      Tainted: G S          E       6.19.0 #3
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u385:17 state:D stack:0     pid:8393  tgid:8393  ppid:2      task_flags:0x4248060 flags:0x00080000
Workqueue: xprtiod xprt_autoclose [sunrpc]
Call Trace:
 <TASK>
 __schedule+0x48b/0x18b0
 ? ib_post_send_mad+0x247/0xae0 [ib_core]
 schedule+0x27/0xf0
 schedule_timeout+0x104/0x110
 __wait_for_common+0x98/0x180
 ? __pfx_schedule_timeout+0x10/0x10
 wait_for_completion+0x24/0x40
 rpcrdma_xprt_disconnect+0x444/0x460 [rpcrdma]
 xprt_rdma_close+0x12/0x40 [rpcrdma]
 xprt_autoclose+0x5f/0x120 [sunrpc]
 process_one_work+0x191/0x3e0
 worker_thread+0x2e3/0x420
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x10d/0x230
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x273/0x2b0
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-43469"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-08T15:16:59Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxprtrdma: Decrement re_receiving on the early exit paths\n\nIn the event that rpcrdma_post_recvs() fails to create a work request\n(due to memory allocation failure, say) or otherwise exits early, we\nshould decrement ep-\u003ere_receiving before returning. Otherwise we will\nhang in rpcrdma_xprt_drain() as re_receiving will never reach zero and\nthe completion will never be triggered.\n\nOn a system with high memory pressure, this can appear as the following\nhung task:\n\n    INFO: task kworker/u385:17:8393 blocked for more than 122 seconds.\n          Tainted: G S          E       6.19.0 #3\n    \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n    task:kworker/u385:17 state:D stack:0     pid:8393  tgid:8393  ppid:2      task_flags:0x4248060 flags:0x00080000\n    Workqueue: xprtiod xprt_autoclose [sunrpc]\n    Call Trace:\n     \u003cTASK\u003e\n     __schedule+0x48b/0x18b0\n     ? ib_post_send_mad+0x247/0xae0 [ib_core]\n     schedule+0x27/0xf0\n     schedule_timeout+0x104/0x110\n     __wait_for_common+0x98/0x180\n     ? __pfx_schedule_timeout+0x10/0x10\n     wait_for_completion+0x24/0x40\n     rpcrdma_xprt_disconnect+0x444/0x460 [rpcrdma]\n     xprt_rdma_close+0x12/0x40 [rpcrdma]\n     xprt_autoclose+0x5f/0x120 [sunrpc]\n     process_one_work+0x191/0x3e0\n     worker_thread+0x2e3/0x420\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x10d/0x230\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x273/0x2b0\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30",
  "id": "GHSA-mxr7-7p5m-m8xr",
  "modified": "2026-05-11T09:30:32Z",
  "published": "2026-05-08T15:31:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43469"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/49f53ee4e25297d886f14e31f355ad1c2735ddfb"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/74c39a47856bddcde7874f2196a00143b5cd0af9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7b6275c80a0c81c5f8943272292dfe67730ce849"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7ea69259a60a364f56cf4aa9e2eafb588d1c762b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8127b5fec04757c2a41ed65bca0b3266968efd3b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8cb6b5d8296b1f99a8d36849901ebabfe3f749db"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dc3ebd7e2d73dbd4d317785735ffa6c4a6384ddf"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.