cve-2024-58100
Vulnerability from cvelistv5
Published
2025-05-05 14:53
Modified
2025-05-09 08:06
Severity ?
Summary
bpf: check changes_pkt_data property for extension programs
Impacted products
LinuxLinux
LinuxLinux
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "include/linux/bpf.h",
            "kernel/bpf/verifier.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7",
              "status": "affected",
              "version": "be8704ff07d2374bcc5c675526f95e70c6459683",
              "versionType": "git"
            },
            {
              "lessThan": "3846e2bea565ee1c5195dcc625fda9868fb0e3b3",
              "status": "affected",
              "version": "be8704ff07d2374bcc5c675526f95e70c6459683",
              "versionType": "git"
            },
            {
              "lessThan": "81f6d0530ba031b5f038a091619bf2ff29568852",
              "status": "affected",
              "version": "be8704ff07d2374bcc5c675526f95e70c6459683",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "include/linux/bpf.h",
            "kernel/bpf/verifier.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.6"
            },
            {
              "lessThan": "5.6",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.90",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.25",
              "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.90",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.25",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "5.6",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: check changes_pkt_data property for extension programs\n\nWhen processing calls to global sub-programs, verifier decides whether\nto invalidate all packet pointers in current state depending on the\nchanges_pkt_data property of the global sub-program.\n\nBecause of this, an extension program replacing a global sub-program\nmust be compatible with changes_pkt_data property of the sub-program\nbeing replaced.\n\nThis commit:\n- adds changes_pkt_data flag to struct bpf_prog_aux:\n  - this flag is set in check_cfg() for main sub-program;\n  - in jit_subprogs() for other sub-programs;\n- modifies bpf_check_attach_btf_id() to check changes_pkt_data flag;\n- moves call to check_attach_btf_id() after the call to check_cfg(),\n  because it needs changes_pkt_data flag to be set:\n\n    bpf_check:\n      ...                             ...\n    - check_attach_btf_id             resolve_pseudo_ldimm64\n      resolve_pseudo_ldimm64   --\u003e    bpf_prog_is_offloaded\n      bpf_prog_is_offloaded           check_cfg\n      check_cfg                     + check_attach_btf_id\n      ...                             ...\n\nThe following fields are set by check_attach_btf_id():\n- env-\u003eops\n- prog-\u003eaux-\u003eattach_btf_trace\n- prog-\u003eaux-\u003eattach_func_name\n- prog-\u003eaux-\u003eattach_func_proto\n- prog-\u003eaux-\u003edst_trampoline\n- prog-\u003eaux-\u003emod\n- prog-\u003eaux-\u003esaved_dst_attach_type\n- prog-\u003eaux-\u003esaved_dst_prog_type\n- prog-\u003eexpected_attach_type\n\nNeither of these fields are used by resolve_pseudo_ldimm64() or\nbpf_prog_offload_verifier_prep() (for netronome and netdevsim\ndrivers), so the reordering is safe."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-09T08:06:09.147Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7"
        },
        {
          "url": "https://git.kernel.org/stable/c/3846e2bea565ee1c5195dcc625fda9868fb0e3b3"
        },
        {
          "url": "https://git.kernel.org/stable/c/81f6d0530ba031b5f038a091619bf2ff29568852"
        }
      ],
      "title": "bpf: check changes_pkt_data property for extension programs",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-58100",
    "datePublished": "2025-05-05T14:53:33.445Z",
    "dateReserved": "2025-03-06T15:52:09.189Z",
    "dateUpdated": "2025-05-09T08:06:09.147Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-58100\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-05-05T15:15:53.913\",\"lastModified\":\"2025-05-09T08:15:18.937\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nbpf: check changes_pkt_data property for extension programs\\n\\nWhen processing calls to global sub-programs, verifier decides whether\\nto invalidate all packet pointers in current state depending on the\\nchanges_pkt_data property of the global sub-program.\\n\\nBecause of this, an extension program replacing a global sub-program\\nmust be compatible with changes_pkt_data property of the sub-program\\nbeing replaced.\\n\\nThis commit:\\n- adds changes_pkt_data flag to struct bpf_prog_aux:\\n  - this flag is set in check_cfg() for main sub-program;\\n  - in jit_subprogs() for other sub-programs;\\n- modifies bpf_check_attach_btf_id() to check changes_pkt_data flag;\\n- moves call to check_attach_btf_id() after the call to check_cfg(),\\n  because it needs changes_pkt_data flag to be set:\\n\\n    bpf_check:\\n      ...                             ...\\n    - check_attach_btf_id             resolve_pseudo_ldimm64\\n      resolve_pseudo_ldimm64   --\u003e    bpf_prog_is_offloaded\\n      bpf_prog_is_offloaded           check_cfg\\n      check_cfg                     + check_attach_btf_id\\n      ...                             ...\\n\\nThe following fields are set by check_attach_btf_id():\\n- env-\u003eops\\n- prog-\u003eaux-\u003eattach_btf_trace\\n- prog-\u003eaux-\u003eattach_func_name\\n- prog-\u003eaux-\u003eattach_func_proto\\n- prog-\u003eaux-\u003edst_trampoline\\n- prog-\u003eaux-\u003emod\\n- prog-\u003eaux-\u003esaved_dst_attach_type\\n- prog-\u003eaux-\u003esaved_dst_prog_type\\n- prog-\u003eexpected_attach_type\\n\\nNeither of these fields are used by resolve_pseudo_ldimm64() or\\nbpf_prog_offload_verifier_prep() (for netronome and netdevsim\\ndrivers), so the reordering is safe.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bpf: comprobar la propiedad changes_pkt_data para programas de extensi\u00f3n Al procesar llamadas a subprogramas globales, el verificador decide si invalidar todos los punteros de paquete en el estado actual dependiendo de la propiedad changes_pkt_data del subprograma global. Debido a esto, un programa de extensi\u00f3n que reemplaza un subprograma global debe ser compatible con la propiedad changes_pkt_data del subprograma que se est\u00e1 reemplazando. Esta confirmaci\u00f3n: - a\u00f1ade el indicador changes_pkt_data a struct bpf_prog_aux: - este indicador se establece en check_cfg() para el subprograma principal; - en jit_subprogs() para otros subprogramas; - modifica bpf_check_attach_btf_id() para comprobar el indicador changes_pkt_data; - mueve la llamada a check_attach_btf_id() despu\u00e9s de la llamada a check_cfg(), porque necesita que se configure el indicador changes_pkt_data: bpf_check: ... ... - check_attach_btf_id resolve_pseudo_ldimm64 resolve_pseudo_ldimm64 --\u0026gt; bpf_prog_is_offloaded bpf_prog_is_offloaded check_cfg check_cfg + check_attach_btf_id ... ... Los siguientes campos se configuran mediante check_attach_btf_id(): - env-\u0026gt;ops - prog-\u0026gt;aux-\u0026gt;attach_btf_trace - prog-\u0026gt;aux-\u0026gt;attach_func_name - prog-\u0026gt;aux-\u0026gt;attach_func_proto - prog-\u0026gt;aux-\u0026gt;dst_trampoline - prog-\u0026gt;aux-\u0026gt;mod - prog-\u0026gt;aux-\u0026gt;saved_dst_attach_type - prog-\u0026gt;aux-\u0026gt;saved_dst_prog_type - prog-\u0026gt;expected_attach_type Ninguno de estos campos es utilizado por resolve_pseudo_ldimm64() o bpf_prog_offload_verifier_prep() (para los controladores netronome y netdevsim), por lo que el reordenamiento es seguro.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/3846e2bea565ee1c5195dcc625fda9868fb0e3b3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/81f6d0530ba031b5f038a091619bf2ff29568852\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

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