Vulnerability-Lookup

GHSA-P3GW-45VQ-6CWQ

Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31

Details

In the Linux kernel, the following vulnerability has been resolved:

bpf: Preserve packet pointer class displacement in regsafe()

regsafe() maps packet pointer IDs between states and checks that each current register range is a subset of the corresponding explored register range. It does not, however, preserve the displacement between registers that share a packet pointer ID.

This is unsound because packet range is shared by ID. A bounds check on one class member updates every member, and a later access can consume the range through another member. Commit 022ac0750883 ("bpf: use reg->var_off instead of reg->off for pointers") folded the fixed pointer offset into r64 and removed the old off equality check, so two individually narrower registers can prune even when their displacement has changed. The explored path can then license an out-of-bounds packet access on the pruned path.

Require matching range bases for packet pointers with an ID. Together with the existing ID mapping, this preserves the displacement between members of each packet-pointer class without adding per-ID state. Packet pointers without an ID remain unaffected.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-98627"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-18T16:17:15Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Preserve packet pointer class displacement in regsafe()\n\nregsafe() maps packet pointer IDs between states and checks that each\ncurrent register range is a subset of the corresponding explored\nregister range. It does not, however, preserve the displacement between\nregisters that share a packet pointer ID.\n\nThis is unsound because packet range is shared by ID. A bounds check on\none class member updates every member, and a later access can consume the\nrange through another member. Commit 022ac0750883 (\"bpf: use reg-\u003evar_off\ninstead of reg-\u003eoff for pointers\") folded the fixed pointer offset into\nr64 and removed the old off equality check, so two individually narrower\nregisters can prune even when their displacement has changed. The\nexplored path can then license an out-of-bounds packet access on the\npruned path.\n\nRequire matching range bases for packet pointers with an ID. Together\nwith the existing ID mapping, this preserves the displacement between\nmembers of each packet-pointer class without adding per-ID state.\nPacket pointers without an ID remain unaffected.",
  "id": "GHSA-p3gw-45vq-6cwq",
  "modified": "2026-10-18T18:31:56Z",
  "published": "2026-10-18T18:31:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98627"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/091b40845bd3cf96791171ca95113e9184ccb596"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fd16449a9b3b31a8f18944c2f0e29e4e218ca2cf"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-98627 (GCVE-0-2026-98627)

Vulnerability from cvelistv5 – Published: 2026-10-18 15:19 – Updated: 2026-10-19 09:22

Title

bpf: Preserve packet pointer class displacement in regsafe()

Summary

In the Linux kernel, the following vulnerability has been resolved: bpf: Preserve packet pointer class displacement in regsafe() regsafe() maps packet pointer IDs between states and checks that each current register range is a subset of the corresponding explored register range. It does not, however, preserve the displacement between registers that share a packet pointer ID. This is unsound because packet range is shared by ID. A bounds check on one class member updates every member, and a later access can consume the range through another member. Commit 022ac0750883 ("bpf: use reg->var_off instead of reg->off for pointers") folded the fixed pointer offset into r64 and removed the old off equality check, so two individually narrower registers can prune even when their displacement has changed. The explored path can then license an out-of-bounds packet access on the pruned path. Require matching range bases for packet pointers with an ID. Together with the existing ID mapping, this preserves the displacement between members of each packet-pointer class without adding per-ID state. Packet pointers without an ID remain unaffected.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6820 records in the last 180 days details

References

2 references

URL	Tags
https://git.kernel.org/stable/c/091b40845bd3cf967…
https://git.kernel.org/stable/c/fd16449a9b3b31a8f…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 022ac075088366b62e130da5e1b200bc93a47191 , < 091b40845bd3cf96791171ca95113e9184ccb596 (git) Affected: 022ac075088366b62e130da5e1b200bc93a47191 , < fd16449a9b3b31a8f18944c2f0e29e4e218ca2cf (git)
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (semver) Unaffected: 7.2.9 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/bpf/states.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "091b40845bd3cf96791171ca95113e9184ccb596",
              "status": "affected",
              "version": "022ac075088366b62e130da5e1b200bc93a47191",
              "versionType": "git"
            },
            {
              "lessThan": "fd16449a9b3b31a8f18944c2f0e29e4e218ca2cf",
              "status": "affected",
              "version": "022ac075088366b62e130da5e1b200bc93a47191",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/bpf/states.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.9",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Preserve packet pointer class displacement in regsafe()\n\nregsafe() maps packet pointer IDs between states and checks that each\ncurrent register range is a subset of the corresponding explored\nregister range. It does not, however, preserve the displacement between\nregisters that share a packet pointer ID.\n\nThis is unsound because packet range is shared by ID. A bounds check on\none class member updates every member, and a later access can consume the\nrange through another member. Commit 022ac0750883 (\"bpf: use reg-\u003evar_off\ninstead of reg-\u003eoff for pointers\") folded the fixed pointer offset into\nr64 and removed the old off equality check, so two individually narrower\nregisters can prune even when their displacement has changed. The\nexplored path can then license an out-of-bounds packet access on the\npruned path.\n\nRequire matching range bases for packet pointers with an ID. Together\nwith the existing ID mapping, this preserves the displacement between\nmembers of each packet-pointer class without adding per-ID state.\nPacket pointers without an ID remain unaffected."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T09:22:55.260Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/091b40845bd3cf96791171ca95113e9184ccb596"
        },
        {
          "url": "https://git.kernel.org/stable/c/fd16449a9b3b31a8f18944c2f0e29e4e218ca2cf"
        }
      ],
      "title": "bpf: Preserve packet pointer class displacement in regsafe()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98627",
    "datePublished": "2026-10-18T15:19:48.952Z",
    "dateReserved": "2026-09-25T10:25:14.361Z",
    "dateUpdated": "2026-10-19T09:22:55.260Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted