cve-2024-50032
Vulnerability from cvelistv5
Published
2024-10-21 19:39
Modified
2024-12-19 09:31
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: rcu/nocb: Fix rcuog wake-up from offline softirq After a CPU has set itself offline and before it eventually calls rcutree_report_cpu_dead(), there are still opportunities for callbacks to be enqueued, for example from a softirq. When that happens on NOCB, the rcuog wake-up is deferred through an IPI to an online CPU in order not to call into the scheduler and risk arming the RT-bandwidth after hrtimers have been migrated out and disabled. But performing a synchronized IPI from a softirq is buggy as reported in the following scenario: WARNING: CPU: 1 PID: 26 at kernel/smp.c:633 smp_call_function_single Modules linked in: rcutorture torture CPU: 1 UID: 0 PID: 26 Comm: migration/1 Not tainted 6.11.0-rc1-00012-g9139f93209d1 #1 Stopper: multi_cpu_stop+0x0/0x320 <- __stop_cpus+0xd0/0x120 RIP: 0010:smp_call_function_single <IRQ> swake_up_one_online __call_rcu_nocb_wake __call_rcu_common ? rcu_torture_one_read call_timer_fn __run_timers run_timer_softirq handle_softirqs irq_exit_rcu ? tick_handle_periodic sysvec_apic_timer_interrupt </IRQ> Fix this with forcing deferred rcuog wake up through the NOCB timer when the CPU is offline. The actual wake up will happen from rcutree_report_cpu_dead().
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/84a5feebba10354c683983f5f1372a144225e4c2Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e66b1e01f2eb3209d08122572f41f7838b79540dPatch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/f7345ccc62a4b880cf76458db5f320725f28e400Patch
Impacted products
Vendor Product Version
Linux Linux Version: 9b52ee18f6d2f0e845b0dd5ba35edc02ba318827
Version: 00a611229bfad075660181c53e054ff544d3ac34
Version: 9139f93209d1ffd7f489ab19dee01b7c3a1a43d2
 Create a notification for this product.
   Linux Linux Version: 6.6.54   ≤
