🔴 Live Security Advisory & EPSS Exploit Radar

Zero-Day & Vulnerability Intelligence Hub

Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.

421k+ 🇪🇺 EUVD-Datenbank
0 🔴 Critical im Radar
0 ⚠️ CISA KEV
0 🔓 Aktiv ausgenutzt
8 🧪 PoC verfügbar
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
🔴 Criticals pro Monat (12 M) 2025-12: 426 Criticals, davon 9 KEV, Ø CVSS 9,6 dec 25 2026-01: 433 Criticals, davon 10 KEV, Ø CVSS 9,6 2026-02: 419 Criticals, davon 4 KEV, Ø CVSS 9,5 feb 26 2026-03: 652 Criticals, davon 6 KEV, Ø CVSS 9,5 2026-04: 578 Criticals, davon 5 KEV, Ø CVSS 9,5 apr 26 2026-05: 683 Criticals, davon 13 KEV, Ø CVSS 9,5 2026-06: 944 Criticals, davon 14 KEV, Ø CVSS 9,6 jun 26 2026-07: 1329 Criticals, davon 13 KEV, Ø CVSS 9,6 2026-08: 1830 Criticals, davon 11 KEV, Ø CVSS 9,5 aug 26 2026-09: 1551 Criticals, davon 17 KEV, Ø CVSS 9,5 2026-10: 1625 Criticals, davon 12 KEV, Ø CVSS 9,5 okt 26 2026-11: 399 Criticals, davon 2 KEV, Ø CVSS 9,5 Ø CVSS je Monat 10.869 Criticals · ▮ KEV-Anteil · ┄ Ø CVSS 9,5
🏢 Top-Vendor-Veröffentlichungen (6 M) Adobe Apache Software Foundation Apple Google IBM Linux Microsoft Oracle Corporation
● Adobe ● Apache Software Foundation ● Apple ● Google ● IBM ● Linux ● Microsoft ● Oracle Corporation
📈 EPSS-Verteilung (Messungen)
TierCVEsAnteilΔ 7 T
≥90 %7950,2 %+8
≥50 %3.5610,9 %+3
≥10 %13.1773,2 %+12
<10 %397.80995,8 %+1.738
415.342 CVEs mit EPSS-Score (FIRST.org) · Stand 22.11.2026 · Δ vs. 14.11.
📈 EPSS-Riser (7 Tage · Top 8)
Microsoft EPSS 81,9 % ↑ +78,8 % CVE-2026-50522 CVSS 9,8
Microsoft · CVE-2026-50522 | Deserialization of untru…
CVE-2026-50522 | Deserialization of untrusted data in Microsoft Office SharePoint allows an unauthorized attacker to execute code over a ne…
EPSS: 3,0 % → 81,9 % (+78,8 %) ⚠️ KEV 🧪 PoC
WSO2 EPSS 78,8 % ↑ +56,5 % CVE-2026-5430 CVSS 10,0
WSO2 · CVE-2026-5430 | The JWT authentication me…
CVE-2026-5430 | The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported.…
EPSS: 22,4 % → 78,8 % (+56,5 %) ⚠️ KEV 🧪 PoC
Mirasvit EPSS 82,3 % ↑ +56,2 % CVE-2026-45247 CVSS 9,3
Mirasvit · CVE-2026-45247 | Mirasvit Full Page Cache…
CVE-2026-45247 | Mirasvit Full Page Cache Warmer for Magento 2 before version 1.11.12 contains a PHP object injection vulnerability that al…
EPSS: 26,2 % → 82,3 % (+56,2 %) ⚠️ KEV 🧪 PoC
SolarWinds EPSS 87,3 % ↑ +39,3 % CVE-2026-28318 CVSS 7,5
SolarWinds · CVE-2026-28318 | SolarWinds Serv-U is sus…
CVE-2026-28318 | SolarWinds Serv-U is susceptible to specially crafted POST requests that crash the Serv-U service without authentication u…
EPSS: 48,0 % → 87,3 % (+39,3 %) ⚠️ KEV 🧪 PoC
Adobe EPSS 81,6 % ↑ +34,2 % CVE-2026-48356 CVSS 9,3
Adobe · CVE-2026-48356 | Adobe Commerce is affect…
CVE-2026-48356 | Adobe Commerce is affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitr…
EPSS: 47,5 % → 81,6 % (+34,2 %) ⚠️ KEV 🧪 PoC
kestra-io EPSS 20,4 % ↑ +18,3 % CVE-2026-49869 CVSS 10,0
kestra-io · CVE-2026-49869 | Kestra is an open-source…
CVE-2026-49869 | Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, AuthenticationFilter in Kestra …
EPSS: 2,1 % → 20,4 % (+18,3 %) ⚠️ KEV 🧪 PoC
Plex EPSS 19,8 % ↑ +18,0 % CVE-2026-96656 CVSS 8,6
Plex · CVE-2026-96656 | Plex Media Server before…
CVE-2026-96656 | Plex Media Server before 1.43.3.10861 allows an admin user to write arbitrary files that may be executed on load. The pref…
EPSS: 1,8 % → 19,8 % (+18,0 %) ⚠️ KEV 🧪 PoC
Google EPSS 99,9 % ↑ +17,3 % CVE-2026-111497 CVSS 9,2
Google · CVE-2026-111497 | A buffer overflow vulne…
CVE-2026-111497 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on a…
EPSS: 82,6 % → 99,9 % (+17,3 %) ⚠️ KEV 🧪 PoC
Frühindikator · FIRST.org
Datenquellen & Methodik: Primärquelle ist die EUVD der ENISA (laufender Datenbank-Sync, alle 15 Minuten), abgeglichen mit dem CISA-KEV-Katalog und der NVD — Detail-Dossiers reichern fehlende Felder live per NVD an — mit Fallback auf CIRCL vulnerability-lookup (EU/Non-Profit, aggregiert CVE-, GitHub- und OSV-Advisories). Der CISA-KEV-Katalog (Known Exploited Vulnerabilities, ~1.700 aktiv ausgenutzte Schwachstellen) wird bei jedem Sync vollständig neu geladen und kreuzreferenziert — filterbar über die KEV-Pille. CVSS 3.1 wird nach Ampel-Logik aus Verteidigersicht dekodiert; EPSS bezeichnet die 30-Tage-Exploit-Wahrscheinlichkeit (FIRST.org).
🇪🇺 ENISA EUVD 🇺🇸 NVD ⚠️ CISA KEV ⚡ EPSS
🛡️ Ethisch gebruik: Alle CVE- en PoC-gegevens zijn uitsluitend bedoeld voor defensieve beveiliging, patchverificatie en geautoriseerde tests (Responsible Disclosure). Ethiek- & Disclosure-richtlijn · Voorwaarden § 6a (v2026.11)
Ökosystem & Hersteller Bedrohungs-Matrix:
⚙️ Geavanceerde onderzoeksfilters (Lifecycle, Scores, EPSS, Exploit, Sortering, Dynamiek, Bron, CWE)
84 resultaten (60 van 84 resultaten)
Weergave “🟠 High (7.0+) · Product: linux” resetten ✕
84 Schwachstellen
J/↓ Nächste K/↑ Vorherige Enter/O Dossier öffnen C CVE kopieren V Kacheln ↔ Liste / Suche G Nach oben Esc Fokus/Filter löschen
7.1 HIGH
EPSS 0.2%
CVE-2026-99430 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-99430 | In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix chunk number of the first chunk in a local quota file Mounting a crafted OCFS2 image can corrupt kernel memory. When the local quota file header of such an image claims zero chunks, the first quota entry allocated during the mount gets a chunk number taken from a kernel pointer, and releasing that entry clears a bit far outside the chunk bitmap. The write will corrupt the data

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix chunk number of the first chunk in a local quota file Mounting a crafted OCFS2 image can corrupt kernel memory. When the local quota file header of such an im

