CVE-2022-48721 (GCVE-0-2022-48721)
Vulnerability from cvelistv5
Published
2024-06-20 11:13
Modified
2026-08-05 08:51
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: net/smc: Forward wakeup to smc socket waitqueue after fallback When we replace TCP with SMC and a fallback occurs, there may be some socket waitqueue entries remaining in smc socket->wq, such as eppoll_entries inserted by userspace applications. After the fallback, data flows over TCP/IP and only clcsocket->wq will be woken up. Applications can't be notified by the entries which were inserted in smc socket->wq before fallback. So we need a mechanism to wake up smc socket->wq at the same time if some entries remaining in it. The current workaround is to transfer the entries from smc socket->wq to clcsock->wq during the fallback. But this may cause a crash like this: general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E 5.16.0+ #107 RIP: 0010:__wake_up_common+0x65/0x170 Call Trace: <IRQ> __wake_up_common_lock+0x7a/0xc0 sock_def_readable+0x3c/0x70 tcp_data_queue+0x4a7/0xc40 tcp_rcv_established+0x32f/0x660 ? sk_filter_trim_cap+0xcb/0x2e0 tcp_v4_do_rcv+0x10b/0x260 tcp_v4_rcv+0xd2a/0xde0 ip_protocol_deliver_rcu+0x3b/0x1d0 ip_local_deliver_finish+0x54/0x60 ip_local_deliver+0x6a/0x110 ? tcp_v4_early_demux+0xa2/0x140 ? tcp_v4_early_demux+0x10d/0x140 ip_sublist_rcv_finish+0x49/0x60 ip_sublist_rcv+0x19d/0x230 ip_list_rcv+0x13e/0x170 __netif_receive_skb_list_core+0x1c2/0x240 netif_receive_skb_list_internal+0x1e6/0x320 napi_complete_done+0x11d/0x190 mlx5e_napi_poll+0x163/0x6b0 [mlx5_core] __napi_poll+0x3c/0x1b0 net_rx_action+0x27c/0x300 __do_softirq+0x114/0x2d2 irq_exit_rcu+0xb4/0xe0 common_interrupt+0xba/0xe0 </IRQ> <TASK> The crash is caused by privately transferring waitqueue entries from smc socket->wq to clcsock->wq. The owners of these entries, such as epoll, have no idea that the entries have been transferred to a different socket wait queue and still use original waitqueue spinlock (smc socket->wq.wait.lock) to make the entries operation exclusive, but it doesn't work. The operations to the entries, such as removing from the waitqueue (now is clcsock->wq after fallback), may cause a crash when clcsock waitqueue is being iterated over at the moment. This patch tries to fix this by no longer transferring wait queue entries privately, but introducing own implementations of clcsock's callback functions in fallback situation. The callback functions will forward the wakeup to smc socket->wq if clcsock->wq is actually woken up and smc socket->wq has remaining entries.
References
Impacted products
Vendor Product Version
Linux Linux Version: fb92e025baa73e99250b79ab64f4e088d2888993
Version: 2153bd1e3d3dbf6a3403572084ef6ed31c53c5f0
Version: 2153bd1e3d3dbf6a3403572084ef6ed31c53c5f0
Version: d6e981ec9491be5ec46d838b1151e7edefe607f5
Version: ff6eeb627898c179aac421af5d6515d3f50b84df
Version: 5.15.7   ≤
Version: 5.4.164   ≤
Version: 5.10.84   ≤
Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T15:25:00.192Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/0ef6049f664941bc0f75828b3a61877635048b27"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/504078fbe9dd570d685361b57784a6050bc40aaa"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/341adeec9adad0874f29a0a1af35638207352a39"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2022-48721",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-10T17:11:16.258278Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-11T17:34:49.624Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/smc/af_smc.c",
            "net/smc/smc.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "0ef6049f664941bc0f75828b3a61877635048b27",
              "status": "affected",
              "version": "fb92e025baa73e99250b79ab64f4e088d2888993",
              "versionType": "git"
            },
            {
              "lessThan": "504078fbe9dd570d685361b57784a6050bc40aaa",
              "status": "affected",
              "version": "2153bd1e3d3dbf6a3403572084ef6ed31c53c5f0",
              "versionType": "git"
            },
            {
              "lessThan": "341adeec9adad0874f29a0a1af35638207352a39",
              "status": "affected",
              "version": "2153bd1e3d3dbf6a3403572084ef6ed31c53c5f0",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "d6e981ec9491be5ec46d838b1151e7edefe607f5",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "ff6eeb627898c179aac421af5d6515d3f50b84df",
              "versionType": "git"
            },
            {
              "lessThan": "5.15.22",
              "status": "affected",
              "version": "5.15.7",
              "versionType": "semver"
            },
            {
              "lessThan": "5.5",
              "status": "affected",
              "version": "5.4.164",
              "versionType": "semver"
            },
            {
              "lessThan": "5.11",
              "status": "affected",
              "version": "5.10.84",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/smc/af_smc.c",
            "net/smc/smc.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.16"
            },
            {
              "lessThan": "5.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.22",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.16.*",
              "status": "unaffected",
              "version": "5.16.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "5.17",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.22",
                  "versionStartIncluding": "5.15.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.16.8",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.17",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.4.164",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.10.84",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: Forward wakeup to smc socket waitqueue after fallback\n\nWhen we replace TCP with SMC and a fallback occurs, there may be\nsome socket waitqueue entries remaining in smc socket-\u003ewq, such\nas eppoll_entries inserted by userspace applications.\n\nAfter the fallback, data flows over TCP/IP and only clcsocket-\u003ewq\nwill be woken up. Applications can\u0027t be notified by the entries\nwhich were inserted in smc socket-\u003ewq before fallback. So we need\na mechanism to wake up smc socket-\u003ewq at the same time if some\nentries remaining in it.\n\nThe current workaround is to transfer the entries from smc socket-\u003ewq\nto clcsock-\u003ewq during the fallback. But this may cause a crash\nlike this:\n\n general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI\n CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E     5.16.0+ #107\n RIP: 0010:__wake_up_common+0x65/0x170\n Call Trace:\n  \u003cIRQ\u003e\n  __wake_up_common_lock+0x7a/0xc0\n  sock_def_readable+0x3c/0x70\n  tcp_data_queue+0x4a7/0xc40\n  tcp_rcv_established+0x32f/0x660\n  ? sk_filter_trim_cap+0xcb/0x2e0\n  tcp_v4_do_rcv+0x10b/0x260\n  tcp_v4_rcv+0xd2a/0xde0\n  ip_protocol_deliver_rcu+0x3b/0x1d0\n  ip_local_deliver_finish+0x54/0x60\n  ip_local_deliver+0x6a/0x110\n  ? tcp_v4_early_demux+0xa2/0x140\n  ? tcp_v4_early_demux+0x10d/0x140\n  ip_sublist_rcv_finish+0x49/0x60\n  ip_sublist_rcv+0x19d/0x230\n  ip_list_rcv+0x13e/0x170\n  __netif_receive_skb_list_core+0x1c2/0x240\n  netif_receive_skb_list_internal+0x1e6/0x320\n  napi_complete_done+0x11d/0x190\n  mlx5e_napi_poll+0x163/0x6b0 [mlx5_core]\n  __napi_poll+0x3c/0x1b0\n  net_rx_action+0x27c/0x300\n  __do_softirq+0x114/0x2d2\n  irq_exit_rcu+0xb4/0xe0\n  common_interrupt+0xba/0xe0\n  \u003c/IRQ\u003e\n  \u003cTASK\u003e\n\nThe crash is caused by privately transferring waitqueue entries from\nsmc socket-\u003ewq to clcsock-\u003ewq. The owners of these entries, such as\nepoll, have no idea that the entries have been transferred to a\ndifferent socket wait queue and still use original waitqueue spinlock\n(smc socket-\u003ewq.wait.lock) to make the entries operation exclusive,\nbut it doesn\u0027t work. The operations to the entries, such as removing\nfrom the waitqueue (now is clcsock-\u003ewq after fallback), may cause a\ncrash when clcsock waitqueue is being iterated over at the moment.\n\nThis patch tries to fix this by no longer transferring wait queue\nentries privately, but introducing own implementations of clcsock\u0027s\ncallback functions in fallback situation. The callback functions will\nforward the wakeup to smc socket-\u003ewq if clcsock-\u003ewq is actually woken\nup and smc socket-\u003ewq has remaining entries."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Exploitation requires a local process to create an AF_SMC (or TCP_ULP smc) socket, attach epoll waiters, and trigger SMC\u2192TCP fallback; remote packets alone cannot set up the vulnerable waitqueue transfer.\nAC:L - The attacker controls both sides of the race\u2014epoll_ctl/close removing waiters while send/recv or loopback traffic wakes the clcsock waitqueue\u2014so the lock-mismatch corruption can be triggered reliably.\nPR:L - AF_SMC SOCK_STREAM sockets can be created by an unprivileged user with no capability checks, and fallback occurs automatically when connecting to a non-SMC TCP peer (or via unsupported options like TCP_FASTOPEN).\nUI:N - No victim action is required; the attacker fully drives socket creation, epoll registration, connect/fallback, and the racing wake/remove operations.\nS:U - Impact is confined to the local kernel/OS authority (crash or privilege escalation within the same host); it does not cross VM, IOMMU, or other security boundaries.\nC:H - Concurrent unlock-protected list_del of epoll wait entries while softirq walks the spliced waitqueue is a use-after-free of wait_queue_entry/eppoll_entry memory, which can be reused to obtain arbitrary kernel read primitives.\nI:H - The same UAF targets wait_queue_entry objects that contain a callable func pointer invoked from __wake_up_common in softirq context, enabling heap reuse for control-flow hijacking and arbitrary write/code execution.\nA:H - The bug demonstrably causes a kernel general protection fault (LIST_POISON in __wake_up_common during TCP receive softirq), producing a full kernel oops/DoS."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T08:51:56.989Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/0ef6049f664941bc0f75828b3a61877635048b27"
        },
        {
          "url": "https://git.kernel.org/stable/c/504078fbe9dd570d685361b57784a6050bc40aaa"
        },
        {
          "url": "https://git.kernel.org/stable/c/341adeec9adad0874f29a0a1af35638207352a39"
        }
      ],
      "title": "net/smc: Forward wakeup to smc socket waitqueue after fallback",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-48721",
    "datePublished": "2024-06-20T11:13:12.668Z",
    "dateReserved": "2024-06-20T11:09:39.051Z",
    "dateUpdated": "2026-08-05T08:51:56.989Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/0ef6049f664941bc0f75828b3a61877635048b27\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/504078fbe9dd570d685361b57784a6050bc40aaa\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/341adeec9adad0874f29a0a1af35638207352a39\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-03T15:25:00.192Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-48721\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-10T17:11:16.258278Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-11T12:42:26.184Z\"}}], \"cna\": {\"title\": \"net/smc: Forward wakeup to smc socket waitqueue after fallback\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.8, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - Exploitation requires a local process to create an AF_SMC (or TCP_ULP smc) socket, attach epoll waiters, and trigger SMC\\u2192TCP fallback; remote packets alone cannot set up the vulnerable waitqueue transfer.\\nAC:L - The attacker controls both sides of the race\\u2014epoll_ctl/close removing waiters while send/recv or loopback traffic wakes the clcsock waitqueue\\u2014so the lock-mismatch corruption can be triggered reliably.\\nPR:L - AF_SMC SOCK_STREAM sockets can be created by an unprivileged user with no capability checks, and fallback occurs automatically when connecting to a non-SMC TCP peer (or via unsupported options like TCP_FASTOPEN).\\nUI:N - No victim action is required; the attacker fully drives socket creation, epoll registration, connect/fallback, and the racing wake/remove operations.\\nS:U - Impact is confined to the local kernel/OS authority (crash or privilege escalation within the same host); it does not cross VM, IOMMU, or other security boundaries.\\nC:H - Concurrent unlock-protected list_del of epoll wait entries while softirq walks the spliced waitqueue is a use-after-free of wait_queue_entry/eppoll_entry memory, which can be reused to obtain arbitrary kernel read primitives.\\nI:H - The same UAF targets wait_queue_entry objects that contain a callable func pointer invoked from __wake_up_common in softirq context, enabling heap reuse for control-flow hijacking and arbitrary write/code execution.\\nA:H - The bug demonstrably causes a kernel general protection fault (LIST_POISON in __wake_up_common during TCP receive softirq), producing a full kernel oops/DoS.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"fb92e025baa73e99250b79ab64f4e088d2888993\", \"lessThan\": \"0ef6049f664941bc0f75828b3a61877635048b27\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"2153bd1e3d3dbf6a3403572084ef6ed31c53c5f0\", \"lessThan\": \"504078fbe9dd570d685361b57784a6050bc40aaa\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"2153bd1e3d3dbf6a3403572084ef6ed31c53c5f0\", \"lessThan\": \"341adeec9adad0874f29a0a1af35638207352a39\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"d6e981ec9491be5ec46d838b1151e7edefe607f5\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ff6eeb627898c179aac421af5d6515d3f50b84df\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"5.15.7\", \"lessThan\": \"5.15.22\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"5.4.164\", \"lessThan\": \"5.5\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"5.10.84\", \"lessThan\": \"5.11\", \"versionType\": \"semver\"}], \"programFiles\": [\"net/smc/af_smc.c\", \"net/smc/smc.h\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.16\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.16\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.22\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"5.16.8\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.16.*\"}, {\"status\": \"unaffected\", \"version\": \"5.17\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"net/smc/af_smc.c\", \"net/smc/smc.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/0ef6049f664941bc0f75828b3a61877635048b27\"}, {\"url\": \"https://git.kernel.org/stable/c/504078fbe9dd570d685361b57784a6050bc40aaa\"}, {\"url\": \"https://git.kernel.org/stable/c/341adeec9adad0874f29a0a1af35638207352a39\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/smc: Forward wakeup to smc socket waitqueue after fallback\\n\\nWhen we replace TCP with SMC and a fallback occurs, there may be\\nsome socket waitqueue entries remaining in smc socket-\u003ewq, such\\nas eppoll_entries inserted by userspace applications.\\n\\nAfter the fallback, data flows over TCP/IP and only clcsocket-\u003ewq\\nwill be woken up. Applications can\u0027t be notified by the entries\\nwhich were inserted in smc socket-\u003ewq before fallback. So we need\\na mechanism to wake up smc socket-\u003ewq at the same time if some\\nentries remaining in it.\\n\\nThe current workaround is to transfer the entries from smc socket-\u003ewq\\nto clcsock-\u003ewq during the fallback. But this may cause a crash\\nlike this:\\n\\n general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI\\n CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E     5.16.0+ #107\\n RIP: 0010:__wake_up_common+0x65/0x170\\n Call Trace:\\n  \u003cIRQ\u003e\\n  __wake_up_common_lock+0x7a/0xc0\\n  sock_def_readable+0x3c/0x70\\n  tcp_data_queue+0x4a7/0xc40\\n  tcp_rcv_established+0x32f/0x660\\n  ? sk_filter_trim_cap+0xcb/0x2e0\\n  tcp_v4_do_rcv+0x10b/0x260\\n  tcp_v4_rcv+0xd2a/0xde0\\n  ip_protocol_deliver_rcu+0x3b/0x1d0\\n  ip_local_deliver_finish+0x54/0x60\\n  ip_local_deliver+0x6a/0x110\\n  ? tcp_v4_early_demux+0xa2/0x140\\n  ? tcp_v4_early_demux+0x10d/0x140\\n  ip_sublist_rcv_finish+0x49/0x60\\n  ip_sublist_rcv+0x19d/0x230\\n  ip_list_rcv+0x13e/0x170\\n  __netif_receive_skb_list_core+0x1c2/0x240\\n  netif_receive_skb_list_internal+0x1e6/0x320\\n  napi_complete_done+0x11d/0x190\\n  mlx5e_napi_poll+0x163/0x6b0 [mlx5_core]\\n  __napi_poll+0x3c/0x1b0\\n  net_rx_action+0x27c/0x300\\n  __do_softirq+0x114/0x2d2\\n  irq_exit_rcu+0xb4/0xe0\\n  common_interrupt+0xba/0xe0\\n  \u003c/IRQ\u003e\\n  \u003cTASK\u003e\\n\\nThe crash is caused by privately transferring waitqueue entries from\\nsmc socket-\u003ewq to clcsock-\u003ewq. The owners of these entries, such as\\nepoll, have no idea that the entries have been transferred to a\\ndifferent socket wait queue and still use original waitqueue spinlock\\n(smc socket-\u003ewq.wait.lock) to make the entries operation exclusive,\\nbut it doesn\u0027t work. The operations to the entries, such as removing\\nfrom the waitqueue (now is clcsock-\u003ewq after fallback), may cause a\\ncrash when clcsock waitqueue is being iterated over at the moment.\\n\\nThis patch tries to fix this by no longer transferring wait queue\\nentries privately, but introducing own implementations of clcsock\u0027s\\ncallback functions in fallback situation. The callback functions will\\nforward the wakeup to smc socket-\u003ewq if clcsock-\u003ewq is actually woken\\nup and smc socket-\u003ewq has remaining entries.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.22\", \"versionStartIncluding\": \"5.15.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.16.8\", \"versionStartIncluding\": \"5.16\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.17\", \"versionStartIncluding\": \"5.16\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionStartIncluding\": \"5.4.164\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionStartIncluding\": \"5.10.84\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T08:51:56.989Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2022-48721\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T08:51:56.989Z\", \"dateReserved\": \"2024-06-20T11:09:39.051Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-06-20T11:13:12.668Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.