FKIE_CVE-2026-98626

Vulnerability from fkie_nvd - Published: 2026-10-18 16:17 - Updated: 2026-10-19 10:19
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Restrict CO-RE poisoning to relocatable instructions CO-RE relocation records can name any instruction offset. When a relocation cannot be resolved, bpf_core_patch_insn() currently poisons its target before checking whether that instruction is a valid relocation target. Malformed metadata can therefore replace jumps, calls, exits, register-source arithmetic, or non-immediate loads instead of failing at the relocation step. Handle poisoning only after the instruction has passed the same class and operand-form checks used for a resolved relocation. Route invalid forms through the existing diagnostic and return a hard error. Keep poisoning supported instructions, including both halves of a plain ldimm64, so an unresolved relocation in dead code remains valid. Extend bpf_core_poison_insn() to poison both halves of ldimm64, and return its status directly from each validated instruction case. This avoids routing the success path through a common label and leaves the helper free to report errors. The shared relocation code applies this restriction to both libbpf and in-kernel CO-RE.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "tools/lib/bpf/relo_core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a8c47e62d9aea2d47a09e06c1682c59c21b92449",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            },
            {
              "lessThan": "d3219c229d16900cef936adad28633c98946e432",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            },
            {
              "lessThan": "a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            },
            {
              "lessThan": "f2a24101e89dd0804e717da7c1bd6af513698aa2",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            },
            {
              "lessThan": "2d7d04357c41aa49a5ac658fcc207439f2ad6456",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            },
            {
              "lessThan": "8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            },
            {
              "lessThan": "394ae398337c5f87e567f6cd63b937fc2b2f6ddc",
              "status": "affected",
              "version": "d7a252708dbc950ca2064310217e8b9f85846e2f",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "tools/lib/bpf/relo_core.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": "5.15.*",
              "status": "unaffected",
              "version": "5.15.222",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.189",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.158",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.112",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.55",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Restrict CO-RE poisoning to relocatable instructions\n\nCO-RE relocation records can name any instruction offset. When a\nrelocation cannot be resolved, bpf_core_patch_insn() currently poisons its\ntarget before checking whether that instruction is a valid relocation\ntarget. Malformed metadata can therefore replace jumps, calls, exits,\nregister-source arithmetic, or non-immediate loads instead of failing at\nthe relocation step.\n\nHandle poisoning only after the instruction has passed the same class and\noperand-form checks used for a resolved relocation. Route invalid forms\nthrough the existing diagnostic and return a hard error. Keep poisoning\nsupported instructions, including both halves of a plain ldimm64, so an\nunresolved relocation in dead code remains valid.\n\nExtend bpf_core_poison_insn() to poison both halves of ldimm64, and return\nits status directly from each validated instruction case. This avoids\nrouting the success path through a common label and leaves the helper free\nto report errors.\n\nThe shared relocation code applies this restriction to both libbpf and\nin-kernel CO-RE."
    }
  ],
  "id": "CVE-2026-98626",
  "lastModified": "2026-10-19T10:19:26.820",
  "metrics": {},
  "published": "2026-10-18T16:17:15.640",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2d7d04357c41aa49a5ac658fcc207439f2ad6456"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/394ae398337c5f87e567f6cd63b937fc2b2f6ddc"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a8c47e62d9aea2d47a09e06c1682c59c21b92449"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/d3219c229d16900cef936adad28633c98946e432"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f2a24101e89dd0804e717da7c1bd6af513698aa2"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.