GHSA-Q738-WCRR-X4XX

Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-05-27 15:33
VLAI
Details

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

landlock: Fix LOG_SUBDOMAINS_OFF inheritance across fork()

hook_cred_transfer() only copies the Landlock security blob when the source credential has a domain. This is inconsistent with landlock_restrict_self() which can set LOG_SUBDOMAINS_OFF on a credential without creating a domain (via the ruleset_fd=-1 path): the field is committed but not preserved across fork() because the child's prepare_creds() calls hook_cred_transfer() which skips the copy when domain is NULL.

This breaks the documented use case where a process mutes subdomain logs before forking sandboxed children: the children lose the muting and their domains produce unexpected audit records.

Fix this by unconditionally copying the Landlock credential blob.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-46057"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-27T14:17:25Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nlandlock: Fix LOG_SUBDOMAINS_OFF inheritance across fork()\n\nhook_cred_transfer() only copies the Landlock security blob when the\nsource credential has a domain.  This is inconsistent with\nlandlock_restrict_self() which can set LOG_SUBDOMAINS_OFF on a\ncredential without creating a domain (via the ruleset_fd=-1 path): the\nfield is committed but not preserved across fork() because the child\u0027s\nprepare_creds() calls hook_cred_transfer() which skips the copy when\ndomain is NULL.\n\nThis breaks the documented use case where a process mutes subdomain logs\nbefore forking sandboxed children: the children lose the muting and\ntheir domains produce unexpected audit records.\n\nFix this by unconditionally copying the Landlock credential blob.",
  "id": "GHSA-q738-wcrr-x4xx",
  "modified": "2026-05-27T15:33:22Z",
  "published": "2026-05-27T15:33:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46057"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1c513b8a00df13d231021e74ad92babb3fedf64a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2fcde49092aac55d5beef43fdd3633217672f7d1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/874c8f83826c95c62c21d9edfe9ef43e5c346724"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


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…