Lucene search
+L

387315 matches found

CVE
CVE
added 2026/08/15 5:52 a.m.32 views

CVE-2026-72117

CVE-2026-72117 concerns the Linux kernel “can: bcm” code, where a data race on rx_stamp/rx_ifindex in bcm_rx_handler() could occur for an rx op subscribed to all interfaces (ifindex == 0). The same op could be registered in a shared per-netns wildcard filter list, allowing concurrent bcm_rx_handl...

5.4AI score0.00211EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.25 views

CVE-2026-72116

The CVE-2026-72116 entry describes a Linux kernel issue in the CAN networking path (bcm) where stale RX/TX operation references could occur after device removal. RX: an RX_SETUP update could skip can_rx_register() if NETDEV_UNREGISTER occurred, leaving rx_ops with ifindex=0 and not re-enabling fr...

7.1CVSS5.6AI score0.00181EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.26 views

CVE-2026-72115

The CVE-2026-72115 issue affects the Linux kernel CAN BCM RX path. A race between bcm_rx_handler(), hrtimer_cancel(), bcm_rx_starttimer(), and bcm_rx_timeout_handler() could allow an ANYDEV operation (ifindex == 0) to process frames from multiple interfaces, causing spurious RX_TIMEOUT events and...

8.1CVSS5.3AI score0.00295EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.27 views

CVE-2026-72113

Technical details are not publicly available in the provided documents. Monitor for updates from vendors and security advisories.

7.8CVSS5.4AI score0.00164EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.29 views

CVE-2026-72114

In the Linux kernel CAN BCM subsystem, CVE-2026-72114 is due to bcm_rx_setup() not validating the frame length for RTR-reply frames configured via RX_SETUP with RX_RTR_FRAME, unlike bcm_tx_setup() which validates cf->len against CAN/CAN FD DLC limits. The vulnerability is resolved by adding va...

7.8CVSS5.3AI score0.00164EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.29 views

CVE-2026-72112

CVE-2026-72112 concerns the Linux kernel io_uring/bpf-ops path where a second registration of BPF ops could be bound to the same ring due to not advancing past BPF_STRUCT_OPS_STATE_READY, allowing bpf_io_reg() to re-resolve the target ring and potentially bind the same io_uring_bpf_ops map to dif...

7.8CVSS5.5AI score0.00154EPSS
SaveExploits0References2
CVE
CVE
added 2026/08/15 5:52 a.m.30 views

CVE-2026-72111

CVE-2026-72111 affects the Linux kernel BPF verifier. The issue occurs when processing a context load of an LSM hook return value: __mark_reg_s32_range() narrows the destination register by intersecting with stale bounds instead of replacing them, potentially creating a verifier/runtime mismatch ...

8.8CVSS5.3AI score0.00172EPSS
SaveExploits0References4
CVE
CVE
added 2026/08/15 5:52 a.m.28 views

CVE-2026-72110

The CVE-2026-72110 entry documents a Linux kernel issue in which a nascent task may bail out of copy_process() to free_task() before p->bpf_storage is initialized, causing the nascent task’s bpf_storage pointer to be a stale copy from the parent. This can lead to kernel hangs or use-after-free...

7.8CVSS5.3AI score0.00163EPSS
SaveExploits0References7
CVE
CVE
added 2026/08/15 5:52 a.m.26 views

CVE-2026-72109

The CVE-2026-72109 issue affects the Linux kernel net: sparx5, where sparx5_register_notifier_blocks() registers the switchdev blocking notifier before allocating the ordered workqueue. If the workqueue allocation fails, the error path unregisters the switchdev and netdevice notifiers but leaves ...

7.8CVSS5.3AI score0.00164EPSS
SaveExploits0References7
CVE
CVE
added 2026/08/15 5:52 a.m.36 views

CVE-2026-72108

CVE-2026-72108 : The Linux kernel fix addresses a metadata inconsistency in dm thin metadata when a metadata snapshot commit fails. The root cause was that __reserve_metadata_snap() and __release_metadata_snap() modified the superblock’s held_root directly in the block_manager buffer, which could...

7.8CVSS5.4AI score0.00164EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.27 views