Version: 6.11.2   ≤
Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            metrics: [
               {
                  other: {
                     content: {
                        id: "CVE-2024-50032",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-10-22T13:25:57.159032Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-10-22T13:28:45.623Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "kernel/rcu/tree_nocb.h",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "84a5feebba10354c683983f5f1372a144225e4c2",
                     status: "affected",
                     version: "9b52ee18f6d2f0e845b0dd5ba35edc02ba318827",
                     versionType: "git",
                  },
                  {
                     lessThan: "e66b1e01f2eb3209d08122572f41f7838b79540d",
                     status: "affected",
                     version: "00a611229bfad075660181c53e054ff544d3ac34",
                     versionType: "git",
                  },
                  {
                     lessThan: "f7345ccc62a4b880cf76458db5f320725f28e400",
                     status: "affected",
                     version: "9139f93209d1ffd7f489ab19dee01b7c3a1a43d2",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "kernel/rcu/tree_nocb.h",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "6.6.57",
                     status: "affected",
                     version: "6.6.54",
                     versionType: "semver",
                  },
                  {
                     lessThan: "6.11.4",
                     status: "affected",
                     version: "6.11.2",
                     versionType: "semver",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nrcu/nocb: Fix rcuog wake-up from offline softirq\n\nAfter a CPU has set itself offline and before it eventually calls\nrcutree_report_cpu_dead(), there are still opportunities for callbacks\nto be enqueued, for example from a softirq. When that happens on NOCB,\nthe rcuog wake-up is deferred through an IPI to an online CPU in order\nnot to call into the scheduler and risk arming the RT-bandwidth after\nhrtimers have been migrated out and disabled.\n\nBut performing a synchronized IPI from a softirq is buggy as reported in\nthe following scenario:\n\n        WARNING: CPU: 1 PID: 26 at kernel/smp.c:633 smp_call_function_single\n        Modules linked in: rcutorture torture\n        CPU: 1 UID: 0 PID: 26 Comm: migration/1 Not tainted 6.11.0-rc1-00012-g9139f93209d1 #1\n        Stopper: multi_cpu_stop+0x0/0x320 <- __stop_cpus+0xd0/0x120\n        RIP: 0010:smp_call_function_single\n        <IRQ>\n        swake_up_one_online\n        __call_rcu_nocb_wake\n        __call_rcu_common\n        ? rcu_torture_one_read\n        call_timer_fn\n        __run_timers\n        run_timer_softirq\n        handle_softirqs\n        irq_exit_rcu\n        ? tick_handle_periodic\n        sysvec_apic_timer_interrupt\n        </IRQ>\n\nFix this with forcing deferred rcuog wake up through the NOCB timer when\nthe CPU is offline. The actual wake up will happen from\nrcutree_report_cpu_dead().",
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-12-19T09:31:44.634Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/84a5feebba10354c683983f5f1372a144225e4c2",
            },
            {
               url: "https://git.kernel.org/stable/c/e66b1e01f2eb3209d08122572f41f7838b79540d",
            },
            {
               url: "https://git.kernel.org/stable/c/f7345ccc62a4b880cf76458db5f320725f28e400",
            },
         ],
         title: "rcu/nocb: Fix rcuog wake-up from offline softirq",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-50032",
      datePublished: "2024-10-21T19:39:34.435Z",
      dateReserved: "2024-10-21T12:17:06.069Z",
      dateUpdated: "2024-12-19T09:31:44.634Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-50032\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-10-21T20:15:16.417\",\"lastModified\":\"2024-10-25T15:34:22.353\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nrcu/nocb: Fix rcuog wake-up from offline softirq\\n\\nAfter a CPU has set itself offline and before it eventually calls\\nrcutree_report_cpu_dead(), there are still opportunities for callbacks\\nto be enqueued, for example from a softirq. When that happens on NOCB,\\nthe rcuog wake-up is deferred through an IPI to an online CPU in order\\nnot to call into the scheduler and risk arming the RT-bandwidth after\\nhrtimers have been migrated out and disabled.\\n\\nBut performing a synchronized IPI from a softirq is buggy as reported in\\nthe following scenario:\\n\\n        WARNING: CPU: 1 PID: 26 at kernel/smp.c:633 smp_call_function_single\\n        Modules linked in: rcutorture torture\\n        CPU: 1 UID: 0 PID: 26 Comm: migration/1 Not tainted 6.11.0-rc1-00012-g9139f93209d1 #1\\n        Stopper: multi_cpu_stop+0x0/0x320 <- __stop_cpus+0xd0/0x120\\n        RIP: 0010:smp_call_function_single\\n        <IRQ>\\n        swake_up_one_online\\n        __call_rcu_nocb_wake\\n        __call_rcu_common\\n        ? rcu_torture_one_read\\n        call_timer_fn\\n        __run_timers\\n        run_timer_softirq\\n        handle_softirqs\\n        irq_exit_rcu\\n        ? tick_handle_periodic\\n        sysvec_apic_timer_interrupt\\n        </IRQ>\\n\\nFix this with forcing deferred rcuog wake up through the NOCB timer when\\nthe CPU is offline. The actual wake up will happen from\\nrcutree_report_cpu_dead().\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: rcu/nocb: Se ha corregido la activación de rcuog desde un softirq sin conexión. Después de que una CPU se haya desconectado y antes de que finalmente llame a rcutree_report_cpu_dead(), aún hay oportunidades para que se pongan en cola devoluciones de llamadas, por ejemplo, desde un softirq. Cuando eso sucede en NOCB, la activación de rcuog se pospone a través de una IPI a una CPU en línea para no llamar al programador y correr el riesgo de armar el ancho de banda RT después de que los temporizadores hr se hayan migrado y deshabilitado. Pero realizar una IPI sincronizada desde un softirq tiene errores, como se informa en el siguiente escenario: ADVERTENCIA: CPU: 1 PID: 26 en kernel/smp.c:633 smp_call_function_single Módulos vinculados en: rcutorture torture CPU: 1 UID: 0 PID: 26 Comm: immigration/1 No contaminado 6.11.0-rc1-00012-g9139f93209d1 #1 Detenedor: multi_cpu_stop+0x0/0x320 &lt;- __stop_cpus+0xd0/0x120 RIP: 0010:smp_call_function_single  swake_up_one_online __call_rcu_nocb_wake __call_rcu_common ? rcu_torture_one_read call_timer_fn __run_timers run_timer_softirq handle_softirqs irq_exit_rcu ? tick_handle_periodic sysvec_apic_timer_interrupt  Solucione esto forzando la activación diferida de rcuog a través del temporizador NOCB cuando la CPU esté fuera de línea. La activación real se realizará desde rcutree_report_cpu_dead().\"}],\"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\":\"6.6.54\",\"versionEndExcluding\":\"6.6.57\",\"matchCriteriaId\":\"28067F77-C1B2-4A04-BA6B-2C4955E8853E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.10.13\",\"versionEndExcluding\":\"6.11\",\"matchCriteriaId\":\"B88D322F-6F03-45A1-8C58-9E45EAB64B13\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.11.2\",\"versionEndExcluding\":\"6.11.4\",\"matchCriteriaId\":\"72A93F71-1302-40DD-847E-3C6D29220EAE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.1.113:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"81EA2611-0623-46DE-8378-F900B6B1EC79\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"7F361E1D-580F-4A2D-A509-7615F73167A1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/84a5feebba10354c683983f5f1372a144225e4c2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/e66b1e01f2eb3209d08122572f41f7838b79540d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/f7345ccc62a4b880cf76458db5f320725f28e400\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-50032\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-10-22T13:25:57.159032Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-10-22T13:26:00.432Z\"}}], \"cna\": {\"title\": \"rcu/nocb: Fix rcuog wake-up from offline softirq\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"9b52ee18f6d2\", \"lessThan\": \"84a5feebba10\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"00a611229bfa\", \"lessThan\": \"e66b1e01f2eb\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"9139f93209d1\", \"lessThan\": \"f7345ccc62a4\", \"versionType\": \"git\"}], \"programFiles\": [\"kernel/rcu/tree_nocb.h\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.12-rc1\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.12-rc1\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.6.57\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.4\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12-rc3\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"kernel/rcu/tree_nocb.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/84a5feebba10354c683983f5f1372a144225e4c2\"}, {\"url\": \"https://git.kernel.org/stable/c/e66b1e01f2eb3209d08122572f41f7838b79540d\"}, {\"url\": \"https://git.kernel.org/stable/c/f7345ccc62a4b880cf76458db5f320725f28e400\"}], \"x_generator\": {\"engine\": \"bippy-9e1c9544281a\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nrcu/nocb: Fix rcuog wake-up from offline softirq\\n\\nAfter a CPU has set itself offline and before it eventually calls\\nrcutree_report_cpu_dead(), there are still opportunities for callbacks\\nto be enqueued, for example from a softirq. When that happens on NOCB,\\nthe rcuog wake-up is deferred through an IPI to an online CPU in order\\nnot to call into the scheduler and risk arming the RT-bandwidth after\\nhrtimers have been migrated out and disabled.\\n\\nBut performing a synchronized IPI from a softirq is buggy as reported in\\nthe following scenario:\\n\\n        WARNING: CPU: 1 PID: 26 at kernel/smp.c:633 smp_call_function_single\\n        Modules linked in: rcutorture torture\\n        CPU: 1 UID: 0 PID: 26 Comm: migration/1 Not tainted 6.11.0-rc1-00012-g9139f93209d1 #1\\n        Stopper: multi_cpu_stop+0x0/0x320 <- __stop_cpus+0xd0/0x120\\n        RIP: 0010:smp_call_function_single\\n        <IRQ>\\n        swake_up_one_online\\n        __call_rcu_nocb_wake\\n        __call_rcu_common\\n        ? rcu_torture_one_read\\n        call_timer_fn\\n        __run_timers\\n        run_timer_softirq\\n        handle_softirqs\\n        irq_exit_rcu\\n        ? tick_handle_periodic\\n        sysvec_apic_timer_interrupt\\n        </IRQ>\\n\\nFix this with forcing deferred rcuog wake up through the NOCB timer when\\nthe CPU is offline. The actual wake up will happen from\\nrcutree_report_cpu_dead().\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-11-05T09:53:50.810Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2024-50032\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-11-05T09:53:50.810Z\", \"dateReserved\": \"2024-10-21T12:17:06.069Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-10-21T19:39:34.435Z\", \"assignerShortName\": \"Linux\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


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.