{"id":"EM-20261102-2037","url":"https://cyber.eventmonitor.net/incident/EM-20261102-2037/","type":"cve","title":"Linux Kernel Vulnerability (CVE-2026-99218)","subtitle":"CVE-2026-99218","subject":"CVE-2026-99218","status":"Developing","severity":"high","affected":[],"headline":null,"born":"2026-11-02T16:17:45.740Z","firstSignal":"2026-11-02T16:06:31.000Z","lastSignal":"2026-11-02T16:17:45.740Z","updated":"2026-11-04T14:43:58.877Z","revision":1,"life":[{"status":"Born","at":"2026-11-02T16:17:45.740Z","why":"second independent source: C6 NVD CVE API 2.0"},{"status":"Developing","at":"2026-11-02T16:17:45.740Z","why":"signals keep joining"}],"changeLog":[{"at":"2026-11-02T16:06:31.000Z","what":"First signal: C41 Red Hat Security Data"},{"at":"2026-11-02T16:17:45.740Z","what":"Born: second source, C6 NVD CVE API 2.0. Page EM-20261102-2037 created."},{"at":"2026-11-02T16:17:45.740Z","what":"Severity raised to High by C6"}],"stages":[{"name":"Disclosed","at":"2026-11-02T16:17:45.740Z","detail":"C6 NVD published"},{"name":"Scored","at":"2026-11-02T16:17:45.740Z","detail":"CVSS 7 · EPSS 0.1%"},{"name":"Exploited","at":null,"detail":"No exploitation reported"},{"name":"Advisories","at":null,"detail":"None yet"},{"name":"Vendor Response","at":"2026-11-02T16:06:31.000Z","detail":"C41 published"},{"name":"Resolved","at":null,"detail":"After 14 quiet days"}],"signals":[{"at":"2026-11-02T16:06:31.000Z","source":"C41","sourceName":"Red Hat Security Data","role":"Vendor","severity":2,"title":"Red Hat: CVE-2026-99218 (moderate)","text":"kernel: kernel: privilege escalation via use-after-free in coredump subsystem","url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-99218.json"},{"at":"2026-11-02T16:17:45.740Z","source":"C6","sourceName":"NVD CVE API 2.0","role":"Database","severity":3,"title":"CVE-2026-99218 (CVSS 7)","text":"In the Linux kernel, the following vulnerability has been resolved:\n\ncoredump: hold RCU while releasing parked threads\n\ncoredump_finish() releases the parked threads by clearing ->task in\ntheir core_thread entry and calling wake_up_process() on each of them.\nIt does that without holding a reference on the task and without being\ninside rcu.\n\nBut calling wake_up_process(task) without rcu here isn't safe. A parked\nthread doesn't need that wakeup to leave. A spurious wakeup or a\npreemption after the store is enough for the task to go away.\n\nSo if the coredump client is preempted between the store ","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99218"}],"crowd":[],"reference":{"nvd":{"published":"2026-11-02T16:17:45.740","score":7,"severity":"HIGH","desc":"In the Linux kernel, the following vulnerability has been resolved:\n\ncoredump: hold RCU while releasing parked threads\n\ncoredump_finish() releases the parked threads by clearing ->task in\ntheir core_thread entry and calling wake_up_process() on each of them.\nIt does that without holding a reference ","product":"","seen":1793803438877},"kev":null,"epss":{"epss":0.00122,"pct":0.01999,"at":1793803438877},"p0":false},"mergedInto":null,"publisher":"Event Monitor Cyber"}