263186 matches found
CVE-2026-72201
CVE-2026-72201 affects the Linux kernel NTFS implementation where index entries are validated after reading an index root or block. Root cause: insufficient immediate validation of index entries during lookup/readdir paths, leading to potential missed checks. The CVSS appears CRITICAL (Network, N...
CVE-2026-72199
The CVE refers to the Linux kernel ntfs patch that validates resident index root values on lookup. The fix ensures 8-byte alignment of index header fields, sane entries_offset, index_length within allocated_size, and allocated_size consistency within the resident value, and it validates header in...
CVE-2026-72197
The CVE-2026-72197 issue affects the Linux kernel, specifically the fs/ntfs3 path for DeleteIndexEntryAllocation. The root cause is that e->size can cause an overlong memmove when e + e->size points past hdr + hdr->used, leading to a dangerous memmove length. A corresponding guard alread...
CVE-2026-72198 ntfs: reject non-resident records for resident-only attributes
In the Linux kernel, the following vulnerability has been resolved: ntfs: reject non-resident records for resident-only attributes The shared lookup-time attribute validator rejects non-resident $FILENAME and $VOLUMENAME records because their formats require resident values and callers handle...
CVE-2026-72197 fs/ntfs3: bound DeleteIndexEntryAllocation memmove length
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In doaction's DeleteIndexEntryAllocation case, e-size comes from an on-disk INDEXBUFFER entry. When e-size makes e + e-size point past hdr + hdr-used, PtrOffsete1,...
EUVD-2026-58955
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In doaction's DeleteIndexEntryAllocation case, e-size comes from an on-disk INDEXBUFFER entry. When e-size makes e + e-size point past hdr + hdr-used, PtrOffsete1,...
CVE-2026-72195
CVE-2026-72195 concerns Linux kernel ntfs3: UpdateResidentValue may underflow data_size when attr_off/redo_len derive from on-disk LRH and aoff + dlen
CVE-2026-72190
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix mreclock ABBA deadlock in rename ntfsfilefsync, ntfsdirfsync and ntfswriteinode lock an inode's mreclock before taking the mreclock of its parent directory. ntfsrename takes oldni-mreclock and olddirni-mreclock before...
CVE-2026-72158
CVE-2026-72158 concerns the Linux kernel’s FPGA DFH handling in the dfl driver. The flaw: dfh_get_param_size() could report a parameter size larger than the feature region because the loop bounds check ran before incrementing size, and if EOP was set in the same iteration, an inflated size bypass...
EUVD-2026-58916
In the Linux kernel, the following vulnerability has been resolved: fpga: dfl: add bounds check in dfhgetparamsize dfhgetparamsize can return a parameter size larger than the feature region because the loop bounds check is evaluated before incrementing size. If the EOP End of Parameters bit is se...
CVE-2026-72157 net: thunderbolt: Fix frags[] overflow by bounding frame_count
In the Linux kernel, the following vulnerability has been resolved: net: thunderbolt: Fix frags overflow by bounding framecount tbnetpoll assembles a multi-frame ThunderboltIP packet into one skb. The first frame goes into the skb linear area and every further frame is added as a page fragment...
CVE-2026-72155
In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: swp: Improve locking user experience In the case of the first block being locked or the few first blocks, if the user want to fully unlock the device it has two possibilities: - either it asks to unlock the entire...
EUVD-2026-58914
In the Linux kernel, the following vulnerability has been resolved: fpga: microchip-spi: fix zero headersize OOB read in mpfopsparseheader mpfopsparseheader reads headersize from the bitstream at MPFHEADERSIZEOFFSET 24. When headersize is zero, the expression buf + headersize - 1 reads one byte...
CVE-2026-72134
In the Linux kernel, the following vulnerability has been resolved: spi: imx: reconfigure for PIO when DMA cannot be started When spiimxcandma selects DMA, the ECSPI is configured for DMA: spiimxsetupxfer sets CTRL.SMC and clears dynamicburst, and spiimxdmatransfer programs the dynamic-burst...
EUVD-2026-58887
In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: handle inline data with a nonzero offset nvmetrdmauseinlinesg maps the host-controlled inline data offset into the per-command inline scatterlist. The bounds check admits any offset with off + len offset = off;...
CVE-2026-72119
Summary: CVE-2026-72119 concerns a Linux kernel CAN subsystem issue in bcm_tx_lock usage during data and timer updates. The fix stages new CAN frame content for an existing tx operation into a kmalloc() buffer, validates it there, and only copies validated data into op->frames while holding op...
EUVD-2026-58877
In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcmtxlock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc'd buffer and validate it there, mirroring the approach already used in bcmrxsetup. Only copy the validat...
CVE-2026-72119 can: bcm: extend bcm_tx_lock usage for data and timer updates
In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcmtxlock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc'd buffer and validate it there, mirroring the approach already used in bcmrxsetup. Only copy the validat...
EUVD-2026-59072
In the Linux kernel, the following vulnerability has been resolved: can: bcm: validate frame length in bcmrxsetup for RTR replies bcmtxsetup validates cf-len against the CAN/CAN FD DLC limits before installing frames for TXSETUP, but bcmrxsetup never did the same for the RTR-reply frame configure...
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...