{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46057 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-46057 is a low-severity vulnerability in Linux kernel, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46057 and fix it if it is affected.\n\nWhat it is: CVE-2026-46057 is a low-severity vulnerability in Linux kernel, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46057 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46057/ (Markdown: https://insights.sbomify.com/CVE-2026-46057/index.md)","id":"CVE-2026-46057","markdown":"https://insights.sbomify.com/CVE-2026-46057/index.md","name":"CVE-2026-46057","record":{"aliases":["BELL-CVE-2026-46057","DEBIAN-CVE-2026-46057","GHSA-q738-wcrr-x4xx","UBUNTU-CVE-2026-46057"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A flaw in Linux kernel Landlock allows child processes to bypass log muting, potentially exposing sensitive audit records.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"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's\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"landlock: Fix LOG_SUBDOMAINS_OFF inheritance across fork()","id":"CVE-2026-46057","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"media: amphion: Fix race between m2m job_abort and device_run","id":"CVE-2026-46058"},"packages":[],"prev":{"headline":"Bluetooth: hci_event: fix potential UAF in SSP passkey handlers","id":"CVE-2026-46056"},"products":["Linux"],"published":"2026-05-27","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-06-14","vendors":["Linux"]},"summary":"A flaw in Linux kernel Landlock allows child processes to bypass log muting, potentially exposing sensitive audit records.","url":"https://insights.sbomify.com/CVE-2026-46057/"}