CVE-2026-72107

Summary (CVE-2026-72107) In the Linux kernel, the vulnerability is in the dm-era code path where writes are tracked in target-relative blocks. The root cause is that era_map() calculates the writeset block before applying the target offset, allowing a non-zero start sector to pass an absolute map...

8.8CVSS5.3AI score0.00632EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.26 views

CVE-2026-72106

In the Linux kernel, the dm-ioctl path in list_version_get_info has a potential buffer overflow: sizeof(tt->version) is 12 bytes, but the code writes 16 bytes into the output buffer (info->vers->version[0..2] and info->vers->next). The fix replaces sizeof(tt->version) with sizeo...

5.8AI score0.00216EPSS
SaveExploits0References5
CVE
CVE
added 2026/08/15 5:52 a.m.31 views

CVE-2026-72105

The CVE-2026-72105 entry concerns the Linux kernel dm-log component, where a bitset_size overflow on 32‑bit architectures could occur during region_count handling. The root cause is a miscalculation of bitset_size (size_t) when computing the bitmap memory based on region_count, which could wrap t...

7.8CVSS5.5AI score0.00164EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.22 views

CVE-2026-72104

The CVE-2026-72104 entry concerns the Linux kernel component dm-pcache (pcache target). The vulnerability arises when optional arguments are parsed as name/value pairs and a table advertises an option (e.g., cache_mode) but provides only the option name; after consuming the name, the parser decre...

5.4AI score0.00198EPSS
SaveExploits0References3
CVE
CVE
added 2026/08/15 5:52 a.m.25 views

CVE-2026-72102

The CVE-2026-72102 entry concerns the Linux kernel. Affected area: dm_early_create logic related to dynamic device-mapper table handling. Root cause: when dm_resume fails, a table is freed via dm_table_destroy even though it was already instantiated with dm_swap_table, leading to a potential use-...

7.8CVSS5.4AI score0.00164EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.27 views

CVE-2026-72103

CVE-2026-72103 relates to the Linux kernel’s dm-crypt flow. A refactoring bug caused the caller’s thread keyring to be kept alive beyond the caller’s lifetime, making the LUKS volume key linger in memory. As a result, cryptsetup luksSuspend could fail to wipe the key, even though luksOpen passes ...

7.3CVSS5.5AI score0.00159EPSS
SaveExploits0References4
CVE
CVE
added 2026/08/15 5:52 a.m.30 views

CVE-2026-72101

The CVE-2026-72101 involves the Linux kernel dm‑integrity module. A bug caused zeroing of the remaining space to fail when the hash size was smaller than the device tuple size, leading to leaking uninitialized kernel memory. The issue has been fixed by a commit that corrects the zeroing behavior....

5.4AI score0.002EPSS
SaveExploits0References4
CVE
CVE
added 2026/08/15 5:52 a.m.32 views

CVE-2026-72099

Summary (CVE-2026-72099) In the Linux kernel, the dm-integrity component had an issue where hash_offset could be incremented twice; the loop already increments hash_offset, so a second increment was unnecessary. The vulnerability was resolved by correcting this behavior in the relevant code path ...

7.1CVSS5.2AI score0.00459EPSS
SaveExploits0References8
CVE
CVE
added 2026/08/15 5:52 a.m.30 views

CVE-2026-72100

CVE-2026-72100 concerns the Linux kernel function dm-integrity. A bug in dm_integrity_check_limits could exit with DM_MAPIO_KILL while the affected range was still locked, causing a potential deadlock and leaked resources. The fix moves the limit check up so that on exit no resources are leaked. ...

8.8CVSS5.3AI score0.0056EPSS
SaveExploits0References4
CVE
CVE
added 2026/08/15 5:52 a.m.50 views

CVE-2026-72098

The CVE-2026-72098 issue affects the Linux kernel’s dm-verity FEC calculation. A buffer overflow occurs in dm-verity-fec when computing erasures: if (neras && *neras fec->roots) fio->erasures[(*neras)++] = i;. The post-increment can push *neras to roots+1, which is passed as no_eras to deco...

9.8CVSS5.8AI score0.00646EPSS
SaveExploits0References3
Rows per page
Query Builder