CVE-2022-49973 (GCVE-0-2022-49973)
Vulnerability from cvelistv5
Published
2025-06-18 11:00
Modified
2025-06-18 11:00
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: skmsg: Fix wrong last sg check in sk_msg_recvmsg() Fix one kernel NULL pointer dereference as below: [ 224.462334] Call Trace: [ 224.462394] __tcp_bpf_recvmsg+0xd3/0x380 [ 224.462441] ? sock_has_perm+0x78/0xa0 [ 224.462463] tcp_bpf_recvmsg+0x12e/0x220 [ 224.462494] inet_recvmsg+0x5b/0xd0 [ 224.462534] __sys_recvfrom+0xc8/0x130 [ 224.462574] ? syscall_trace_enter+0x1df/0x2e0 [ 224.462606] ? __do_page_fault+0x2de/0x500 [ 224.462635] __x64_sys_recvfrom+0x24/0x30 [ 224.462660] do_syscall_64+0x5d/0x1d0 [ 224.462709] entry_SYSCALL_64_after_hwframe+0x65/0xca In commit 9974d37ea75f ("skmsg: Fix invalid last sg check in sk_msg_recvmsg()"), we change last sg check to sg_is_last(), but in sockmap redirection case (without stream_parser/stream_verdict/ skb_verdict), we did not mark the end of the scatterlist. Check the sk_msg_alloc, sk_msg_page_add, and bpf_msg_push_data functions, they all do not mark the end of sg. They are expected to use sg.end for end judgment. So the judgment of '(i != msg_rx->sg.end)' is added back here.
References
Impacted products
Vendor Product Version
Linux Linux Version: 293c53b7dbf9073cbcc488f938bc053ff4caeec0
Version: 1295dae30f30c3daa03005ed8958d44b17f037fd
Version: 9974d37ea75f01b47d16072b5dad305bd8d23fcc
Version: 4674c0da448b546e390a981b819cd4af5cb16cf9
 Create a notification for this product.
   Linux Linux Version: 5.15.61   ≤
