cve-2024-56641
Vulnerability from cvelistv5
Published
2024-12-27 15:02
Modified
2025-01-20 06:24
Severity ?
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.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0541db8ee32c09463a72d0987382b3a3336b0043
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6638e52dcfafaf1b9cbc34544f0c832db0069ea1
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/f0c37002210aaede10dae849d1a78efc2243add2
Impacted products
Vendor Product Version
Linux Linux Version: 46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e
Version: 46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e
Version: 46c28dbd4c23c3f7fa37f5ea48772af79c9cc40e
 Create a notification for this product.
   Linux Linux Version: 4.12
 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",
                  },
               ],
            },
         ],
         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->close_work is\nflushed before initialization, resulting in WARN_ON(!work->func).\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->conns_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(&close_work)\n\nSo fix this by initializing close_work before establishing the\nconnection.",
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-01-20T06:24:52.698Z",
            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-5f407fcff5a0",
         },
      },
   },
   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: "2025-01-20T06:24:52.698Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-56641\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-27T15:15:23.830\",\"lastModified\":\"2024-12-27T15:15:23.830\",\"vulnStatus\":\"Received\",\"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->close_work is\\nflushed before initialization, resulting in WARN_ON(!work->func).\\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->conns_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(&close_work)\\n\\nSo fix this by initializing close_work before establishing the\\nconnection.\"}],\"metrics\":{},\"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\"}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.
  • 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.