CVE-2024-56641 (GCVE-0-2024-56641)

Vulnerability from cvelistv5 – Published: 2024-12-27 15:02 – Updated: 2026-05-11 20:56
VLAI?
Title
net/smc: initialize close_work early to avoid warning
Summary
In the Linux kernel, the following vulnerability has been resolved: net/smc: initialize close_work early to avoid warning We encountered a warning that close_work was canceled before initialization. WARNING: CPU: 7 PID: 111103 at kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0 Workqueue: events smc_lgr_terminate_work [smc] RIP: 0010:__flush_work+0x19e/0x1b0 Call Trace: ? __wake_up_common+0x7a/0x190 ? work_busy+0x80/0x80 __cancel_work_timer+0xe3/0x160 smc_close_cancel_work+0x1a/0x70 [smc] smc_close_active_abort+0x207/0x360 [smc] __smc_lgr_terminate.part.38+0xc8/0x180 [smc] process_one_work+0x19e/0x340 worker_thread+0x30/0x370 ? process_one_work+0x340/0x340 kthread+0x117/0x130 ? __kthread_cancel_work+0x50/0x50 ret_from_fork+0x22/0x30 This is because when smc_close_cancel_work is triggered, e.g. the RDMA driver is rmmod and the LGR is terminated, the conn->close_work is flushed before initialization, resulting in WARN_ON(!work->func). __smc_lgr_terminate | smc_connect_{rdma|ism} ------------------------------------------------------------- | smc_conn_create | \- smc_lgr_register_conn for conn in lgr->conns_all | \- smc_conn_kill | \- smc_close_active_abort | \- smc_close_cancel_work | \- cancel_work_sync | \- __flush_work | (close_work) | | smc_close_init | \- INIT_WORK(&close_work) So fix this by initializing close_work before establishing the connection.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e , < f0c37002210aaede10dae849d1a78efc2243add2 (git)
Affected: 46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e , < 6638e52dcfafaf1b9cbc34544f0c832db0069ea1 (git)
Affected: 46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e , < 0541db8ee32c09463a72d0987382b3a3336b0043 (git)
Create a notification for this product.
Linux Linux Affected: 4.12
Unaffected: 0 , < 4.12 (semver)
Unaffected: 6.6.66 , ≤ 6.6.* (semver)
Unaffected: 6.12.5 , ≤ 6.12.* (semver)
Unaffected: 6.13 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/smc/af_smc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f0c37002210aaede10dae849d1a78efc2243add2",
              "status": "affected",
              "version": "46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e",
              "versionType": "git"
            },
            {
              "lessThan": "6638e52dcfafaf1b9cbc34544f0c832db0069ea1",
              "status": "affected",
              "version": "46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e",
              "versionType": "git"
            },
            {
              "lessThan": "0541db8ee32c09463a72d0987382b3a3336b0043",
              "status": "affected",
              "version": "46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/smc/af_smc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.12"
            },
            {
              "lessThan": "4.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.66",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.66",
                  "versionStartIncluding": "4.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.5",
                  "versionStartIncluding": "4.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "4.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: initialize close_work early to avoid warning\n\nWe encountered a warning that close_work was canceled before\ninitialization.\n\n  WARNING: CPU: 7 PID: 111103 at kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0\n  Workqueue: events smc_lgr_terminate_work [smc]\n  RIP: 0010:__flush_work+0x19e/0x1b0\n  Call Trace:\n   ? __wake_up_common+0x7a/0x190\n   ? work_busy+0x80/0x80\n   __cancel_work_timer+0xe3/0x160\n   smc_close_cancel_work+0x1a/0x70 [smc]\n   smc_close_active_abort+0x207/0x360 [smc]\n   __smc_lgr_terminate.part.38+0xc8/0x180 [smc]\n   process_one_work+0x19e/0x340\n   worker_thread+0x30/0x370\n   ? process_one_work+0x340/0x340\n   kthread+0x117/0x130\n   ? __kthread_cancel_work+0x50/0x50\n   ret_from_fork+0x22/0x30\n\nThis is because when smc_close_cancel_work is triggered, e.g. the RDMA\ndriver is rmmod and the LGR is terminated, the conn-\u003eclose_work is\nflushed before initialization, resulting in WARN_ON(!work-\u003efunc).\n\n__smc_lgr_terminate             | smc_connect_{rdma|ism}\n-------------------------------------------------------------\n                                | smc_conn_create\n\t\t\t\t| \\- smc_lgr_register_conn\nfor conn in lgr-\u003econns_all      |\n\\- smc_conn_kill                |\n   \\- smc_close_active_abort    |\n      \\- smc_close_cancel_work  |\n         \\- cancel_work_sync    |\n            \\- __flush_work     |\n\t         (close_work)   |\n\t                        | smc_close_init\n\t                        | \\- INIT_WORK(\u0026close_work)\n\nSo fix this by initializing close_work before establishing the\nconnection."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:56:25.107Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2"
        },
        {
          "url": "https://git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1"
        },
        {
          "url": "https://git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043"
        }
      ],
      "title": "net/smc: initialize close_work early to avoid warning",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-56641",
    "datePublished": "2024-12-27T15:02:42.958Z",
    "dateReserved": "2024-12-27T15:00:39.839Z",
    "dateUpdated": "2026-05-11T20:56:25.107Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-56641",
      "date": "2026-05-21",
      "epss": "9e-05",
      "percentile": "0.00976"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/smc: initialize close_work early to avoid warning\\n\\nWe encountered a warning that close_work was canceled before\\ninitialization.\\n\\n  WARNING: CPU: 7 PID: 111103 at kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0\\n  Workqueue: events smc_lgr_terminate_work [smc]\\n  RIP: 0010:__flush_work+0x19e/0x1b0\\n  Call Trace:\\n   ? __wake_up_common+0x7a/0x190\\n   ? work_busy+0x80/0x80\\n   __cancel_work_timer+0xe3/0x160\\n   smc_close_cancel_work+0x1a/0x70 [smc]\\n   smc_close_active_abort+0x207/0x360 [smc]\\n   __smc_lgr_terminate.part.38+0xc8/0x180 [smc]\\n   process_one_work+0x19e/0x340\\n   worker_thread+0x30/0x370\\n   ? process_one_work+0x340/0x340\\n   kthread+0x117/0x130\\n   ? __kthread_cancel_work+0x50/0x50\\n   ret_from_fork+0x22/0x30\\n\\nThis is because when smc_close_cancel_work is triggered, e.g. the RDMA\\ndriver is rmmod and the LGR is terminated, the conn-\u003eclose_work is\\nflushed before initialization, resulting in WARN_ON(!work-\u003efunc).\\n\\n__smc_lgr_terminate             | smc_connect_{rdma|ism}\\n-------------------------------------------------------------\\n                                | smc_conn_create\\n\\t\\t\\t\\t| \\\\- smc_lgr_register_conn\\nfor conn in lgr-\u003econns_all      |\\n\\\\- smc_conn_kill                |\\n   \\\\- smc_close_active_abort    |\\n      \\\\- smc_close_cancel_work  |\\n         \\\\- cancel_work_sync    |\\n            \\\\- __flush_work     |\\n\\t         (close_work)   |\\n\\t                        | smc_close_init\\n\\t                        | \\\\- INIT_WORK(\u0026close_work)\\n\\nSo fix this by initializing close_work before establishing the\\nconnection.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/smc: inicializar close_work antes para evitar advertencias Encontramos una advertencia que indicaba que close_work se cancel\\u00f3 antes de la inicializaci\\u00f3n. ADVERTENCIA: CPU: 7 PID: 111103 en kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0 Workqueue: eventos smc_lgr_terminate_work [smc] RIP: 0010:__flush_work+0x19e/0x1b0 Rastreo de llamadas: ? __wake_up_common+0x7a/0x190 ? trabajo_ocupado+0x80/0x80 __cancelar_temporizador_trabajo+0xe3/0x160 smc_cerrar_cancelar_trabajo+0x1a/0x70 [smc] smc_cerrar_aborto_activo+0x207/0x360 [smc] __smc_lgr_terminate.part.38+0xc8/0x180 [smc] proceso_uno_trabajo+0x19e/0x340 subproceso_trabajador+0x30/0x370 ? proceso_uno_trabajo+0x340/0x340 kthread+0x117/0x130 ? __kthread_cancel_work+0x50/0x50 ret_from_fork+0x22/0x30 Esto se debe a que cuando se activa smc_close_cancel_work, p. ej., el controlador RDMA es rmmod y se termina el LGR, conn-\u0026gt;close_work se vac\\u00eda antes de la inicializaci\\u00f3n, lo que genera WARN_ON(!work-\u0026gt;func). __smc_lgr_terminate | smc_connect_{rdma|ism} ------------------------------------------------------------- | smc_conn_create | \\\\- smc_lgr_register_conn para conn en lgr-\u0026gt;conns_all | \\\\- smc_conn_kill | \\\\- smc_close_active_abort | \\\\- smc_close_cancel_work | \\\\- cancel_work_sync | \\\\- __flush_work | (close_work) | | smc_close_init | \\\\- INIT_WORK(\u0026amp;close_work) Solucione esto inicializando close_work antes de establecer la conexi\\u00f3n.\"}]",
      "id": "CVE-2024-56641",
      "lastModified": "2024-12-27T15:15:23.830",
      "published": "2024-12-27T15:15:23.830",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-56641\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-27T15:15:23.830\",\"lastModified\":\"2025-10-06T17:38:15.090\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/smc: initialize close_work early to avoid warning\\n\\nWe encountered a warning that close_work was canceled before\\ninitialization.\\n\\n  WARNING: CPU: 7 PID: 111103 at kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0\\n  Workqueue: events smc_lgr_terminate_work [smc]\\n  RIP: 0010:__flush_work+0x19e/0x1b0\\n  Call Trace:\\n   ? __wake_up_common+0x7a/0x190\\n   ? work_busy+0x80/0x80\\n   __cancel_work_timer+0xe3/0x160\\n   smc_close_cancel_work+0x1a/0x70 [smc]\\n   smc_close_active_abort+0x207/0x360 [smc]\\n   __smc_lgr_terminate.part.38+0xc8/0x180 [smc]\\n   process_one_work+0x19e/0x340\\n   worker_thread+0x30/0x370\\n   ? process_one_work+0x340/0x340\\n   kthread+0x117/0x130\\n   ? __kthread_cancel_work+0x50/0x50\\n   ret_from_fork+0x22/0x30\\n\\nThis is because when smc_close_cancel_work is triggered, e.g. the RDMA\\ndriver is rmmod and the LGR is terminated, the conn-\u003eclose_work is\\nflushed before initialization, resulting in WARN_ON(!work-\u003efunc).\\n\\n__smc_lgr_terminate             | smc_connect_{rdma|ism}\\n-------------------------------------------------------------\\n                                | smc_conn_create\\n\\t\\t\\t\\t| \\\\- smc_lgr_register_conn\\nfor conn in lgr-\u003econns_all      |\\n\\\\- smc_conn_kill                |\\n   \\\\- smc_close_active_abort    |\\n      \\\\- smc_close_cancel_work  |\\n         \\\\- cancel_work_sync    |\\n            \\\\- __flush_work     |\\n\\t         (close_work)   |\\n\\t                        | smc_close_init\\n\\t                        | \\\\- INIT_WORK(\u0026close_work)\\n\\nSo fix this by initializing close_work before establishing the\\nconnection.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/smc: inicializar close_work antes para evitar advertencias Encontramos una advertencia que indicaba que close_work se cancel\u00f3 antes de la inicializaci\u00f3n. ADVERTENCIA: CPU: 7 PID: 111103 en kernel/workqueue.c:3047 __flush_work+0x19e/0x1b0 Workqueue: eventos smc_lgr_terminate_work [smc] RIP: 0010:__flush_work+0x19e/0x1b0 Rastreo de llamadas: ? __wake_up_common+0x7a/0x190 ? trabajo_ocupado+0x80/0x80 __cancelar_temporizador_trabajo+0xe3/0x160 smc_cerrar_cancelar_trabajo+0x1a/0x70 [smc] smc_cerrar_aborto_activo+0x207/0x360 [smc] __smc_lgr_terminate.part.38+0xc8/0x180 [smc] proceso_uno_trabajo+0x19e/0x340 subproceso_trabajador+0x30/0x370 ? proceso_uno_trabajo+0x340/0x340 kthread+0x117/0x130 ? __kthread_cancel_work+0x50/0x50 ret_from_fork+0x22/0x30 Esto se debe a que cuando se activa smc_close_cancel_work, p. ej., el controlador RDMA es rmmod y se termina el LGR, conn-\u0026gt;close_work se vac\u00eda antes de la inicializaci\u00f3n, lo que genera WARN_ON(!work-\u0026gt;func). __smc_lgr_terminate | smc_connect_{rdma|ism} ------------------------------------------------------------- | smc_conn_create | \\\\- smc_lgr_register_conn para conn en lgr-\u0026gt;conns_all | \\\\- smc_conn_kill | \\\\- smc_close_active_abort | \\\\- smc_close_cancel_work | \\\\- cancel_work_sync | \\\\- __flush_work | (close_work) | | smc_close_init | \\\\- INIT_WORK(\u0026amp;close_work) Solucione esto inicializando close_work antes de establecer la conexi\u00f3n.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"4.12\",\"versionEndExcluding\":\"6.6.66\",\"matchCriteriaId\":\"8D1BA5AF-8DA3-47DD-8406-865833A2A5FC\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.12.5\",\"matchCriteriaId\":\"9501D045-7A94-42CA-8B03-821BE94A65B7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"62567B3C-6CEE-46D0-BC2E-B3717FBF7D13\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


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.