Version: 5.19.2   ≤
Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/core/skmsg.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "de22cba333d8699ad77e79f862fe1320cb1284de",
              "status": "affected",
              "version": "293c53b7dbf9073cbcc488f938bc053ff4caeec0",
              "versionType": "git"
            },
            {
              "lessThan": "10ee118a1756141f8e9c87aa7344ed12b41630a8",
              "status": "affected",
              "version": "1295dae30f30c3daa03005ed8958d44b17f037fd",
              "versionType": "git"
            },
            {
              "lessThan": "583585e48d965338e73e1eb383768d16e0922d73",
              "status": "affected",
              "version": "9974d37ea75f01b47d16072b5dad305bd8d23fcc",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "4674c0da448b546e390a981b819cd4af5cb16cf9",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/core/skmsg.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5.15.66",
              "status": "affected",
              "version": "5.15.61",
              "versionType": "semver"
            },
            {
              "lessThan": "5.19.8",
              "status": "affected",
              "version": "5.19.2",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.66",
                  "versionStartIncluding": "5.15.61",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.19.8",
                  "versionStartIncluding": "5.19.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.18.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nskmsg: Fix wrong last sg check in sk_msg_recvmsg()\n\nFix one kernel NULL pointer dereference as below:\n\n[  224.462334] Call Trace:\n[  224.462394]  __tcp_bpf_recvmsg+0xd3/0x380\n[  224.462441]  ? sock_has_perm+0x78/0xa0\n[  224.462463]  tcp_bpf_recvmsg+0x12e/0x220\n[  224.462494]  inet_recvmsg+0x5b/0xd0\n[  224.462534]  __sys_recvfrom+0xc8/0x130\n[  224.462574]  ? syscall_trace_enter+0x1df/0x2e0\n[  224.462606]  ? __do_page_fault+0x2de/0x500\n[  224.462635]  __x64_sys_recvfrom+0x24/0x30\n[  224.462660]  do_syscall_64+0x5d/0x1d0\n[  224.462709]  entry_SYSCALL_64_after_hwframe+0x65/0xca\n\nIn commit 9974d37ea75f (\"skmsg: Fix invalid last sg check in\nsk_msg_recvmsg()\"), we change last sg check to sg_is_last(),\nbut in sockmap redirection case (without stream_parser/stream_verdict/\nskb_verdict), we did not mark the end of the scatterlist. Check the\nsk_msg_alloc, sk_msg_page_add, and bpf_msg_push_data functions, they all\ndo not mark the end of sg. They are expected to use sg.end for end\njudgment. So the judgment of \u0027(i != msg_rx-\u003esg.end)\u0027 is added back here."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-06-18T11:00:36.303Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/de22cba333d8699ad77e79f862fe1320cb1284de"
        },
        {
          "url": "https://git.kernel.org/stable/c/10ee118a1756141f8e9c87aa7344ed12b41630a8"
        },
        {
          "url": "https://git.kernel.org/stable/c/583585e48d965338e73e1eb383768d16e0922d73"
        }
      ],
      "title": "skmsg: Fix wrong last sg check in sk_msg_recvmsg()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-49973",
    "datePublished": "2025-06-18T11:00:36.303Z",
    "dateReserved": "2025-06-18T10:57:27.384Z",
    "dateUpdated": "2025-06-18T11:00:36.303Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-49973\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-06-18T11:15:24.673\",\"lastModified\":\"2025-06-18T13:46:52.973\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nskmsg: Fix wrong last sg check in sk_msg_recvmsg()\\n\\nFix one kernel NULL pointer dereference as below:\\n\\n[  224.462334] Call Trace:\\n[  224.462394]  __tcp_bpf_recvmsg+0xd3/0x380\\n[  224.462441]  ? sock_has_perm+0x78/0xa0\\n[  224.462463]  tcp_bpf_recvmsg+0x12e/0x220\\n[  224.462494]  inet_recvmsg+0x5b/0xd0\\n[  224.462534]  __sys_recvfrom+0xc8/0x130\\n[  224.462574]  ? syscall_trace_enter+0x1df/0x2e0\\n[  224.462606]  ? __do_page_fault+0x2de/0x500\\n[  224.462635]  __x64_sys_recvfrom+0x24/0x30\\n[  224.462660]  do_syscall_64+0x5d/0x1d0\\n[  224.462709]  entry_SYSCALL_64_after_hwframe+0x65/0xca\\n\\nIn commit 9974d37ea75f (\\\"skmsg: Fix invalid last sg check in\\nsk_msg_recvmsg()\\\"), we change last sg check to sg_is_last(),\\nbut in sockmap redirection case (without stream_parser/stream_verdict/\\nskb_verdict), we did not mark the end of the scatterlist. Check the\\nsk_msg_alloc, sk_msg_page_add, and bpf_msg_push_data functions, they all\\ndo not mark the end of sg. They are expected to use sg.end for end\\njudgment. So the judgment of \u0027(i != msg_rx-\u003esg.end)\u0027 is added back here.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: skmsg: Corrige la \u00faltima comprobaci\u00f3n sg incorrecta en sk_msg_recvmsg() Corrige una desreferencia de puntero NULL del kernel como se muestra a continuaci\u00f3n: [224.462334] Seguimiento de llamadas: [224.462394] __tcp_bpf_recvmsg+0xd3/0x380 [224.462441] ? syscall_trace_enter+0x1df/0x2e0 [ 224.462606] ? __do_page_fault+0x2de/0x500 [ 224.462635] __x64_sys_recvfrom+0x24/0x30 [ 224.462660] do_syscall_64+0x5d/0x1d0 [ 224.462709] entry_SYSCALL_64_after_hwframe+0x65/0xca En el commit 9974d37ea75f (\\\"skmsg: Corregir la \u00faltima comprobaci\u00f3n de sg no v\u00e1lida en sk_msg_recvmsg()\\\"), cambiamos la \u00faltima comprobaci\u00f3n de sg a sg_is_last(), pero en el caso de redirecci\u00f3n de sockmap (sin stream_parser/stream_verdict/skb_verdict), no marcamos el final de la lista de dispersi\u00f3n. Verifique las funciones sk_msg_alloc, sk_msg_page_add y bpf_msg_push_data; ninguna marca el final de sg. Se espera que usen sg.end para la determinaci\u00f3n del final. Por lo tanto, se a\u00f1ade aqu\u00ed la determinaci\u00f3n de \u0027(i != msg_rx-\u0026gt;sg.end)\u0027.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/10ee118a1756141f8e9c87aa7344ed12b41630a8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/583585e48d965338e73e1eb383768d16e0922d73\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/de22cba333d8699ad77e79f862fe1320cb1284de\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


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