fkie_cve-2024-53210
Vulnerability from fkie_nvd
Published
2024-12-27 14:15
Modified
2025-01-14 15:50
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct() Passing MSG_PEEK flag to skb_recv_datagram() increments skb refcount (skb->users) and iucv_sock_recvmsg() does not decrement skb refcount at exit. This results in skb memory leak in skb_queue_purge() and WARN_ON in iucv_sock_destruct() during socket close. To fix this decrease skb refcount by one if MSG_PEEK is set in order to prevent memory leak and WARN_ON. WARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv] CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G W 6.10.0-rc7 #1 Hardware name: IBM 3931 A01 704 (z/VM 7.3.0) Call Trace: [<001587c682c4aa98>] iucv_sock_destruct+0x148/0x1a0 [af_iucv] [<001587c682c4a9d0>] iucv_sock_destruct+0x80/0x1a0 [af_iucv] [<001587c704117a32>] __sk_destruct+0x52/0x550 [<001587c704104a54>] __sock_release+0xa4/0x230 [<001587c704104c0c>] sock_close+0x2c/0x40 [<001587c702c5f5a8>] __fput+0x2e8/0x970 [<001587c7024148c4>] task_work_run+0x1c4/0x2c0 [<001587c7023b0716>] do_exit+0x996/0x1050 [<001587c7023b13aa>] do_group_exit+0x13a/0x360 [<001587c7023b1626>] __s390x_sys_exit_group+0x56/0x60 [<001587c7022bccca>] do_syscall+0x27a/0x380 [<001587c7049a6a0c>] __do_syscall+0x9c/0x160 [<001587c7049ce8a8>] system_call+0x70/0x98 Last Breaking-Event-Address: [<001587c682c4a9d4>] iucv_sock_destruct+0x84/0x1a0 [af_iucv]
Impacted products



{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "1B71E394-0408-4562-9D95-9A76BEE44EC2",
                     versionEndExcluding: "6.1.120",
                     versionStartIncluding: "2.6.21",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "CA16DEE3-ABEC-4449-9F4A-7A3DC4FC36C7",
                     versionEndExcluding: "6.6.64",
                     versionStartIncluding: "6.2",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "21434379-192D-472F-9B54-D45E3650E893",
                     versionEndExcluding: "6.11.11",
                     versionStartIncluding: "6.7",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "D8882B1B-2ABC-4838-AC1D-DBDBB5764776",
                     versionEndExcluding: "6.12.2",
                     versionStartIncluding: "6.12",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/iucv: MSG_PEEK causes memory leak in iucv_sock_destruct()\n\nPassing MSG_PEEK flag to skb_recv_datagram() increments skb refcount\n(skb->users) and iucv_sock_recvmsg() does not decrement skb refcount\nat exit.\nThis results in skb memory leak in skb_queue_purge() and WARN_ON in\niucv_sock_destruct() during socket close. To fix this decrease\nskb refcount by one if MSG_PEEK is set in order to prevent memory\nleak and WARN_ON.\n\nWARNING: CPU: 2 PID: 6292 at net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv]\nCPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: loaded Tainted: G        W          6.10.0-rc7 #1\nHardware name: IBM 3931 A01 704 (z/VM 7.3.0)\nCall Trace:\n        [<001587c682c4aa98>] iucv_sock_destruct+0x148/0x1a0 [af_iucv]\n        [<001587c682c4a9d0>] iucv_sock_destruct+0x80/0x1a0 [af_iucv]\n        [<001587c704117a32>] __sk_destruct+0x52/0x550\n        [<001587c704104a54>] __sock_release+0xa4/0x230\n        [<001587c704104c0c>] sock_close+0x2c/0x40\n        [<001587c702c5f5a8>] __fput+0x2e8/0x970\n        [<001587c7024148c4>] task_work_run+0x1c4/0x2c0\n        [<001587c7023b0716>] do_exit+0x996/0x1050\n        [<001587c7023b13aa>] do_group_exit+0x13a/0x360\n        [<001587c7023b1626>] __s390x_sys_exit_group+0x56/0x60\n        [<001587c7022bccca>] do_syscall+0x27a/0x380\n        [<001587c7049a6a0c>] __do_syscall+0x9c/0x160\n        [<001587c7049ce8a8>] system_call+0x70/0x98\n        Last Breaking-Event-Address:\n        [<001587c682c4a9d4>] iucv_sock_destruct+0x84/0x1a0 [af_iucv]",
      },
      {
         lang: "es",
         value: "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: s390/iucv: MSG_PEEK provoca una pérdida de memoria en iucv_sock_destruct(). Pasar el indicador MSG_PEEK a skb_recv_datagram() incrementa el recuento de referencias de skb (skb-&gt;users) y iucv_sock_recvmsg() no decrementa el recuento de referencias de skb al salir. Esto da como resultado una pérdida de memoria de skb en skb_queue_purge() y WARN_ON en iucv_sock_destruct() durante el cierre del socket. Para solucionar esto, disminuya el recuento de referencias de skb en uno si MSG_PEEK está configurado para evitar la pérdida de memoria y WARN_ON. ADVERTENCIA: CPU: 2 PID: 6292 en net/iucv/af_iucv.c:286 iucv_sock_destruct+0x144/0x1a0 [af_iucv] CPU: 2 PID: 6292 Comm: afiucv_test_msg Kdump: cargado Contaminado: GW 6.10.0-rc7 #1 Nombre del hardware: IBM 3931 A01 704 (z/VM 7.3.0) Rastreo de llamadas: [&lt;001587c682c4aa98&gt;] iucv_sock_destruct+0x148/0x1a0 [af_iucv] [&lt;001587c682c4a9d0&gt;] iucv_sock_destruct+0x80/0x1a0 [af_iucv] [&lt;001587c704117a32&gt;] __sk_destruct+0x52/0x550 [&lt;001587c704104a54&gt;] __sock_release+0xa4/0x230 [&lt;001587c704104c0c&gt;] sock_close+0x2c/0x40 [&lt;001587c702c5f5a8&gt;] __fput+0x2e8/0x970 [&lt;001587c7024148c4&gt;] task_work_run+0x1c4/0x2c0 [&lt;001587c7023b0716&gt;] do_exit+0x996/0x1050 [&lt;001587c7023b13aa&gt;] do_group_exit+0x13a/0x360 [&lt;001587c7023b1626&gt;] __s390x_sys_exit_group+0x56/0x60 [&lt;001587c7022bccca&gt;] do_syscall+0x27a/0x380 [&lt;001587c7049a6a0c&gt;] __do_syscall+0x9c/0x160 [&lt;001587c7049ce8a8&gt;] system_call+0x70/0x98 Última dirección del evento de interrupción: [&lt;001587c682c4a9d4&gt;] iucv_sock_destruct+0x84/0x1a0 [af_iucv]",
      },
   ],
   id: "CVE-2024-53210",
   lastModified: "2025-01-14T15:50:32.413",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "LOCAL",
               availabilityImpact: "HIGH",
               baseScore: 5.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 1.8,
            impactScore: 3.6,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2024-12-27T14:15:28.897",
   references: [
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/42251c2d1ef1cb0822638bebb87ad9120c759673",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/783c2c6e61c5a04eb8baea598753d5fa174dbe85",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/934326aef7ac4652f81c69d18bf44eebaefc39c3",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/9f603e66e1c59c1d25e60eb0636cb307d190782e",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/ebaf81317e42aa990ad20b113cfe3a7b20d4e937",
      },
   ],
   sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
   vulnStatus: "Analyzed",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-401",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


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.


Loading…

Loading…

Loading…

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.