Overview 18,437 matches · 1 in Waratek scope · 1 protected · 7 exploited · 0 CISA KEV · 131 public PoC · 0 EPSS ≥ 0.5
18,437matches
1in Waratek scope0.0%
1protected0.0%
7exploited0.0%
0CISA KEV0.0%
131public PoC0.7%
0EPSS ≥ 0.50.0%
Protected by Waratek
1
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
1,003
5.4%
Withdrawn CVE
17,433
94.6%
blocked by ARMR today
1
0.0%
partly blocked
0
0.0%
not blocked
18,436
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 3,471 / year
19921
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19930
19941
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19950
19961
Withdrawn CVE1
Unknown1
not blocked1
Working exploit published1
19971
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19981
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
199929
Withdrawn CVE29
Unknown29
not blocked29
Working exploit published1
No public exploit28
20001
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
20013
Withdrawn CVE3
Unknown3
not blocked3
No public exploit3
200214
Withdrawn CVE14
Unknown14
not blocked14
Working exploit published2
No public exploit12
200321
Withdrawn CVE21
Unknown21
not blocked21
Working exploit published1
No public exploit20
200428
Withdrawn CVE28
Unknown28
not blocked28
No public exploit28
200578
Withdrawn CVE78
Unknown78
not blocked78
Working exploit published5
No public exploit73
200651
Withdrawn CVE51
Unknown51
not blocked51
Working exploit published3
No public exploit48
200780
Withdrawn CVE80
Unknown80
not blocked80
Working exploit published3
No public exploit77
200832
Withdrawn CVE32
Unknown32
not blocked32
Working exploit published5
No public exploit27
200946
Withdrawn CVE46
Unknown46
not blocked46
Working exploit published6
No public exploit40
201028
Withdrawn CVE28
Unknown28
not blocked28
Working exploit published2
No public exploit26
201122
Withdrawn CVE22
Unknown22
not blocked22
Working exploit published3
No public exploit19
201263
Withdrawn CVE63
Unknown63
not blocked63
Working exploit published5
No public exploit58
2013137
Withdrawn CVE137
Unknown137
not blocked137
Working exploit published20
No public exploit117
201480
Withdrawn CVE80
Unknown80
not blocked80
Working exploit published11
No public exploit69
2015101
Withdrawn CVE101
Unknown101
not blocked101
Working exploit published5
No public exploit96
201668
Withdrawn CVE68
Unknown68
not blocked68
Working exploit published4
No public exploit64
20173,471
Withdrawn CVE3,471
Unknown3,471
not blocked3,471
Exploited1
Working exploit published10
No public exploit3,460
20181,644
Withdrawn CVE1,644
Unknown1,644
not blocked1,644
Working exploit published5
Proof of concept only1
No public exploit1,638
20191,633
Withdrawn CVE1,633
Unknown1,633
not blocked1,633
Exploited1
Working exploit published3
No public exploit1,629
2020900
Withdrawn CVE900
Unknown900
not blocked900
Working exploit published5
No public exploit895
20211,801
Withdrawn CVE1,801
Unknown1,801
not blocked1,801
Working exploit published1
No public exploit1,800
20221,360
Not applicable2
Withdrawn CVE1,358
Unknown1,360
not blocked1,360
Working exploit published4
Proof of concept only6
No public exploit1,350
20232,134
Not applicable1
Withdrawn CVE2,133
Unknown2,134
not blocked2,134
Exploited1
Working exploit published6
Proof of concept only1
No public exploit2,126
2024759
Protected by Waratek1
Not applicable7
Withdrawn CVE751
Unknown759
blocked by ARMR today1
not blocked758
Exploited1
Working exploit published4
Proof of concept only1
No public exploit753
20252,719
Not applicable897
Withdrawn CVE1,822
Unknown2,719
not blocked2,719
Exploited2
Working exploit published3
Proof of concept only2
No public exploit2,712
20261,129
Not applicable96
Withdrawn CVE1,033
Unknown1,129
not blocked1,129
Exploited1
No public exploit1,128
199319961999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-27583 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27582 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27581 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27580 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27573 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27501 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27500 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27201 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-27200 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the situation described is not a vulnerability. |
| CVE-2026-2647 | Unknown | 2026-02-27 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-11384 | Unknown | 2026-02-26 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-11383 | Unknown | 2026-02-26 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-11382 | Unknown | 2026-02-26 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-11381 | Unknown | 2026-02-26 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-3197 | Unknown | 2026-02-25 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-27163 | Unknown | 2026-02-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE was assigned in error. |
| CVE-2026-25984 | Unknown | 2026-02-23 | Withdrawn CVE | No public exploit | Rejected reason: This CVE was assigned in error. |
| CVE-2026-27534 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27533 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27532 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27531 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27530 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27529 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27528 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27527 | Unknown | 2026-02-21 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27325 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27324 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27323 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27322 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27321 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27320 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27319 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27318 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27317 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26995 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: Further research determined the issue is an external dependency vulnerability. |
| CVE-2026-26957 | Unknown | 2026-02-20 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: Upon further research, the maintainer determined that the behavior described by the CVE record is intended behavior. Per the GitHub Security Advisory: "Libredesk is a single-tenant, self-hosted application. Configuring outbound webhook URLs requires an admin-only permission that is not granted by default - the operator must explicitly assign it. Anyone holding this permission already has full administrative control over the application, and outbound HTTP to operator-chosen URLs is the documented purpose of the webhook feature. This is working as designed." Notes: none. |
| CVE-2026-2744 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-27066 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-25412 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71250 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71249 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71248 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71247 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71246 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71245 | Unknown | 2026-02-19 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2026-27038 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27037 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27036 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27035 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27034 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27033 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27032 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-27031 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-25421 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Collision with another CVE. |
| CVE-2025-71228 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-71226 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2025-13965 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2025-12500. Reason: This candidate is a reservation duplicate of CVE-2025-12500. Notes: All CVE users should reference CVE-2025-12500 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2025-13933 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2025-12500. Reason: This candidate is a reservation duplicate of CVE-2025-12500. Notes: All CVE users should reference CVE-2025-12500 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2025-13602 | Unknown | 2026-02-18 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-2570 | Unknown | 2026-02-17 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-1452 | Unknown | 2026-02-17 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-1783 | Unknown | 2026-02-16 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2026-26303 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26302 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26301 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26300 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26299 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26298 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26297 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26296 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26295 | Unknown | 2026-02-14 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-23183 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: cgroup/dmem: fix NULL pointer dereference when setting max An issue was triggered: BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 15 UID: 0 PID: 658 Comm: bash Tainted: 6.19.0-rc6-next-2026012 Tainted: [O]=OOT_MODULE Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), RIP: 0010:strcmp+0x10/0x30 RSP: 0018:ffffc900017f7dc0 EFLAGS: 00000246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff888107cd4358 RDX: 0000000019f73907 RSI: ffffffff82cc381a RDI: 0000000000000000 RBP: ffff8881016bef0d R08: 000000006c0e7145 R09: 0000000056c0e714 R10: 0000000000000001 R11: ffff888107cd4358 R12: 0007ffffffffffff R13: ffff888101399200 R14: ffff888100fcb360 R15: 0007ffffffffffff CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000105c79000 CR4: 00000000000006f0 Call Trace: <TASK> dmemcg_limit_write.constprop.0+0x16d/0x390 ? __pfx_set_resource_max+0x10/0x10 kernfs_fop_write_iter+0x14e/0x200 vfs_write+0x367/0x510 ksys_write+0x66/0xe0 do_syscall_64+0x6b/0x390 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f42697e1887 It was trriggered setting max without limitation, the command is like: "echo test/region0 > dmem.max". To fix this issue, add check whether options is valid after parsing the region_name. |
| CVE-2026-23182 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: spi: tegra: Fix a memory leak in tegra_slink_probe() In tegra_slink_probe(), when platform_get_irq() fails, it directly returns from the function with an error code, which causes a memory leak. Replace it with a goto label to ensure proper cleanup. |
| CVE-2026-23181 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: btrfs: sync read disk super and set block size When the user performs a btrfs mount, the block device is not set correctly. The user sets the block size of the block device to 0x4000 by executing the BLKBSZSET command. Since the block size change also changes the mapping->flags value, this further affects the result of the mapping_min_folio_order() calculation. Let's analyze the following two scenarios: Scenario 1: Without executing the BLKBSZSET command, the block size is 0x1000, and mapping_min_folio_order() returns 0; Scenario 2: After executing the BLKBSZSET command, the block size is 0x4000, and mapping_min_folio_order() returns 2. do_read_cache_folio() allocates a folio before the BLKBSZSET command is executed. This results in the allocated folio having an order value of 0. Later, after BLKBSZSET is executed, the block size increases to 0x4000, and the mapping_min_folio_order() calculation result becomes 2. This leads to two undesirable consequences: 1. filemap_add_folio() triggers a VM_BUG_ON_FOLIO(folio_order(folio) < mapping_min_folio_order(mapping)) assertion. 2. The syzbot report [1] shows a null pointer dereference in create_empty_buffers() due to a buffer head allocation failure. Synchronization should be established based on the inode between the BLKBSZSET command and read cache page to prevent inconsistencies in block size or mapping flags before and after folio allocation. [1] KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:create_empty_buffers+0x4d/0x480 fs/buffer.c:1694 Call Trace: folio_create_buffers+0x109/0x150 fs/buffer.c:1802 block_read_full_folio+0x14c/0x850 fs/buffer.c:2403 filemap_read_folio+0xc8/0x2a0 mm/filemap.c:2496 do_read_cache_folio+0x266/0x5c0 mm/filemap.c:4096 do_read_cache_page mm/filemap.c:4162 [inline] read_cache_page_gfp+0x29/0x120 mm/filemap.c:4195 btrfs_read_disk_super+0x192/0x500 fs/btrfs/volumes.c:1367 |
| CVE-2026-23179 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() When the socket is closed while in TCP_LISTEN a callback is run to flush all outstanding packets, which in turns calls nvmet_tcp_listen_data_ready() with the sk_callback_lock held. So we need to check if we are in TCP_LISTEN before attempting to get the sk_callback_lock() to avoid a deadlock. |
| CVE-2026-23177 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: mm, shmem: prevent infinite loop on truncate race When truncating a large swap entry, shmem_free_swap() returns 0 when the entry's index doesn't match the given index due to lookup alignment. The failure fallback path checks if the entry crosses the end border and aborts when it happens, so truncate won't erase an unexpected entry or range. But one scenario was ignored. When `index` points to the middle of a large swap entry, and the large swap entry doesn't go across the end border, find_get_entries() will return that large swap entry as the first item in the batch with `indices[0]` equal to `index`. The entry's base index will be smaller than `indices[0]`, so shmem_free_swap() will fail and return 0 due to the "base < index" check. The code will then call shmem_confirm_swap(), get the order, check if it crosses the END boundary (which it doesn't), and retry with the same index. The next iteration will find the same entry again at the same index with same indices, leading to an infinite loop. Fix this by retrying with a round-down index, and abort if the index is smaller than the truncate range. |
| CVE-2026-23176 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: platform/x86: toshiba_haps: Fix memory leaks in add/remove routines toshiba_haps_add() leaks the haps object allocated by it if it returns an error after allocating that object successfully. toshiba_haps_remove() does not free the object pointed to by toshiba_haps before clearing that pointer, so it becomes unreachable allocated memory. Address these memory leaks by using devm_kzalloc() for allocating the memory in question. |
| CVE-2026-23174 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: nvme-pci: handle changing device dma map requirements The initial state of dma_needs_unmap may be false, but change to true while mapping the data iterator. Enabling swiotlb is one such case that can change the result. The nvme driver needs to save the mapped dma vectors to be unmapped later, so allocate as needed during iteration rather than assume it was always allocated at the beginning. This fixes a NULL dereference from accessing an uninitialized dma_vecs when the device dma unmapping requirements change mid-iteration. |
| CVE-2025-71224 | Unknown | 2026-02-14 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: ocb: skip rx_no_sta when interface is not joined ieee80211_ocb_rx_no_sta() assumes a valid channel context, which is only present after JOIN_OCB. RX may run before JOIN_OCB is executed, in which case the OCB interface is not operational. Skip RX peer handling when the interface is not joined to avoid warnings in the RX path. |
| CVE-2026-26257 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26256 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26255 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26254 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26253 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26252 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26251 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26250 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2026-26249 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: Not used |
| CVE-2025-68128 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-68127 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-68126 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-68125 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-68124 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-58184 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-58182 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-47915 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: reserved but not needed |
| CVE-2025-36552 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused |
| CVE-2025-36545 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused |
| CVE-2025-36542 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused |
| CVE-2025-36538 | Unknown | 2026-02-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused |