GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-7P9J-GMGX-G4FV

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33
VLAI
Details

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

bpf: Tighten cgroup storage cookie checks for prog arrays

The fix in commit abad3d0bad72 ("bpf: Fix oob access in cgroup local storage") is still incomplete. The prog-array compatibility check treats a program with no cgroup storage as compatible with any stored storage cookie. This allows a storage-less program to bridge a tail call chain between an entry program and a storage-using callee even though cgroup local storage at runtime still follows the caller's context, that is, A -> B(no storage) -> C(storage) path.

Requiring exact cookie equality would break the legitimate case of a storage-less leaf program being tail called from a storage-using one. Instead, only accept a zero storage cookie if the program cannot perform tail calls itself. This keeps A -> B(no storage) working while rejecting the A -> B(no storage) -> C(storage) bridge.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-74305"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:30Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Tighten cgroup storage cookie checks for prog arrays\n\nThe fix in commit abad3d0bad72 (\"bpf: Fix oob access in cgroup local\nstorage\") is still incomplete. The prog-array compatibility check\ntreats a program with no cgroup storage as compatible with any stored\nstorage cookie. This allows a storage-less program to bridge a tail\ncall chain between an entry program and a storage-using callee even\nthough cgroup local storage at runtime still follows the caller\u0027s\ncontext, that is, A -\u003e B(no storage) -\u003e C(storage) path.\n\nRequiring exact cookie equality would break the legitimate case of a\nstorage-less leaf program being tail called from a storage-using one.\nInstead, only accept a zero storage cookie if the program cannot\nperform tail calls itself. This keeps A -\u003e B(no storage) working\nwhile rejecting the A -\u003e B(no storage) -\u003e C(storage) bridge.",
  "id": "GHSA-7p9j-gmgx-g4fv",
  "modified": "2026-08-17T06:33:37Z",
  "published": "2026-08-15T06:32:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74305"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/10627ddc0167aab5c1c390a10ef461e9937aba08"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1c762d28698483ce7c372091f34d86e4d4828652"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/46fbafe3d2d569d828e8d24a7dbe1659f63685cf"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/87177497cca90bf4fcfb759eb898560eb5b46a10"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9ca06849c4239aa2d580c54651f8588c51cb398b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cb22dc79528eb26a46d346c3118dbd6b14c70609"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/eb73056ce2a6f101ddd3bdba89af6b24ebffff85"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…