Export limit exceeded: 416241 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 416241 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (416241 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-117712 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117711 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117710 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117709 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117708 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117707 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117706 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117705 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117704 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117703 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117702 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117701 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117700 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117699 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117698 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117697 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117696 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117695 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-99179 | 1 Linux | 1 Linux Kernel | 2026-10-28 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: watch_queue: Fix note pool publication race in watch_queue_set_size() There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this). Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0]. An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0 Call Trace: __post_watch_notification+0x148/0x180 keyctl_setperm_key+0x119/0x130 do_syscall_64+0x108/0x4c0 entry_SYSCALL_64_after_hwframe+0x77/0x7f Kernel panic - not syncing: Fatal exception in interrupt Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched. A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before. | ||||
| CVE-2026-99166 | 1 Linux | 1 Linux Kernel | 2026-10-28 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: net: rds: fix uninitialized trans dereference in CM event handler rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA). On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases. An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue. GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops. The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies. The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport. The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it. The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event. On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0. [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of bailing out for every event on a non-IB device, so that rdma_cm does not destroy connection ids RDS still tracks; drop a connection whose address resolved to a non-IB device before a route is resolved on it; changelog adjusted] | ||||