🔴 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
2 🔴 Critical im Radar
0 ⚠️ CISA KEV
0 🔓 Aktiv ausgenutzt
0 🧪 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: 394 Criticals, davon 2 KEV, Ø CVSS 9,5 Ø CVSS je Monat 10.864 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.78395,8 %+1.738
415.316 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) 1 aktiv
644 resultaten (54 van 644 resultaten)
Weergave “🏢 linux · Sort: EPSS” resetten ✕
644 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.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
9.8 CRITICAL
EPSS 0.6%
CVE-2026-99153 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99153 | In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Validate the ITT reflected in a Reject PDU A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up: memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr)); ... task = iscsi_itt_to_task(conn, rejected_pdu.itt); That value is whatever the target put there. iscsi_itt_to_task()

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Validate the ITT reflected in a Reject PDU A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy

🛡️ 49 🔬 40
9.8 CRITICAL
EPSS 0.5%
CVE-2026-99154 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99154 | In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Reject a negative task index from parse_pdu_itt A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only: if (i >= session->cmds_max) i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array. be2iscsi produces one. beiscsi_parse_pdu() assigns the

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Reject a negative task index from parse_pdu_itt A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bou

🛡️ 49 🔬 40
7.5 HIGH
EPSS 0.5%
CVE-2026-99152 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99152 | In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Validate the task named by a management response __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved: case ISCSI_OP_LOGOUT_RSP: case ISCSI_OP_LOGIN_RSP: case ISCSI_OP_TEXT_RSP: case ISCSI_OP_SCSI_TMFUNC_RSP: case ISCSI_OP_NOOP_IN: task = iscsi_itt_to_task(conn, hdr

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Validate the task named by a management response __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the i

🛡️ 41 🔬 36
8.2 HIGH
EPSS 0.4%
CVE-2026-99131 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-99131 | In the Linux kernel, the following vulnerability has been resolved: xfs: fix capability check in xfs An user reported a bug where he managed to evade group's quota by changing a file's gid to a different group id the same user belonged to, even though quotas were enforced on both gids and the file's size was big enough to exceed the quota's hardlimit. Commit eba0549bc7d1 replaced a capable() call by a has_capability_noaudit() to prevent unnecessary selinux

In the Linux kernel, the following vulnerability has been resolved: xfs: fix capability check in xfs An user reported a bug where he managed to evade group's quota by changing a file's gid to a different group id the same user belonged to

🛡️ 44 🔬 36
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
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
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
8.8 HIGH
EPSS 0.4%
CVE-2026-99083 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-99083 | In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix heap out-of-bounds write in krb5_authenticate() In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off. This causes out_len to overstate remaining buffer

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix heap out-of-bounds write in krb5_authenticate() In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming

🛡️ 41 🔬 26
– OHNE BEWERTUNG
EPSS 0.2%
CVE-2026-98439 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-98439 | Linux Kernel up to 7.2.6 SMB Server improper synchronization (Nessus ID 385073)

A vulnerability was found in Linux Kernel up to 7.2.6. It has been classified as critical. The impacted element is an unknown function of the component SMB Server. The manipulation leads to improper synchronization. This vulnerability is tr

– OHNE BEWERTUNG
EPSS 0.2%
CVE-2026-98177 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-98177 | Linux Kernel up to 7.2.7/7.3-rc3 amdkfd eop_ring_buffer_size integer underflow (Nessus ID 385073 / WID-SEC-2026-3743)

A vulnerability labeled as very critical has been found in Linux Kernel up to 7.2.7/7.3-rc3. This issue affects some unknown processing of the component amdkfd. Executing a manipulation of the argument eop_ring_buffer_size can lead to integ

– OHNE BEWERTUNG
EPSS 0.2%
CVE-2026-98176 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-98176 | Linux Kernel amdkfd integer underflow (Nessus ID 385073 / WID-SEC-2026-3743)

A vulnerability identified as very critical has been detected in Linux Kernel. This vulnerability affects unknown code of the component amdkfd. Performing a manipulation results in integer underflow. This vulnerability is reported as CVE-20

– OHNE BEWERTUNG
EPSS 0.2%
CVE-2026-89866 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-89866 | Linux Kernel up to 7.2.4 wave5 send_firmware_command race condition (Nessus ID 385073)

A vulnerability was found in Linux Kernel up to 7.2.4. It has been declared as critical. The impacted element is the function send_firmware_command of the component wave5. Such manipulation leads to race condition. This vulnerability is lis

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.5 HIGH
EPSS 0.2%
CVE-2026-99094 🌐 Adjacent Network 🔓 Keine Authentifizierung nötig

CVE-2026-99094 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel_pcie: fix TX descriptor bounds check btintel_pcie_prepare_tx() uses tfd_index to access the TFD and data buffer arrays before the index is advanced modulo txq->count. An index equal to txq->count is one past the end of both arrays, so reject it in the bounds check.

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btintel_pcie: fix TX descriptor bounds check btintel_pcie_prepare_tx() uses tfd_index to access the TFD and data buffer arrays before the index is advanced mod

🛡️ 36 🔬 28
8.8 HIGH
EPSS 0.2%
CVE-2026-99082 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99082 | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use active memslots for the per-vCPU MMIO cache KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information. Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1. Commit 56f17dd3fbc4 ("kvm: x86: fix stale mmio

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Use active memslots for the per-vCPU MMIO cache KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO info

🛡️ 36 🔬 18
– OHNE BEWERTUNG
EPSS 0.1%
CVE-2026-98228 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-98228 | Linux Kernel up to 7.2.7/7.3-rc3 MIPS LL/SC fs/pipe.c arch_cmpxchg race condition (Nessus ID 385073)

A vulnerability marked as critical has been reported in Linux Kernel up to 7.2.7/7.3-rc3. The affected element is the function arch_cmpxchg of the file fs/pipe.c of the component MIPS LL/SC. Performing a manipulation results in race conditi

– OHNE BEWERTUNG
EPSS 0.1%
CVE-2026-98180 💻 Lokal 🔓 Keine Authentifizierung nötig

CVE-2026-98180 | Linux Kernel up to 6.18.53/7.2.7/7.3-rc3 drm/msm drm_sched_fence_get_timeline_name use after free (Nessus ID 385073 / WID-SEC-2026-3743)

A vulnerability described as very critical has been identified in Linux Kernel up to 6.18.53/7.2.7/7.3-rc3. The affected element is the function drm_sched_fence_get_timeline_name of the component drm/msm. The manipulation results in use aft

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
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
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
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
7.8 HIGH
EPSS 0.1%
CVE-2026-99164 💻 Lokal 🔑 Geringe Nutzerrechte nötig

CVE-2026-99164 | In the Linux kernel, the following vulnerability has been resolved: spi: imx: fix slab corruption from undersized DMA bounce buffers Since commit faa8e404ad8e ("spi: imx: support dynamic burst length for ECSPI DMA mode"), the driver allocates its private DMA TX/RX buffers with kzalloc(dma_len), where dma_len is only rounded up to 4 bytes, but maps, syncs and unmaps them with DMA_CACHE_ALIGNED_LEN(dma_len), i.e. rounded up to the cache line size. As a result

In the Linux kernel, the following vulnerability has been resolved: spi: imx: fix slab corruption from undersized DMA bounce buffers Since commit faa8e404ad8e ("spi: imx: support dynamic burst length for ECSPI DMA mode"), the driver alloc

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

CVE-2026-99163 | In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields In check_synth_field(), when a synthetic event field is a stacktrace (field->is_stack) and the histogram field is not a "long[" stacktrace array, validation falls through to the generic size and signedness comparison. Because parse_synth_field() sets a stacktrace field's type to "__data_loc unsigned long[]", i

In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields In check_synth_field(), when a synthetic event field is a stacktrace (field->is_stack) an

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

CVE-2026-99156 | In the Linux kernel, the following vulnerability has been resolved: scsi: st: Fix use-after-free race between st_remove() and st_open() st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr. scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes

In the Linux kernel, the following vulnerability has been resolved: scsi: st: Fix use-after-free race between st_remove() and st_open() st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its

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

CVE-2026-99148 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: keep the eviction fence until the last handle is closed amdgpu_gem_object_close() detaches the user queue eviction fence from the BO before it checks bo_va->ref_count, so closing any handle of a BO removes the fence, even when the file still has another handle to the BO and the bo_va with its GPU mappings stays. The BO can then be evicted without suspending the user queues of th

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: keep the eviction fence until the last handle is closed amdgpu_gem_object_close() detaches the user queue eviction fence from the BO before it checks bo_va->r

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

CVE-2026-99143 | In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the predicate limit separate from program capacity predicate_parse() adds two to nr_preds to reserve the terminal TRUE and FALSE entries. It also uses that increased value as the limit for parsed predicates. If the initial count is smaller than the number actually parsed, the program can fill the allocation and subsequent accesses can go past its end. Keep nr_preds as the pre

In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the predicate limit separate from program capacity predicate_parse() adds two to nr_preds to reserve the terminal TRUE and FALSE entries. It also uses that

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

CVE-2026-99142 | In the Linux kernel, the following vulnerability has been resolved: tracing: Check operator stack capacity before pushing predicate_parse() uses the first operator stack entry before processing any opening parentheses. A push then increments top before writing. The existing check still permits that write when top already points to the last allocated entry, which can access beyond the operator stack. Reject the push when top reaches the last allocated entry

In the Linux kernel, the following vulnerability has been resolved: tracing: Check operator stack capacity before pushing predicate_parse() uses the first operator stack entry before processing any opening parentheses. A push then increme

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

CVE-2026-99136 | In the Linux kernel, the following vulnerability has been resolved: dm-crypt: fix a tiny race condition in crypt_dec_pending crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and wa

In the Linux kernel, the following vulnerability has been resolved: dm-crypt: fix a tiny race condition in crypt_dec_pending crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio ca

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

CVE-2026-99123 | In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: validate packet source for connected sockets virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket. The fallback does not validate th

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: validate packet source for connected sockets virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destinatio

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

CVE-2026-99122 | In the Linux kernel, the following vulnerability has been resolved: vsock/vmci: validate packet source for connected sockets vmci_transport_recv_stream_cb() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback can select a non-listening socket without checking whether the packet came from its stored peer. This was reproduced with two VMCI contexts. A RST from the context not stored in a

In the Linux kernel, the following vulnerability has been resolved: vsock/vmci: validate packet source for connected sockets vmci_transport_recv_stream_cb() looks up sockets first by the full source and destination tuple, then by destinat

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

CVE-2026-99117 | In the Linux kernel, the following vulnerability has been resolved: net: bridge: mcast: don't truncate the port group walk on teardown __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl(). If such an entry is the iterator's saved next node, hlist_del_

In the Linux kernel, the following vulnerability has been resolved: net: bridge: mcast: don't truncate the port group walk on teardown __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_ent

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

CVE-2026-99116 | In the Linux kernel, the following vulnerability has been resolved: net: psp: do not inherit the Rx association on clone sk->psp_assoc sits past sk_dontcopy_end, so sock_copy() copies it into every socket accepted from a listener without taking a reference, while inet_sock_destruct() puts for every inet socket. psp_twsk_init() does refcount_inc() for the timewait socket, so a child closing through TIME_WAIT cancels its own put and leaves the association wit

In the Linux kernel, the following vulnerability has been resolved: net: psp: do not inherit the Rx association on clone sk->psp_assoc sits past sk_dontcopy_end, so sock_copy() copies it into every socket accepted from a listener without

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

CVE-2026-99112 | In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_flower: validate mask pointer after nla_next() fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes. The nla_ok() added by commit c96adff956191 ("cls_flow

In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_flower: validate mask pointer after nla_next() fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing

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

CVE-2026-99110 | In the Linux kernel, the following vulnerability has been resolved: smb: client: fix heap overflow in cifs_do_set_acl() cifs_set_acl() validates ACL size using posix_acl_xattr_size(): 4 + (count * 8) // 4-byte header + 8 bytes per ACE cifs_do_set_acl() then calls posix_acl_to_cifs() to write the CIFS wire format into the same buffer: 6 + (count * 10) // 6-byte header + 10 bytes per ACE An ACL that passes the xattr-based check in cifs_s

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix heap overflow in cifs_do_set_acl() cifs_set_acl() validates ACL size using posix_acl_xattr_size(): 4 + (count * 8) // 4-byte header + 8 bytes p

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

CVE-2026-99109 | In the Linux kernel, the following vulnerability has been resolved: smb: client: reject SetEA requests that do not fit the request buffer CIFSSMBSetEA() copies the caller's extended attribute value into the SMB request buffer without checking that it fits. The requirement is stated in the source but was never implemented: /*BB add length check to see if it would fit in negotiated SMB buffer size BB */ /* if (ea_value_len > buffer_size - 512 (enoug

In the Linux kernel, the following vulnerability has been resolved: smb: client: reject SetEA requests that do not fit the request buffer CIFSSMBSetEA() copies the caller's extended attribute value into the SMB request buffer without chec

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

CVE-2026-99107 | In the Linux kernel, the following vulnerability has been resolved: ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize ntfs_new_attr_flags() passes the wrong MFT record to ntfs_attr_record_resize(). When the attribute is in an extent record, ctx->mrec points to the extent but the function receives the base record pointer m, causing incorrect size calculations in memmove. Fix by passing ctx->mrec (the actual MFT record containing the a

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize ntfs_new_attr_flags() passes the wrong MFT record to ntfs_attr_record_resize(). When the attribut

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

CVE-2026-99099 | In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Fix AMD TLBI Erratum #1718 The processor may fail to invalidate a TLB entry while executing an INVLPGB/TLBSYNC instruction pair. Detect the erratum and apply a software workaround when a microcode fix is not present.

In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Fix AMD TLBI Erratum #1718 The processor may fail to invalidate a TLB entry while executing an INVLPGB/TLBSYNC instruction pair. Detect the erratum and appl

🛡️ 32 🔬 18
54 von ~54 Einträgen geladen Ende der Trefferliste — 54 Einträge geladen. Tipp: Filter leichtern für tieferes Blättern.