39 matches found
DEBIAN-CVE-2026-68286
In the Linux kernel, the following vulnerability has been resolved: dropmonitor: perform u64stats updates under IRQ-disabled section In netdmpackettracekfreeskbhit and netdmhwtrappacketprobe, u64statsupdatebegin / u64statsinc / u64statsupdateend were called after...
UBUNTU-CVE-2026-68286
In the Linux kernel, the following vulnerability has been resolved: dropmonitor: perform u64stats updates under IRQ-disabled section In netdmpackettracekfreeskbhit and netdmhwtrappacketprobe, u64statsupdatebegin / u64statsinc / u64statsupdateend were called after...
CVE-2026-68286
In the Linux kernel, the following vulnerability has been resolved: dropmonitor: perform u64stats updates under IRQ-disabled section In netdmpackettracekfreeskbhit and netdmhwtrappacketprobe, u64statsupdatebegin / u64statsinc / u64statsupdateend were called after...
CVE-2026-68286 drop_monitor: perform u64_stats updates under IRQ-disabled section
In the Linux kernel, the following vulnerability has been resolved: dropmonitor: perform u64stats updates under IRQ-disabled section In netdmpackettracekfreeskbhit and netdmhwtrappacketprobe, u64statsupdatebegin / u64statsinc / u64statsupdateend were called after...
CVE-2026-68286
CVE-2026-68286 affects the Linux kernel’s drop_monitor code. The vulnerability arises because 64-bit per-CPU stats updates (u64_stats_update_begin/Inc/update_end) were performed after releasing drop_queue.lock (spin_unlock_irqrestore), i.e., after local IRQs had been re-enabled, in the functions ...
Linux Distros Unpatched Vulnerability : CVE-2026-68286
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - dropmonitor: perform u64stats updates under IRQ-disabled section In netdmpackettracekfreeskbhit and netdmhwtrappacketprobe, u64statsupdatebegin / u64statsinc /...
kernel: flex_proportions: make fprop_new_period() hardirq safe
A deadlock vulnerability was found in the Linux kernel's flexible proportions fprop code used for I/O writeback accounting. When a hardirq interrupts the seqcount write section in fpropnewperiod during softirq context, a reader in the hardirq handler can spin indefinitely waiting for the odd...
Linux Distros Unpatched Vulnerability : CVE-2026-64160
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - netfs: Fix potential for tearing in -remoteisize and -zeropoint Fix potential tearing in using -remoteisize and -zeropoint by copying isizeread and isizewrite a...
CVE-2026-64160
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential for tearing in -remoteisize and -zeropoint Fix potential tearing in using -remoteisize and -zeropoint by copying isizeread and isizewrite and using the same seqcount as for isize. We need to make sure that...
CVE-2026-64160 netfs: Fix potential for tearing in ->remote_i_size and ->zero_point
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential for tearing in -remoteisize and -zeropoint Fix potential tearing in using -remoteisize and -zeropoint by copying isizeread and isizewrite and using the same seqcount as for isize. We need to make sure that...
CVE-2026-64160
In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential for tearing in -remoteisize and -zeropoint Fix potential tearing in using -remoteisize and -zeropoint by copying isizeread and isizewrite and using the same seqcount as for isize. We need to make sure that...
CVE-2026-64160
CVE-2026-64160 involves a Linux kernel netfs issue where tearing could occur in remote_i_size and zero_point updates. The fix copies i_size_read() and i_size_write() and uses the same seqcount as i_size to prevent i_size_seqcount corruption, and requires netfslib and filesystems using it to hold ...
PT-2026-61477
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A potential for tearing exists when using remote i size and zero point. This occurs because these values were not being accessed using the same sequence count as i size. Tearing refers t...
Astra Linux – Vulnerability in Linux 5.10
In the Linux kernel, the following vulnerability has been resolved: mm/slab: Do not access current-memsallowedseq if !allowspin Lockdep reports a problem when the getfromanypartial function is called in an NMI context, because current-memsallowedseq is of type seqcountspinlockt, which is not...
SUSE CVE-2026-43285
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current-memsallowedseq if !allowspin Lockdep complains when getfromanypartial is called in an NMI context, because current-memsallowedseq is seqcountspinlockt and not NMI-safe:...
EUVD-2026-28555
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current-memsallowedseq if !allowspin Lockdep complains when getfromanypartial is called in an NMI context, because current-memsallowedseq is seqcountspinlockt and not NMI-safe:...
CVE-2026-43285
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current-memsallowedseq if !allowspin Lockdep complains when getfromanypartial is called in an NMI context, because current-memsallowedseq is seqcountspinlockt and not NMI-safe:...
UBUNTU-CVE-2026-43285
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current-memsallowedseq if !allowspin Lockdep complains when getfromanypartial is called in an NMI context, because current-memsallowedseq is seqcountspinlockt and not NMI-safe:...
CVE-2026-43285
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current-memsallowedseq if !allowspin Lockdep complains when getfromanypartial is called in an NMI context, because current-memsallowedseq is seqcountspinlockt and not NMI-safe:...
CVE-2026-43285 mm/slab: do not access current->mems_allowed_seq if !allow_spin
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current-memsallowedseq if !allowspin Lockdep complains when getfromanypartial is called in an NMI context, because current-memsallowedseq is seqcountspinlockt and not NMI-safe:...