CVE-2026-89485

CVE-2026-89485 is a use-after-free vulnerability in the Linux kernel's lockd (NLM) subsystem. In nlm_traverse_files(), the current file is pinned across a mutex_unlock window, but the saved next pointer is not. A concurrent nlm_release_file() can free that next file, causing the iterator to deref...

CVE-2026-89485 lockd: pin next file across nlm_inspect_file lock-drop

In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlminspectfile lock-drop nlmtraversefiles pins the current file with fcount++ across a mutexunlock for nlminspectfile, but nothing pins the saved next pointer. A concurrent nlmreleasefile can kfree the...

EUVD-2026-76391

In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlminspectfile lock-drop nlmtraversefiles pins the current file with fcount++ across a mutexunlock for nlminspectfile, but nothing pins the saved next pointer. A concurrent nlmreleasefile can kfree the...

CVE-2026-89484 lockd: fix NULL dereference on lockowner allocation failure

In the Linux kernel, the following vulnerability has been resolved: lockd: fix NULL dereference on lockowner allocation failure nlmclntlocksinitprivate installs NLM file lock operations even when nlmclntfindlockowner fails to allocate a lockowner. nlmclntproc then returns -ENOMEM, but the VFS sti...

CVE-2026-89483

CVE-2026-89483 is an information disclosure flaw in the Linux kernel NVMe subsystem . When nvme_setup_discard() falls back to the per-controller ctrl->discard_page (allocated via alloc_page(GFP_KERNEL) without zeroing) under memory pressure, up to 4080 bytes of uninitialized kernel memory (inc...

CVE-2026-89483

In the Linux kernel, the following vulnerability has been resolved: nvme: zero the discard fallback page nvmesetupdiscard always maps sizeofstruct nvmedsmrange NVMEDSMMAXRANGES = 4096 bytes as the DSM payload however many ranges the command declares, because some devices ignore the 'Number of...

CVE-2026-89484

In the Linux kernel, the following vulnerability has been resolved: lockd: fix NULL dereference on lockowner allocation failure nlmclntlocksinitprivate installs NLM file lock operations even when nlmclntfindlockowner fails to allocate a lockowner. nlmclntproc then returns -ENOMEM, but the VFS sti...

CVE-2026-89484

CVE-2026-89484 is a NULL pointer dereference in the Linux kernel's lockd (Network Lock Manager) subsystem. The bug occurs when nlmclnt_find_lockowner() fails to allocate a lockowner, yet nlmclnt_locks_init_private() still installs NLM file lock operations. When the VFS subsequently tears down the...

EUVD-2026-76390

In the Linux kernel, the following vulnerability has been resolved: lockd: fix NULL dereference on lockowner allocation failure nlmclntlocksinitprivate installs NLM file lock operations even when nlmclntfindlockowner fails to allocate a lockowner. nlmclntproc then returns -ENOMEM, but the VFS sti...

EUVD-2026-76389

In the Linux kernel, the following vulnerability has been resolved: nvme: zero the discard fallback page nvmesetupdiscard always maps sizeofstruct nvmedsmrange NVMEDSMMAXRANGES = 4096 bytes as the DSM payload however many ranges the command declares, because some devices ignore the 'Number of...

CVE-2026-89484 lockd: fix NULL dereference on lockowner allocation failure

In the Linux kernel, the following vulnerability has been resolved: lockd: fix NULL dereference on lockowner allocation failure nlmclntlocksinitprivate installs NLM file lock operations even when nlmclntfindlockowner fails to allocate a lockowner. nlmclntproc then returns -ENOMEM, but the VFS sti...

CVE-2026-89483 nvme: zero the discard fallback page

In the Linux kernel, the following vulnerability has been resolved: nvme: zero the discard fallback page nvmesetupdiscard always maps sizeofstruct nvmedsmrange NVMEDSMMAXRANGES = 4096 bytes as the DSM payload however many ranges the command declares, because some devices ignore the 'Number of...

EUVD-2026-76388

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blkrqpayloadbytes alone Commit 25e5cb780e62 "nvme-tcp: fix possible crash in writezeroes processing" established that blkrqpayloadbytes must not be read without first checking...

CVE-2026-89482 nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blkrqpayloadbytes alone Commit 25e5cb780e62 "nvme-tcp: fix possible crash in writezeroes processing" established that blkrqpayloadbytes must not be read without first checking...

CVE-2026-89482 nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blkrqpayloadbytes alone Commit 25e5cb780e62 "nvme-tcp: fix possible crash in writezeroes processing" established that blkrqpayloadbytes must not be read without first checking...

CVE-2026-89482

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blkrqpayloadbytes alone Commit 25e5cb780e62 "nvme-tcp: fix possible crash in writezeroes processing" established that blkrqpayloadbytes must not be read without first checking...

CVE-2026-89482

CVE-2026-89482 is a wild-memory-access vulnerability in the Linux kernel's nvme-tcp module. The root cause is an incorrect receive-side gate: for REQ_OP_WRITE_ZEROES commands, blk_rq_payload_bytes() returns a non-zero value despite the absence of physical segments, so the setup phase leaves req-&...

EUVD-2026-76387

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix host memory disclosure on R2T for a read command nvmetcphandler2t does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it:...

CVE-2026-89481 nvme-tcp: fix host memory disclosure on R2T for a read command

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix host memory disclosure on R2T for a read command nvmetcphandler2t does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it:...

CVE-2026-89481

CVE-2026-89481 affects the Linux kernel's NVMe over TCP (nvme-tcp) component. The root cause is that nvme_tcp_handle_r2t() does not validate the direction of the request a Ready to Transfer (R2T) refers to. A malicious NVMe controller can send an R2T for a READ command; the host then sends the co...