Search
CVE Explorer
Search the full tracked CVE corpus across every vendor — by keyword, vendor, severity, CVSS band and publication date. Server-rendered; each filtered view has its own URL.
01
Filters
Submit to refine — state is held in the URL.
02
Results
83,150 matching · page 71/1663Each CVE id links to its NVD record.
| CVE | Severity | CVSS | Summary | Published |
|---|---|---|---|---|
| CVE-2026-99105(opens NVD record) | Unscored | — | In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix stall when a task enqueued with SCX_ENQ_LAST lands back on its CPU's local DSQ With SCX_OPS_ENQ_LAST, the last runnable task on a CPU is passed to ops.enqueue() instead of being kept running. Exiting tasks without SCX_OPS_ENQ_EXITING, migration disabled tasks without SCX_OPS_ENQ_MIGRATION_DISABLED and tasks on an offline rq skip ops.enqueue() and go straight to the local DSQ. This happens in put_prev_task_scx() after the pick has settled on idle, so nothing reschedules the CPU, which idles with the task queued until an unrelated wakeup lands on it or the watchdog fires. scx_mitosis, which sets SCX_OPS_ENQ_LAST without SCX_OPS_ENQ_EXITING, hit this during mass cgroup teardown: exiting tasks stuck in exit_mmap() for over 40 seconds. A task put on the local DSQ runs, as anywhere else. If the SCX_ENQ_LAST enqueue left the task on this CPU's local DSQ, set need_resched on the task being switched in, as proxy_resched_idle() does. resched_curr() would flag the task being put instead, and __schedule() clears that right after the pick. | Oct 28, 2026 |
| CVE-2026-99104(opens NVD record) | Unscored | — | In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor scx_bypass() claims bypass dispatch when the scheduler's depth goes from zero to one and releases it when the depth returns to zero, but propagates only the depth to the descendants, not the claim. A descendant that starts bypassing with its ancestor never claims, and one whose own bypass ends under the ancestor's keeps its claim, as its depth does not return to zero. A sub-scheduler enable whose bypass ends under a PM suspend thus leaks its claim: the parent keeps hosting bypass dispatch and the sub-scheduler's next bypass trips the WARN_ON_ONCE() on the claim. A sub-scheduler disable that starts under a PM suspend has no claim, so once the resume lifts the root's bypass its tasks sit on the parent's bypass DSQs with nobody consuming them. Claim for every descendant whose depth goes from zero to one in the propagation and release every scheduler in the subtree whose depth returned to zero once the tasks have moved out of the bypass DSQs. A parent that is bypassing itself when a descendant claims consumes only its own bypass DSQs, empty until it leaves bypass and becomes the host. | Oct 28, 2026 |
| CVE-2026-99103(opens NVD record) | Unscored | — | In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a use-after-free of an unbound worker_pool in node_activate_pending_pwq(): BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120 Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318 CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: 0x0 (flush-8:0) Call Trace: <TASK> dump_stack_lvl+0x53/0x70 print_report+0xce/0x610 kasan_report+0xce/0x100 _raw_spin_trylock+0x6d/0x120 pwq_dec_nr_in_flight+0x4b4/0xcb0 process_one_work+0x921/0x11a0 worker_thread+0x4d0/0xd20 kthread+0x2de/0x3c0 ret_from_fork+0x3aa/0x620 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 311: alloc_pwq+0x439/0xca0 apply_wqattrs_prepare+0x75e/0xd10 apply_workqueue_attrs_locked+0x44/0xa0 wq_nice_store+0x350/0x450 Freed by task 0: kfree+0x127/0x3b0 rcu_core+0x523/0x1780 handle_softirqs+0x1b3/0x610 Last potentially related work creation: put_unbound_pool+0x3f3/0x7d0 pwq_release_workfn+0x494/0x8e0 kthread_worker_fn+0x1ff/0x790 Canceling the last inactive work skips pwq_dec_nr_active(), so an empty pwq can remain on pending_pwqs when its refcnt reaches zero. pwq_release_workfn() currently puts the pool before removing that pwq. If this drops the last pool reference, the pool can be RCU-freed while the pwq remains reachable, and node_activate_pending_pwq() may trylock the freed pool->lock. Remove the pwq from pending_pwqs before putting the pool. | Oct 28, 2026 |
| CVE-2026-99102(opens NVD record) | Unscored | — | In the Linux kernel, the following vulnerability has been resolved: ntfs: take invalidate_lock in ntfs_setattr_size() ntfs_setattr_size() updates i_size and resizes the on-disk attribute without holding mapping->invalidate_lock. Page faults take the lock shared, so a fault racing the resize can resolve a VCN against the transient runlist state of ntfs_non_resident_attr_expand() and fail with a spurious SIGBUS, and can interleave with the size-change epilogue (truncate_pagecache(), i_size_write(), pagecache_isize_extended()). Take invalidate_lock exclusively around the whole resize after inode_dio_wait(), matching the fallocate path and other filesystems such as xfs, which wraps truncate in its mmaplock (= invalidate_lock). | Oct 28, 2026 |
| CVE-2026-99101(opens NVD record) | Unscored | — | In the Linux kernel, the following vulnerability has been resolved: ntfs: move attribute payload before shrinking its record ntfs_new_attr_flags() resizes the non-resident attribute record before moving its name and mapping pairs to their shorter-header offsets when compression or sparse state is cleared. Shrinking the record first moves the following attribute over the tail of the old record. The subsequent memmove() therefore copies bytes from that following attribute instead of the old mapping pairs. Re-enabling compression on an empty file persists those bytes as a malformed mapping pairs array, which ntfsck reports as a missing or invalid run length. Move the payload before shrinking the record, while retaining the existing resize-before-move ordering when growing it. | Oct 28, 2026 |
| CVE-2026-87880(opens NVD record) | Medium | 6.8 | Sensitive information disclosure due to missing SSL certificate verification affecting one component. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87879(opens NVD record) | Medium | 5.9 | Sensitive information disclosure due to improper token validation. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87878(opens NVD record) | Medium | 6.3 | Linux binaries have executable stack attribute enabled. The following products are affected: Acronis Cyber Protect 17 (Linux) before build 42587. | Oct 28, 2026 |
| CVE-2026-87103(opens NVD record) | High | 7.4 | Sensitive information disclosure and manipulation due to improper token validation. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87102(opens NVD record) | High | 7.4 | Sensitive information disclosure and manipulation due to improper token validation. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87101(opens NVD record) | Medium | 6.2 | Sensitive information disclosure due to improper token validation. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87100(opens NVD record) | Low | 3.6 | Protection mechanism failure due to missing binary hardening in Linux executables. The following products are affected: Acronis Cyber Protect 17 (Linux) before build 42587. | Oct 28, 2026 |
| CVE-2026-87099(opens NVD record) | Medium | 5.7 | Cross-site scripting (XSS) vulnerability due to improper input validation. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87098(opens NVD record) | Low | 3.1 | Sensitive information disclosure due to improper authorization. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-87097(opens NVD record) | Medium | 5.3 | Sensitive information disclosure due to insufficiently protected credentials. The following products are affected: Acronis Cyber Protect 17 (Linux, Windows) before build 42587. | Oct 28, 2026 |
| CVE-2026-86378(opens NVD record) | High | 8.8 | Dell PowerProtect Data Domain, Feature Release versions 7.7.1.0 through 8.8, LTS2024 release versions 7.13.1.0 through 7.13.1.80, LTS2025 release versions 8.3.1.0 through 8.3.1.40, LTS2026 release versions 8.6.1.0 through 8.6.1.20, contain a Stack-based Buffer Overflow vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access. | Oct 28, 2026 |
| CVE-2026-86377(opens NVD record) | High | 7.6 | Dell PowerProtect Data Domain, Feature Release versions 7.7.1.0 through 8.8, LTS2024 release versions 7.13.1.0 through 7.13.1.80, LTS2025 release versions 8.3.1.0 through 8.3.1.40, LTS2026 release versions 8.6.1.0 through 8.6.1.20, contain an Out-of-bounds Write vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Denial of service. | Oct 28, 2026 |
| CVE-2026-6064(opens NVD record) | High | 7.3 | Link following vulnerability in Data Shredder components in Norton Antivirus, Avast Antivirus, and AVG Internet Security prior to 26.5.10933 on Windows allows a local, low-privileged attacker to escalate privileges to SYSTEM. During a privileged shred operation, enabling arbitrary file/folder deletion that is leveraged to gain NT AUTHORITY\SYSTEM privelages. | Oct 28, 2026 |
| CVE-2026-117858(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117857(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117856(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117855(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117854(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117853(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117852(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117851(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117850(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117849(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117848(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117847(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117846(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117845(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117844(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117843(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117842(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117841(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117840(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117839(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117838(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117837(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117836(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117835(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117834(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117833(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117832(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117831(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117830(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117829(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117828(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |
| CVE-2026-117827(opens NVD record) | Unscored | — | Rejected reason: Reserved in error; never associated with a vulnerability. | Oct 28, 2026 |