{"vulnerability": "CVE-2024-42318", "sightings": [{"uuid": "90bf469b-3c87-4898-919a-4ef7e352233f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42318", "type": "seen", "source": "https://t.me/cvedetector/3398", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42318 - Linux Landlock Credential Escalation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42318 \nPublished : Aug. 17, 2024, 9:15 a.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nlandlock: Don't lose track of restrictions on cred_transfer  \n  \nWhen a process' cred struct is replaced, this _almost_ always invokes  \nthe cred_prepare LSM hook; but in one special case (when  \nKEYCTL_SESSION_TO_PARENT updates the parent's credentials), the  \ncred_transfer LSM hook is used instead.  Landlock only implements the  \ncred_prepare hook, not cred_transfer, so KEYCTL_SESSION_TO_PARENT causes  \nall information on Landlock restrictions to be lost.  \n  \nThis basically means that a process with the ability to use the fork()  \nand keyctl() syscalls can get rid of all Landlock restrictions on  \nitself.  \n  \nFix it by adding a cred_transfer hook that does the same thing as the  \nexisting cred_prepare hook. (Implemented by having hook_cred_prepare()  \ncall hook_cred_transfer() so that the two functions are less likely to  \naccidentally diverge in the future.) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T12:18:01.000000Z"}]}