Important: kernel6.18

Issue Overview: In the Linux kernel, the following vulnerability has been resolved: libceph: fix two unsafe bare decodes in decodelockers CVE-2026-68082 In the Linux kernel, the following vulnerability has been resolved: libceph: bound pgtemp,upmap,upmapitems length to CEPHPGMAXSIZE CVE-2026-6815...

Linux Distros Unpatched Vulnerability : CVE-2026-93220

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against...

SUSE CVE-2026-93220

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

DEBIAN-CVE-2026-93220

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

CVE-2026-93220

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

UBUNTU-CVE-2026-93220

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

CVE-2026-93220

The Linux kernel contains a vulnerability in sched_ext where the kick_sync_wait_bal_cb() function incorrectly assumes it always executes on the request queue's (rq ) own CPU. Because the rq lock can be dropped while the callback is queued, it may be executed on a foreign CPU . This leads to compa...

CVE-2026-93220 sched_ext: Keep kick_sync waiting on the rq's own CPU

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

EUVD-2026-85949

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

CVE-2026-93220 sched_ext: Keep kick_sync waiting on the rq's own CPU

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

CVE-2026-93220

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

CVE-2026-93220: Undefined Security Weakness

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

CVE-2026-93220

In the Linux kernel, the following vulnerability has been resolved: schedext: Keep kicksync waiting on the rq's own CPU kicksyncwaitbalcb assumes it runs on the rq's CPU from the schedule tail: the snapshots it compares against live in that CPU's percpu area and the busy-wait runs with the rq loc...

SUSE CVE-2026-90432

In the Linux kernel, the following vulnerability has been resolved: schedext: Abort directly from the hardlockup handler scxhardlockup defers the abort to an irqwork because exit claiming used to take scxschedlock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe a...

Linux Distros Unpatched Vulnerability : CVE-2026-90432

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: schedext: Abort directly from the hardlockup handler scxhardlockup defers the abort to an...

DEBIAN-CVE-2026-90432

In the Linux kernel, the following vulnerability has been resolved: schedext: Abort directly from the hardlockup handler scxhardlockup defers the abort to an irqwork because exit claiming used to take scxschedlock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe a...

CVE-2026-90432

In the Linux kernel, the following vulnerability has been resolved: schedext: Abort directly from the hardlockup handler scxhardlockup defers the abort to an irqwork because exit claiming used to take scxschedlock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe a...

CVE-2026-90432

CVE-2026-90432 affects the Linux kernel 's sched_ext (scheduler extension) subsystem. The vulnerability is in the hardlockup handler (scx_hardlockup()), which deferred the abort to an irq_work—originally needed because exit claiming required scx_sched_lock and couldn't run from NMI. Now that clai...

CVE-2026-90432 sched_ext: Abort directly from the hardlockup handler

In the Linux kernel, the following vulnerability has been resolved: schedext: Abort directly from the hardlockup handler scxhardlockup defers the abort to an irqwork because exit claiming used to take scxschedlock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe a...

EUVD-2026-82093

In the Linux kernel, the following vulnerability has been resolved: schedext: Abort directly from the hardlockup handler scxhardlockup defers the abort to an irqwork because exit claiming used to take scxschedlock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe a...