LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46057: landlock: Fix LOG_SUBDOMAINS_OFF inheritance across fork()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-46057 is a Linux kernel Landlock bug where a setting that suppresses certain sandbox audit logs is not inherited after fork(). The main impact is unexpected audit logging from sandboxed child processes, not a documented privilege escalation or remote compromise. Business urgency is generally low unless audit volume, compliance workflows, or Landlock-based sandboxing are important to operations.

Executive priority

Low for most organizations. Prioritize sooner where Landlock-based sandboxing and audit log controls are operationally important, especially if unexpected audit volume affects monitoring, storage, or compliance processes.

Technical view

Landlock’s hook_cred_transfer() copied the security blob only when the source credential had a domain. landlock_restrict_self() can set LOG_SUBDOMAINS_OFF without creating a domain, so forked children lost that flag. The kernel fix unconditionally copies the Landlock credential blob, preserving LOG_SUBDOMAINS_OFF across fork().

Likely exposure

Exposure is limited to Linux systems using Landlock and relying on LOG_SUBDOMAINS_OFF before forking sandboxed children. Systems not using Landlock, or not depending on this logging control, are unlikely to see practical impact. The source metadata lists Linux as affected but provides no CVSS score.

Exploitation context

No CISA KEV entry or cited source indicates active exploitation. The described outcome is unexpected audit records from child domains. The provided sources do not describe code execution, privilege escalation, sandbox escape, or data theft.

Researcher notes

The public record has no CVSS, CWE, or exploit evidence. The affected-version data is limited and should be reconciled against kernel stable commits and downstream vendor advisories. The bug is a credential-state inheritance issue in Landlock logging behavior.

Mitigation direction

  • Track Linux kernel stable updates containing the referenced Landlock fix.
  • Apply your distribution’s patched kernel when available.
  • If patch status is unclear, check vendor advisories for CVE-2026-46057.
  • Review audit capacity if Landlock logging unexpectedly increases.

Validation and detection

  • Inventory Linux kernels on systems using Landlock sandboxing.
  • Confirm whether applications set LOG_SUBDOMAINS_OFF before fork().
  • Check distro kernel changelogs for the referenced Landlock fix.
  • Review audit logs for unexpected Landlock subdomain records after child process creation.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-46057 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxead9079f75696a028aea8860787770c80eddb8f9, ead9079f75696a028aea8860787770c80eddb8f9, ead9079f75696a028aea8860787770c80eddb8f9unaffected
LinuxLinux6.15, 0, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.