VDB

CVE-2024-42318

CVE-2024-42318 PUBLISHED CVSS 8.8 HIGH

landlock: Don't lose track of restrictions on cred_transfer

Reported by linux · Published August 17, 2024

In the Linux kernel, the following vulnerability has been resolved: landlock: Don't lose track of restrictions on cred_transfer When a process' cred struct is replaced, this _almost_ always invokes the cred_prepare LSM hook; but in one special case (when KEYCTL_SESSION_TO_PARENT updates the parent's credentials), the cred_transfer LSM hook is used instead. Landlock only implements the cred_prepare hook, not cred_transfer, so KEYCTL_SESSION_TO_PARENT causes all information on Landlock restrictions to be lost. This basically means that a process with the ability to use the fork() and keyctl() syscalls can get rid of all Landlock restrictions on itself. Fix it by adding a cred_transfer hook that does the same thing as the existing cred_prepare hook. (Implemented by having hook_cred_prepare() call hook_cred_transfer() so that the two functions are less likely to accidentally diverge in the future.)

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
linux_kernellinux6.10.3, 6.6.44, 6.1.103, 5.15.165

Risk scores

CVSS 3.1
8.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinux385975dca53eb41031d0cbd1de318eb1bc5d6bb9, 385975dca53eb41031d0cbd1de318eb1bc5d6bb9, 385975dca53eb41031d0cbd1de318eb1bc5d6bb9
LinuxLinux5.13, 0, 5.15.165
LinuxLinux385975dca53eb41031d0cbd1de318eb1bc5d6bb9, 5.15.165, 6.1.103
linuxlinux_kernel5.13, 5.13, 5.13

Timeline

  • Aug 17, 2024 CVE Published
  • Aug 18, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 4, 2024 Coalition ESS Score (7 in total, the first dated here)
  • Jan 6, 2026 Security Advisory (141 in total, the first dated here)
  • Mar 30, 2026 Distribution Patch (127 in total, the first dated here)
  • Aug 5, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-42318
vulnetix vdb fixes CVE-2024-42318

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-42318/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›