7.8 HIGH
EPSS 0.2%
CVE-2026-99429 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99429 | In the Linux kernel, the following vulnerability has been resolved: ocfs2: pin refcount trees before dropping the lookup lock A refcount tree returned to ocfs2_lock_refcount_tree() must stay alive until that caller releases its operation reference. However, ocfs2_get_refcount_tree() returns the cached pointer after dropping osb_lock, and the caller only takes its kref afterwards. The registry reference does not protect this gap from concurrent removal. Thi

In the Linux kernel, the following vulnerability has been resolved: ocfs2: pin refcount trees before dropping the lookup lock A refcount tree returned to ocfs2_lock_refcount_tree() must stay alive until that caller releases its operation

7.8 HIGH
EPSS 0.2%
CVE-2026-99425 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99425 | In the Linux kernel, the following vulnerability has been resolved: ovl: hold a reference on the parent in readdir Listing a directory on an overlay uses a freed dentry and crashes the kernel when a lookup moves the directory at the same time. Code that can sleep may only use d_parent without a reference while something stops a move of the dentry. ovl_iterate_real(), ovl_need_adjust_d_ino() and ovl_cache_update() use the d_parent of the listed directory an

In the Linux kernel, the following vulnerability has been resolved: ovl: hold a reference on the parent in readdir Listing a directory on an overlay uses a freed dentry and crashes the kernel when a lookup moves the directory at the same

7.8 HIGH
EPSS 0.2%
CVE-2026-99424 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99424 | In the Linux kernel, the following vulnerability has been resolved: ovl: set OVL_WHITEOUTS before publishing the upper dir Listing a directory while it is copied up causes a use-after-free of the readdir cache. A merge directory must never be iterated as a real upper directory: that mode frees the cache in OVL_I(inode)->cache without looking at its refcount, while files opened in merged mode still use it. ovl_copy_up_workdir() publishes the upper dentry be

In the Linux kernel, the following vulnerability has been resolved: ovl: set OVL_WHITEOUTS before publishing the upper dir Listing a directory while it is copied up causes a use-after-free of the readdir cache. A merge directory must nev

7.8 HIGH
EPSS 0.2%
CVE-2026-99422 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99422 | In the Linux kernel, the following vulnerability has been resolved: ovl: use the pinned upper dir in ovl_fix_origin() Renames made directly on the upper filesystem during a lookup crash the kernel. A dentry that is passed to vfs_setxattr() must be pinned. ovl_fix_origin() passes upper->d_parent to ovl_set_impure() without a reference, and the lookup holds no lock of the upper directory. A rename on the upper filesystem changes d_parent, and only the child

In the Linux kernel, the following vulnerability has been resolved: ovl: use the pinned upper dir in ovl_fix_origin() Renames made directly on the upper filesystem during a lookup crash the kernel. A dentry that is passed to vfs_setxattr

7.0 HIGH
EPSS 0.2%
CVE-2026-99401 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99401 | In the Linux kernel, the following vulnerability has been resolved: rtnetlink: wait for RCU readers in rtnl_link_unregister() rtnl_link_ops_get() finds ops on link_ops under rcu_read_lock() and only then takes ops->srcu. rtnl_link_unregister() unlinks ops, then calls synchronize_srcu() and cleanup_srcu_struct() without first waiting for RCU readers. A reader that found ops before list_del_rcu() and has not yet taken ops->srcu is not waited for. Such a read

In the Linux kernel, the following vulnerability has been resolved: rtnetlink: wait for RCU readers in rtnl_link_unregister() rtnl_link_ops_get() finds ops on link_ops under rcu_read_lock() and only then takes ops->srcu. rtnl_link_unregis

7.8 HIGH
EPSS 0.2%
CVE-2026-99400 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-99400 | In the Linux kernel, the following vulnerability has been resolved: xfs: reject out-of-range attribute value lengths in xfs_attr_copy_value xfs_attr_copy_value() takes the value length as a signed int and, for a remote xattr, is handed args->rmtvaluelen. That field is filled from the on-disk __be32 xfs_attr_leaf_name_remote.valuelen in xfs_attr3_leaf_getvalue(), so a crafted length such as 0x80000000 is stored into the signed rmtvaluelen as a negative numb

In the Linux kernel, the following vulnerability has been resolved: xfs: reject out-of-range attribute value lengths in xfs_attr_copy_value xfs_attr_copy_value() takes the value length as a signed int and, for a remote xattr, is handed ar

7.8 HIGH
EPSS 0.2%
CVE-2026-99399 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-99399 | In the Linux kernel, the following vulnerability has been resolved: xfs: reject remote xattr entries with an out-of-range value length xfs_attr3_leaf_verify_entry() validates a remote attribute entry's name but never bounds its on-disk value length (xfs_attr_leaf_name_remote. valuelen, a __be32). A crafted leaf with valuelen = 0x80000000 passes the verifier and the CRC. That length is later assigned into the signed int args->rmtvaluelen (xfs_attr3_leaf_get

In the Linux kernel, the following vulnerability has been resolved: xfs: reject remote xattr entries with an out-of-range value length xfs_attr3_leaf_verify_entry() validates a remote attribute entry's name but never bounds its on-disk va

7.8 HIGH
EPSS 0.2%
CVE-2026-99395 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-99395 | In the Linux kernel, the following vulnerability has been resolved: xfs: bound inode fork length against the fork size during log recovery xlog_recover_inode_commit_pass2() copies an inode log item's data/attr fork region into the inode buffer using the on-log region length without bounding it against the fork capacity, e.g.: len = item->ri_buf[2].iov_len; memcpy(XFS_DFORK_DPTR(dip), src, len); The only guard is an ASSERT, which is a no-op on production

In the Linux kernel, the following vulnerability has been resolved: xfs: bound inode fork length against the fork size during log recovery xlog_recover_inode_commit_pass2() copies an inode log item's data/attr fork region into the inode b

7.5 HIGH
EPSS 0.2%
CVE-2026-99389 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-99389 | In the Linux kernel, the following vulnerability has been resolved: smb: server: size directory name conversion buffer correctly A 2048-byte ASCII directory name needs 4098 bytes when converted to UTF-16, including the terminator. ksmbd_convert_dir_info_name() caps its allocation at PATH_MAX and writes past the end of that buffer. Allocate space for one UTF-16 code unit per input byte plus the terminator. Use kmalloc_array() to check the size calculation.

In the Linux kernel, the following vulnerability has been resolved: smb: server: size directory name conversion buffer correctly A 2048-byte ASCII directory name needs 4098 bytes when converted to UTF-16, including the terminator. ksmbd_c

8.8 HIGH
EPSS 0.2%
CVE-2026-99388 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-99388 | In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: fix buffer length underflow in RDMA transfers When a remote buffer descriptor is larger than the remaining local buffer, smbdirect_connection_rdma_xmit() clamps its length and sets buf_len to zero. The common accounting code then subtracts the clamped length from buf_len, causing it to underflow. If another descriptor follows, the loop processes it with a wrapped remaining l

In the Linux kernel, the following vulnerability has been resolved: smb: smbdirect: fix buffer length underflow in RDMA transfers When a remote buffer descriptor is larger than the remaining local buffer, smbdirect_connection_rdma_xmit()

7.5 HIGH
EPSS 0.2%
CVE-2026-99386 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99386 | In the Linux kernel, the following vulnerability has been resolved: smb: client: don't resurrect an exiting tcon from cached dir workers cfids_laundromat_worker() bumps tcon->tc_count for every expired open cfid and queues cached_dir_offload_close() without checking whether the tcon is already being torn down. Racing with the final cifs_put_tcon(), the tcon comes back from zero and gets torn down twice: T1 T2 cifs_put_

In the Linux kernel, the following vulnerability has been resolved: smb: client: don't resurrect an exiting tcon from cached dir workers cfids_laundromat_worker() bumps tcon->tc_count for every expired open cfid and queues cached_dir_offl

7.5 HIGH
EPSS 0.2%
CVE-2026-99383 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99383 | In the Linux kernel, the following vulnerability has been resolved: smb: client: reclaim credits for decrypted reads with no matching mid When a decrypted SMB2 READ response carries a MessageId that matches no outstanding request, both the inline receive_encrypted_read() and the offloaded smb2_decrypt_offload() paths drop the frame without accounting the credits the server granted in it. The plaintext unknown-frame path in cifs_demultiplex_thread() already

In the Linux kernel, the following vulnerability has been resolved: smb: client: reclaim credits for decrypted reads with no matching mid When a decrypted SMB2 READ response carries a MessageId that matches no outstanding request, both th

8.1 HIGH
EPSS 0.2%
CVE-2026-99380 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99380 | In the Linux kernel, the following vulnerability has been resolved: smb: client: validate NT transaction response layout and offsets validate_ntransact() assumes that the response uses the fixed 18-word NT transaction layout. A different WordCount makes get_bcc() locate the byte count at a different offset from pSMBr->ByteCount, allowing the subsequent bounds checks to use inconsistent response boundaries. The function also turns the 32-bit ParameterOffset

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate NT transaction response layout and offsets validate_ntransact() assumes that the response uses the fixed 18-word NT transaction layout. A different

7.3 HIGH
EPSS 0.2%
CVE-2026-99379 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-99379 | In the Linux kernel, the following vulnerability has been resolved: smb: client: validate SMB1 EA list bounds before parsing CIFSSMBQAllEAs() checks the server-provided EA list length by adding it to the response pointer. On 32-bit systems, a positive length can wrap the pointer and pass the comparison. The parser then walks outside the received response while reading the next FEA header. A response with a list length of 0x40000000 reproduces this as a nat

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate SMB1 EA list bounds before parsing CIFSSMBQAllEAs() checks the server-provided EA list length by adding it to the response pointer. On 32-bit system

8.1 HIGH
EPSS 0.2%
CVE-2026-99355 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99355 | In the Linux kernel, the following vulnerability has been resolved: SUNRPC: fix oversized GSS proxy token copy gss_read_proxy_verf() allocates one page per token chunk, but it copies the entire linear head of an RPC request into in_token->pages[0]. A UDP datagram can leave more than PAGE_SIZE bytes in the linear head, so a large RPCSEC_GSS INIT token overwrites following pages. Copy the linear head in page-sized chunks before switching to the request page

In the Linux kernel, the following vulnerability has been resolved: SUNRPC: fix oversized GSS proxy token copy gss_read_proxy_verf() allocates one page per token chunk, but it copies the entire linear head of an RPC request into in_token-

8.8 HIGH
EPSS 0.2%
CVE-2026-99346 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99346 | In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch When the pCPU where the VMCB was most recently used is switched, reset the ASID generation in both VMCBs, triggering new ASID allocation for the immediate VMRUN as well as the next VMRUN on the other VMCB. The ASID is shared between vmcb01 and vmcb02, and gets flushed on every nested transition. However, since pCPU tracking

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Trigger new ASID allocation in both VMCBs on pCPU switch When the pCPU where the VMCB was most recently used is switched, reset the ASID generation in both VMCB

7.8 HIGH
EPSS 0.2%
CVE-2026-99345 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99345 | In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0 Reject KVM_SET_NESTED_STATE if the incoming L1 host state has what is effectively an impossible EFER combination of LMA=1 but LME=0, i.e. if the state says long mode is active but not enabled. Unlike VMX, SVM doesn't have an explicit consistent check for the illegal combination; presumably hardware simply ignores EFE

In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Reject KVM_SET_NESTED_STATE if L1 has EFER.LMA=1 && EFER.LME=0 Reject KVM_SET_NESTED_STATE if the incoming L1 host state has what is effectively an impossible

7.1 HIGH
EPSS 0.2%
CVE-2026-99343 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99343 | In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Bug the VM if KVM attempts to walk more levels than the MMU has Extend the "EFER.LMA && !CR4.PAE" check, which exists largely to guard against KVM configuring a paging32 MMU with more than 2 levels of paging, with a very explicit check for exactly that: that KVM isn't trying to walk more levels of paging than the MMU template provides. I.e. harden KVM against all bugs that wo

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Bug the VM if KVM attempts to walk more levels than the MMU has Extend the "EFER.LMA && !CR4.PAE" check, which exists largely to guard against KVM configuri

7.8 HIGH
EPSS 0.2%
CVE-2026-99340 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99340 | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Take SRCU in kvm_zap_gfn_range() kvm_zap_gfn_range() walks memslots and rmaps and may drop mmu_lock to reschedule. Callers that do not already hold kvm->srcu (or slots_lock) can race with memslot deletion: synchronize_srcu_expedited() does not wait, kvm_free_memslot() frees the old slot and its rmap, and the zap resumes on freed memory. The VFIO noncoherent-DMA path hits this by

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Take SRCU in kvm_zap_gfn_range() kvm_zap_gfn_range() walks memslots and rmaps and may drop mmu_lock to reschedule. Callers that do not already hold kvm->srcu (o

7.0 HIGH
EPSS 0.2%
CVE-2026-99336 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99336 | In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: take the invalidate lock when unbinding a dying file kvm_gmem_unbind() takes mapping->invalidate_lock only if the get_file_active() succeeds. When the guest_memfd file is dying, its reference count is already zero so get_file_active fails and the binding is removed without holding the invalidate lock. kvm_gmem_invalidate_{start,end}() checks f->bindings independently to d

In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: take the invalidate lock when unbinding a dying file kvm_gmem_unbind() takes mapping->invalidate_lock only if the get_file_active() succeeds. When the g

8.8 HIGH
EPSS 0.2%
CVE-2026-99322 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-99322 | In the Linux kernel, the following vulnerability has been resolved: ksmbd: rebind completed CREATE replays without draining the old channel A completed DurableHandleReqV2 CREATE can be replayed through another channel while its original channel is exiting. The existing replay path returns the open but leaves its connection and oplock references pointing at the old channel. Its open count also stays on that channel, and a later CLOSE through the surviving ch

In the Linux kernel, the following vulnerability has been resolved: ksmbd: rebind completed CREATE replays without draining the old channel A completed DurableHandleReqV2 CREATE can be replayed through another channel while its original c

8.8 HIGH
EPSS 0.4%
CVE-2026-99313 🌐 Adjacent Network 🔓 Keine Authentifizierung nötig

CVE-2026-99313 | In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: fix race condition when accessing stale stack pointer The driver uses hidpp->send_receive_buf to point to a stack-allocated buffer in the synchronous command path (__do_hidpp_send_message_sync). However, this pointer is not cleared when the function returns. If an event is processed (e.g. by a different thread) while the send_mutex is held by a new command, but before

In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: fix race condition when accessing stale stack pointer The driver uses hidpp->send_receive_buf to point to a stack-allocated buffer in the synchronous

🛡️ 41 🔬 28
7.8 HIGH
EPSS 0.4%
CVE-2026-119846 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-119846 | Out-of-bounds read in Windows Subsystem for Linux allows an authorized attacker to elevate privileges locally.

Out-of-bounds read in Windows Subsystem for Linux allows an authorized attacker to elevate privileges locally.

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.4%
CVE-2026-119834 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-119834 | Heap-based buffer overflow in Windows Subsystem for Linux allows an authorized attacker to elevate privileges locally.

Heap-based buffer overflow in Windows Subsystem for Linux allows an authorized attacker to elevate privileges locally.

🛡️ 32 🔬 18
7.5 HIGH
EPSS 0.6%
CVE-2026-99288 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99288 | In the Linux kernel, the following vulnerability has been resolved: inet: reject unhashed sockets during established lookups TCP established ehash lookups are lockless. The socket caches involved use SLAB_TYPESAFE_BY_RCU, so memory can be reused before an RCU reader that retained its old address has finished. After a tuple match, __inet_lookup_established() and __inet6_lookup_established() acquire a reference and repeat the tuple check. They do not check w

In the Linux kernel, the following vulnerability has been resolved: inet: reject unhashed sockets during established lookups TCP established ehash lookups are lockless. The socket caches involved use SLAB_TYPESAFE_BY_RCU, so memory can be

🛡️ 41 🔬 36
7.5 HIGH
EPSS 0.2%
CVE-2026-104657 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-104657 | Missing integrity verification in the Progress Software Fiddler Download and Setup Skill on Linux, macOS, and Windows which allows an attacker to compromise or influence a release component and execute attacker-controlled code when a user runs the skill. On macOS, the skill stages the package at a predictable path and installs it with administrator privileges, which may allow code execution with root privileges after user approval. A local process may also r

Missing integrity verification in the Progress Software Fiddler Download and Setup Skill on Linux, macOS, and Windows which allows an attacker to compromise or influence a release component and execute attacker-controlled code when a user r

🛡️ 36 🔬 24
8.1 HIGH
EPSS 18.9%
CVE-2026-123158 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-123158 | sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass (related to misinterpretation of whether a string is intended to be a password hash). For some configurations of accounts, any password between 256 and 1024 characters succeeds. An example of a platform using musl libc without PAM is Alpine Linux.

sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass (related to misinterpretation of whether a string is intended to be a password hash). For some configuration

🛡️ 63 🔬 66
7.7 HIGH
EPSS 0.9%
CVE-2026-109518 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-109518 | On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the client into installing an attacker-controlled unverified package and achieve remote code execution with root privileges. The vulnerability is caused by the reuse of hard links and requires the client to follow redirects

On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the

🛡️ 52 🔬 49
8.3 HIGH
EPSS 0.2%
CVE-2026-92704 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-92704 | SharpEmu is an experimental PlayStation 5 emulator for Windows and Linux. In version 0.0.3-release.3 and earlier, the repository-provided debugger frontend tooling is vulnerable while running. This tooling is not included in the release archives. The frontend exposes an HTTP API on 127.0.0.1:8765 without authentication or CSRF token. Its  do_POST  handler in  tools/SharpEmu.DebuggerFrontend/debugger_frontend.py  does not validate the Origin, Referer, Sec-Fetc

SharpEmu is an experimental PlayStation 5 emulator for Windows and Linux. In version 0.0.3-release.3 and earlier, the repository-provided debugger frontend tooling is vulnerable while running. This tooling is not included in the release arc

🛡️ 54 🔬 49
7.8 HIGH
EPSS 0.6%
CVE-2026-95725 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-95725 | A command injection vulnerability exists in the VIA client for Linux. Successful exploitation could allow a low-privileged local attacker to execute arbitrary commands with elevated privileges on the affected system.

A command injection vulnerability exists in the VIA client for Linux. Successful exploitation could allow a low-privileged local attacker to execute arbitrary commands with elevated privileges on the affected system.

🛡️ 32 🔬 18
8.8 HIGH
EPSS 0.7%
CVE-2026-63395 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-63395 | isomorphic-git is a pure JavaScript implementation of Git for Node.js and browsers. Prior to 1.38.6, isomorphic-git's git.checkout writes new child paths through symlinked leading directory components without checking them. A malicious repository can first place a directory symlink and later replace the tree state with a child file beneath that path; the usual trigger is a clone followed by a later pull, while a single clone can trigger the issue when a symli

isomorphic-git is a pure JavaScript implementation of Git for Node.js and browsers. Prior to 1.38.6, isomorphic-git's git.checkout writes new child paths through symlinked leading directory components without checking them. A malicious repo

🛡️ 56 🔬 49
8.1 HIGH
EPSS 0.4%
CVE-2026-99270 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99270 | In the Linux kernel, the following vulnerability has been resolved: tcp: Fix potential UAF in reqsk_timer_handler(). When TCP socket migration fails at inet_ehash_insert() in reqsk_timer_handler(), we jump to the no_ownership: label and free the new reqsk immediately with __reqsk_free(). Thus, we must stop the new reqsk's timer before jumping to the label, but the timer might be missed since the cited commit, resulting in UAF. As we are in the original re

In the Linux kernel, the following vulnerability has been resolved: tcp: Fix potential UAF in reqsk_timer_handler(). When TCP socket migration fails at inet_ehash_insert() in reqsk_timer_handler(), we jump to the no_ownership: label and f

🛡️ 43 🔬 36
7.8 HIGH
EPSS 0.1%
CVE-2026-99269 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99269 | In the Linux kernel, the following vulnerability has been resolved: sched_ext: Wait for SCX_OPSS_DISPATCHING before moving tasks off DSQs A task can be found on a non-local DSQ while the CPU which dispatched it is still running ops.dequeue() and hasn't cleared SCX_OPSS_DISPATCHING. The DSQ consume and move paths don't wait for the dispatch to finish and can operate on the task concurrently with the dispatcher. Call scx_wait_dispatching() in scx_move_local_

In the Linux kernel, the following vulnerability has been resolved: sched_ext: Wait for SCX_OPSS_DISPATCHING before moving tasks off DSQs A task can be found on a non-local DSQ while the CPU which dispatched it is still running ops.dequeu

🛡️ 32 🔬 18
8.1 HIGH
EPSS 0.4%
CVE-2026-99246 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99246 | In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock. This permits bearer teardown to free a link while the trace callback is dumping it: CPU 0 CPU 1 trace_tipc_node_reset_li

In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node's link entries. Unlike the other node even

🛡️ 43 🔬 36
7.8 HIGH
EPSS 0.1%
CVE-2026-99239 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99239 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn l2cap_chan may be linked to l2cap_conn at most once. This is assumed in several places, eg l2cap_chan_del cleanup. There is a TOCTOU race where the invariant is violated: [Task 1] [Task 2] l2cap_chan_connect l2cap_sock_bind l2cap_chan_lock lock_sock

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn l2cap_chan may be linked to l2cap_conn at most once. This is assumed in several places, eg l2cap_chan_d

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99238 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99238 | In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when updating modules in persistent instances trace_module_record() walks ftrace_trace_arrays from the module notifier without trace_types_lock. A concurrent rmdir of an instance removes it from the list and frees it under that lock, so a module load or unload can walk into a freed trace_array.

In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when updating modules in persistent instances trace_module_record() walks ftrace_trace_arrays from the module notifier without trace_types_

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99237 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99237 | In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when resetting last boot data from readers update_last_data_if_empty() is called from tracing_open() with O_TRUNC, tracing_read_pipe() and tracing_buffers_read() without trace_types_lock. Two readers can both pass the LAST_BOOT test and free module_delta twice, and a module notifier can update module_delta while it is being freed. Take trace_types_lock in tho

In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when resetting last boot data from readers update_last_data_if_empty() is called from tracing_open() with O_TRUNC, tracing_read_pipe() and

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99236 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99236 | In the Linux kernel, the following vulnerability has been resolved: tracing: Reject incomplete event filter expressions A non-empty expression normally finishes in predicate_parse()'s inner loop, which resolves the pending logical operators before jumping to finalization. If the input ends after an operator, possibly followed by unary '!' tokens, the outer loop instead falls through with unresolved operator state. For example, "common_pid == 1 || common_pi

In the Linux kernel, the following vulnerability has been resolved: tracing: Reject incomplete event filter expressions A non-empty expression normally finishes in predicate_parse()'s inner loop, which resolves the pending logical operato

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99235 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99235 | In the Linux kernel, the following vulnerability has been resolved: tracing: Save the event file instead of the compatible histogram create_field_var_hist() creates a histogram on the matched event to supply a field variable, and records it on the target so it can be torn down later: hist_data = find_compatible_hist(target_hist_data, file); ... /* Save the compatible histogram information */ var_hist->hist_data = hist_data; hist_data is not the histog

In the Linux kernel, the following vulnerability has been resolved: tracing: Save the event file instead of the compatible histogram create_field_var_hist() creates a histogram on the matched event to supply a field variable, and records

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99233 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99233 | In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Verify event_call identity when updating synth_event refcount In event_hist_trigger_parse() and hist_unreg_all(), the histogram registration and unregistration paths look up find_synth_event() using trace_event_name(file->event_call) and adjust se->ref if a match is found. Because find_synth_event() only compares the event basename, registering or removing a histogram o

In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Verify event_call identity when updating synth_event refcount In event_hist_trigger_parse() and hist_unreg_all(), the histogram registration and unreg

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99231 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99231 | In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: own the request before clearing ->head io_waitid_remove_wq() only takes the wait queue lock if ->head is set. io_waitid_wait() clears ->head first thing, before it tries to become the owner of the request by bumping ->refs. If somebody else owns the request at that point, nothing keeps it from completing the request while the wake up handler is still going to touch it: CPU

In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: own the request before clearing ->head io_waitid_remove_wq() only takes the wait queue lock if ->head is set. io_waitid_wait() clears ->head first thing,

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99227 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99227 | In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: prevent cancel reference wrap io_waitid packs the cancellation state into bit 31 of ->refs and uses bits 30:0 as a 31-bit reference counter: #define IO_WAITID_CANCEL_FLAG BIT(31) #define IO_WAITID_REF_MASK GENMASK(30, 0) __io_waitid_cancel() marks a request canceled, then increments the low bits of ->refs to claim completion ownership. When another path owns the re

In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: prevent cancel reference wrap io_waitid packs the cancellation state into bit 31 of ->refs and uses bits 30:0 as a 31-bit reference counter: #define I

🛡️ 32 🔬 18
7.0 HIGH
EPSS 0.1%
CVE-2026-99224 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99224 | In the Linux kernel, the following vulnerability has been resolved: keys: Protect the type name while describing a key keyctl_describe_key() must keep the key type's name alive until kasprintf() has consumed it. The retained key reference keeps the key and its description alive, but does not pin the module providing its type. The name is passed to kasprintf() without holding key->sem. kvasprintf() uses the saved name pointer in two formatting passes, with

In the Linux kernel, the following vulnerability has been resolved: keys: Protect the type name while describing a key keyctl_describe_key() must keep the key type's name alive until kasprintf() has consumed it. The retained key reference

🛡️ 30 🔬 18
7.0 HIGH
EPSS 0.1%
CVE-2026-99218 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99218 | In the Linux kernel, the following vulnerability has been resolved: coredump: hold RCU while releasing parked threads coredump_finish() releases the parked threads by clearing ->task in their core_thread entry and calling wake_up_process() on each of them. It does that without holding a reference on the task and without being inside rcu. But calling wake_up_process(task) without rcu here isn't safe. A parked thread doesn't need that wakeup to leave. A spur

In the Linux kernel, the following vulnerability has been resolved: coredump: hold RCU while releasing parked threads coredump_finish() releases the parked threads by clearing ->task in their core_thread entry and calling wake_up_process(

🛡️ 30 🔬 18
7.9 HIGH
EPSS 0.2%
CVE-2026-62958 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-62958 | libriscv is a RISC-V sandbox and emulator. Prior to 1.18, a crafted ELF binary can cause out-of-bounds reads in the host emulator. `Memory<W>::binary_loader` checks `PT_LOAD` program-header bounds, but `Memory<W>::serialize_execute_segment` trusts section-header `sh_offset` and `sh_size` when locating `.text` without verifying the file range against `m_binary.size()`; `Memory<W>::lookup()` has a similar section-table problem. Malformed `.text` or `.symtab` of

libriscv is a RISC-V sandbox and emulator. Prior to 1.18, a crafted ELF binary can cause out-of-bounds reads in the host emulator. `Memory::binary_loader` checks `PT_LOAD` program-header bounds, but `Memory::serialize_execute_segment` trust

🛡️ 53 🔬 53
8.2 HIGH
EPSS 0.2%
CVE-2026-62847 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-62847 | Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. Prior to 2025.1.18, 2026.0.25 and 2026.1.19, Metalama.Framework and Metalama.Tool load and execute compile-time assemblies, auxiliary executable tools and embedded helper assemblies from predictable temporary directories. On `Linux` and `macOS`, the default `Path.GetTempPath()` location is world-writable, and existing artifacts are trusted based on sentinel or `.completed` marker

Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. Prior to 2025.1.18, 2026.0.25 and 2026.1.19, Metalama.Framework and Metalama.Tool load and execute compile-time assemblies, auxiliary executable tools and embe

🛡️ 44 🔬 31
7.3 HIGH
EPSS 0.1%
CVE-2026-116250 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-116250 | In server mode pgAdmin 4 validates a path a user gives for a file in their storage directory with check_access_permission() and then opened it by name. Several places opened it with a plain open() or handed the path to a utility that opened it later: the servers.json export and import and the import file listing, and the files given to pg_dump, pg_dumpall, pg_restore and psql by Backup, Restore and Import/Export Data. A symbolic link swapped in at the file o

In server mode pgAdmin 4 validates a path a user gives for a file in their storage directory with check_access_permission() and then opened it by name. Several places opened it with a plain open() or handed the path to a utility that opened

🛡️ 46 🔬 43
7.8 HIGH
EPSS 0.1%
CVE-2026-65584 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-65584 | Software installed and run as a non-privileged user may conduct improper GPU system calls causing a stack overflow in the kernel. The overflow occurs when processing resolved Linux/Android fence synchronization checkpoints, while user checkpoints are excluded from the stack array. Successful exploitation can cause kernel memory corruption and typically results in a denial-of-service condition through a kernel crash. The code vulnerability is a buffer write

Software installed and run as a non-privileged user may conduct improper GPU system calls causing a stack overflow in the kernel. The overflow occurs when processing resolved Linux/Android fence synchronization checkpoints, while user check

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.2%
CVE-2026-115805 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-115805 | Improper handling of local filesystem paths in Rapid7 Insight Agent on Linux and macOS may allow authenticated local users to gain elevated privileges. Exploitation requires existing local access and depends on the Agent's inventory collection processing the crafted path.

Improper handling of local filesystem paths in Rapid7 Insight Agent on Linux and macOS may allow authenticated local users to gain elevated privileges. Exploitation requires existing local access and depends on the Agent's inventory collect

🛡️ 32 🔬 18
8.4 HIGH
EPSS 0.1%
CVE-2026-99216 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-99216 | In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: Don't reset VMBus connection state on error/exit paths In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send me

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: Don't reset VMBus connection state on error/exit paths In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_

🛡️ 39 🔬 28
7.8 HIGH
EPSS 0.1%
CVE-2026-99213 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99213 | In the Linux kernel, the following vulnerability has been resolved: vsock: treat TCP_CLOSING as once-established Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has al

In the Linux kernel, the following vulnerability has been resolved: vsock: treat TCP_CLOSING as once-established Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and r

🛡️ 32 🔬 18
7.0 HIGH
EPSS 0.1%
CVE-2026-99212 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99212 | In the Linux kernel, the following vulnerability has been resolved: net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED. A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the

In the Linux kernel, the following vulnerability has been resolved: net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back

🛡️ 30 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99203 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99203 | In the Linux kernel, the following vulnerability has been resolved: pipe: preserve existing fasync readers on writer setup failure F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback. fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then f

In the Linux kernel, the following vulnerability has been resolved: pipe: preserve existing fasync readers on writer setup failure F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enable

🛡️ 32 🔬 18
8.8 HIGH
EPSS 0.2%
CVE-2026-99185 🌐 Adjacent Network 🔓 Keine Authentifizierung nötig

CVE-2026-99185 | In the Linux kernel, the following vulnerability has been resolved: firewire: core: fix race condition in split transaction handling For a split transaction, either fw_core_handle_response() or split_transaction_timeout_callback() may manipulate the same transaction entry in the pending transaction list. The return value of timer_delete() is used to determine which function handles the entry. If the transaction is a split transaction and timer_delete() retu

In the Linux kernel, the following vulnerability has been resolved: firewire: core: fix race condition in split transaction handling For a split transaction, either fw_core_handle_response() or split_transaction_timeout_callback() may man

🛡️ 41 🔬 28
7.8 HIGH
EPSS 0.1%
CVE-2026-99180 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99180 | In the Linux kernel, the following vulnerability has been resolved: unicode: free the map after a grace period generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still

In the Linux kernel, the following vulnerability has been resolved: unicode: free the map after a grace period generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99177 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99177 | In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Fix page dirtying in sev_gmem_post_populate() set_page_dirty() requires that the caller holds some kind of lock to ensure that the page's mapping does not concurrently go away. That is not the case for a random page we got from get_user_pages_fast(), so use set_page_dirty_lock(). [sean: tag for stable]

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Fix page dirtying in sev_gmem_post_populate() set_page_dirty() requires that the caller holds some kind of lock to ensure that the page's mapping does not concu

🛡️ 32 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99173 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99173 | In the Linux kernel, the following vulnerability has been resolved: eventfs: Free the eventfs_inode after an rcu grace period too tracefs_d_revalidate() reads ->is_freed of the eventfs_inode that dentry->d_fsdata points to, and ->d_revalidate() is called in rcu pathwalk mode with nothing but rcu_read_lock() held. The dentry itself stays around for such a walker, but tracefs_d_release() drops its reference to the eventfs_inode when the dentry is killed, and

In the Linux kernel, the following vulnerability has been resolved: eventfs: Free the eventfs_inode after an rcu grace period too tracefs_d_revalidate() reads ->is_freed of the eventfs_inode that dentry->d_fsdata points to, and ->d_revali

🛡️ 32 🔬 18
8.8 HIGH
EPSS 0.1%
CVE-2026-99170 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99170 | In the Linux kernel, the following vulnerability has been resolved: namespace: a mount that copy_tree() leaves out can't take over a lock Since commit c62a4766937e ("move_mount: transfer MNT_LOCKED") a mount can be moved beneath a locked mount. The lock moves from the old cover to the new mount which takes over the job of hiding what's under it and the old cover can be unmounted. That works as long as the new mount stays. But the caller picks the new mount

In the Linux kernel, the following vulnerability has been resolved: namespace: a mount that copy_tree() leaves out can't take over a lock Since commit c62a4766937e ("move_mount: transfer MNT_LOCKED") a mount can be moved beneath a locked

🛡️ 36 🔬 18
7.8 HIGH
EPSS 0.1%
CVE-2026-99167 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99167 | In the Linux kernel, the following vulnerability has been resolved: net/sched: fix use-after-free in __tcf_action_put() __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as: BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340 Write of size 4 at addr ff11000000d46420 by

In the Linux kernel, the following vulnerability has been resolved: net/sched: fix use-after-free in __tcf_action_put() __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the a

🛡️ 32 🔬 18
60 von ~84 Einträgen geladen