p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-ibm · Page n° 105

Vulnérabilité publiée pour linux-ibm au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 3088

  1. CVE-2021-47506

    Critique · CVSS 9.8EPSS 0,78%Correctif disponible

    nfsd: fix use-after-free due to delegation race

    In the Linux kernel, the following vulnerability has been resolved: nfsd: fix use-after-free due to delegation race A delegation break could arrive as soon as we've called vfs_setlease. A delegation break runs a callback which immediately (in nfsd4_cb_recall_prepare) adds the delegation to del_recall_lru. If we then exit nfs4_set_delegation without hashing the delegation, it will be freed as soon as the callback is done with it, without ever being removed from del_recall_lru. Symptoms show up later as use-after-free or list corruption warnings, usually in the laundromat thread. I suspect aba2072f4523 "nfsd: grant read delegations to cli

    • Mettez à jour vers 5.4.0-1018.20
    Publication Mise à jour
  2. CVE-2021-47505

    Élevée · CVSS 7.8EPSS 0,25%Correctif disponible

    aio: fix use-after-free due to missing POLLFREE handling

    In the Linux kernel, the following vulnerability has been resolved: aio: fix use-after-free due to missing POLLFREE handling signalfd_poll() and binder_poll() are special in that they use a waitqueue whose lifetime is the current task, rather than the struct file as is normally the case. This is okay for blocking polls, since a blocking poll occurs within one task; however, non-blocking polls require another solution. This solution is for the queue to be cleared before it is freed, by sending a POLLFREE notification to all waiters. Unfortunately, only eventpoll handles POLLFREE. A second type of non-blocking poll, aio poll, was added in

    • Mettez à jour vers 5.4.0-1015.16
    Publication Mise à jour
  3. CVE-2021-47501

    Moyenne · CVSS 5.5EPSS 0,24%Correctif disponible

    i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc

    In the Linux kernel, the following vulnerability has been resolved: i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc When trying to dump VFs VSI RX/TX descriptors using debugfs there was a crash due to NULL pointer dereference in i40e_dbg_dump_desc. Added a check to i40e_dbg_dump_desc that checks if VSI type is correct for dumping RX/TX descriptors.

    • Mettez à jour vers 5.4.0-1083.88
    Publication Mise à jour
  4. CVE-2021-47500

    Élevée · CVSS 7.8EPSS 0,24%Correctif disponible

    iio: mma8452: Fix trigger reference couting

    In the Linux kernel, the following vulnerability has been resolved: iio: mma8452: Fix trigger reference couting The mma8452 driver directly assigns a trigger to the struct iio_dev. The IIO core when done using this trigger will call `iio_trigger_put()` to drop the reference count by 1. Without the matching `iio_trigger_get()` in the driver the reference count can reach 0 too early, the trigger gets freed while still in use and a use-after-free occurs. Fix this by getting a reference to the trigger before assigning it to the IIO device.

    • Mettez à jour vers 5.4.0-1015.16
    Publication Mise à jour
  5. CVE-2021-47499

    Moyenne · CVSS 5.5EPSS 0,24%Correctif disponible

    iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove

    In the Linux kernel, the following vulnerability has been resolved: iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove When ACPI type is ACPI_SMO8500, the data->dready_trig will not be set, the memory allocated by iio_triggered_buffer_setup() will not be freed, and cause memory leak as follows: unreferenced object 0xffff888009551400 (size 512): comm "i2c-SMO8500-125", pid 911, jiffies 4294911787 (age 83.852s) hex dump (first 32 bytes): 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 20 e2 e5 c0 ff ff ff ff ........ ....... backtrace: [<0000000041ce75ee>] kmem_ca

    • Mettez à jour vers 5.4.0-1015.16
    Publication Mise à jour
  6. CVE-2021-47497

    Élevée · CVSS 7.8EPSS 0,22%Correctif disponible

    nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells

    In the Linux kernel, the following vulnerability has been resolved: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells If a cell has 'nbits' equal to a multiple of BITS_PER_BYTE the logic *p &= GENMASK((cell->nbits%BITS_PER_BYTE) - 1, 0); will become undefined behavior because nbits modulo BITS_PER_BYTE is 0, and we subtract one from that making a large number that is then shifted more than the number of bits that fit into an unsigned long. UBSAN reports this problem: UBSAN: shift-out-of-bounds in drivers/nvmem/core.c:1386:8 shift exponent 64 is too large for 64-bit type 'unsigned long' CPU: 6 PID: 7 Comm: kworker/u16:0 Not

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour
  7. CVE-2021-47496

    Critique · CVSS 9.8EPSS 0,48%Correctif disponible

    net/tls: Fix flipped sign in tls_err_abort() calls

    In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix flipped sign in tls_err_abort() calls sk->sk_err appears to expect a positive value, a convention that ktls doesn't always follow and that leads to memory corruption in other code. For instance, [kworker] tls_encrypt_done(..., err=<negative error from crypto request>) tls_err_abort(.., err) sk->sk_err = err; [task] splice_from_pipe_feed ... tls_sw_do_sendpage if (sk->sk_err) { ret = -sk->sk_err; // ret is positive splice_from_pipe_feed (continued) ret = actor(...) // ret is still p

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour
  8. CVE-2021-47485

    Élevée · CVSS 7.8EPSS 0,24%Correctif disponible

    IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields

    In the Linux kernel, the following vulnerability has been resolved: IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields Overflowing either addrlimit or bytes_togo can allow userspace to trigger a buffer overflow of kernel memory. Check for overflows in all the places doing math on user controlled buffers.

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour
  9. CVE-2021-47483

    Élevée · CVSS 7.8EPSS 0,23%Correctif disponible

    regmap: Fix possible double-free in regcache_rbtree_exit()

    In the Linux kernel, the following vulnerability has been resolved: regmap: Fix possible double-free in regcache_rbtree_exit() In regcache_rbtree_insert_to_block(), when 'present' realloc failed, the 'blk' which is supposed to assign to 'rbnode->block' will be freed, so 'rbnode->block' points a freed memory, in the error handling path of regcache_rbtree_init(), 'rbnode->block' will be freed again in regcache_rbtree_exit(), KASAN will report double-free as follows: BUG: KASAN: double-free or invalid-free in kfree+0xce/0x390 Call Trace: slab_free_freelist_hook+0x10d/0x240 kfree+0xce/0x390 regcache_rbtree_exit+0x15d/0x1a0 regcache_rbtree_

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour
  10. CVE-2021-47482

    Moyenne · CVSS 5.3EPSS 0,74%Correctif disponible

    net: batman-adv: fix error handling

    In the Linux kernel, the following vulnerability has been resolved: net: batman-adv: fix error handling Syzbot reported ODEBUG warning in batadv_nc_mesh_free(). The problem was in wrong error handling in batadv_mesh_init(). Before this patch batadv_mesh_init() was calling batadv_mesh_free() in case of any batadv_*_init() calls failure. This approach may work well, when there is some kind of indicator, which can tell which parts of batadv are initialized; but there isn't any. All written above lead to cleaning up uninitialized fields. Even if we hide ODEBUG warning by initializing bat_priv->nc.work, syzbot was able to hit GPF in batadv_nc_

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour
  11. CVE-2021-47480

    Moyenne · CVSS 5.5EPSS 0,21%Correctif disponible

    scsi: core: Put LLD module refcnt after SCSI device is released

    In the Linux kernel, the following vulnerability has been resolved: scsi: core: Put LLD module refcnt after SCSI device is released SCSI host release is triggered when SCSI device is freed. We have to make sure that the low-level device driver module won't be unloaded before SCSI host instance is released because shost->hostt is required in the release handler. Make sure to put LLD module refcnt after SCSI device is released. Fixes a kernel panic of 'BUG: unable to handle page fault for address' reported by Changhui and Yi.

    • Mettez à jour vers 5.4.0-1013.14
    Publication Mise à jour
  12. CVE-2021-47478

    Critique · CVSS 9.1EPSS 0,69%Correctif disponible

    isofs: Fix out of bound access for corrupted isofs image

    In the Linux kernel, the following vulnerability has been resolved: isofs: Fix out of bound access for corrupted isofs image When isofs image is suitably corrupted isofs_read_inode() can read data beyond the end of buffer. Sanity-check the directory entry length before using it.

    • Mettez à jour vers 5.4.0-1013.14
    Publication Mise à jour
  13. CVE-2021-47477

    Moyenne · CVSS 5.3EPSS 0,72%Correctif disponible

    comedi: dt9812: fix DMA buffers on stack

    In the Linux kernel, the following vulnerability has been resolved: comedi: dt9812: fix DMA buffers on stack USB transfer buffers are typically mapped for DMA and must not be allocated on the stack or transfers will fail. Allocate proper transfer buffers in the various command helpers and return an error on short transfers instead of acting on random stack data. Note that this also fixes a stack info leak on systems where DMA is not used as 32 bytes are always sent to the device regardless of how short the command is.

    • Mettez à jour vers 5.4.0-1013.14
    Publication Mise à jour
  14. CVE-2021-47476

    Moyenne · CVSS 4.6EPSS 0,39%Correctif disponible

    comedi: ni_usb6501: fix NULL-deref in command paths

    In the Linux kernel, the following vulnerability has been resolved: comedi: ni_usb6501: fix NULL-deref in command paths The driver uses endpoint-sized USB transfer buffers but had no sanity checks on the sizes. This can lead to zero-size-pointer dereferences or overflowed transfer buffers in ni6501_port_command() and ni6501_counter_command() if a (malicious) device has smaller max-packet sizes than expected (or when doing descriptor fuzz testing). Add the missing sanity checks to probe().

    • Mettez à jour vers 5.4.0-1013.14
    Publication Mise à jour
  15. CVE-2021-47475

    Élevée · CVSS 7.8EPSS 0,26%Correctif disponible

    comedi: vmk80xx: fix transfer-buffer overflows

    In the Linux kernel, the following vulnerability has been resolved: comedi: vmk80xx: fix transfer-buffer overflows The driver uses endpoint-sized USB transfer buffers but up until recently had no sanity checks on the sizes. Commit e1f13c879a7c ("staging: comedi: check validity of wMaxPacketSize of usb endpoints found") inadvertently fixed NULL-pointer dereferences when accessing the transfer buffers in case a malicious device has a zero wMaxPacketSize. Make sure to allocate buffers large enough to handle also the other accesses that are done without a size check (e.g. byte 18 in vmk80xx_cnt_insn_read() for the VMK8061_MODEL) to avoid writ

    • Mettez à jour vers 5.4.0-1013.14
    Publication Mise à jour
  16. CVE-2021-47474

    Élevée · CVSS 7.8EPSS 0,26%Correctif disponible

    comedi: vmk80xx: fix bulk-buffer overflow

    In the Linux kernel, the following vulnerability has been resolved: comedi: vmk80xx: fix bulk-buffer overflow The driver is using endpoint-sized buffers but must not assume that the tx and rx buffers are of equal size or a malicious device could overflow the slab-allocated receive buffer when doing bulk transfers.

    • Mettez à jour vers 5.4.0-1013.14
    Publication Mise à jour
  17. CVE-2021-47468

    Moyenne · CVSS 5.5EPSS 0,18%Correctif disponible

    isdn: mISDN: Fix sleeping function called from invalid context

    In the Linux kernel, the following vulnerability has been resolved: isdn: mISDN: Fix sleeping function called from invalid context The driver can call card->isac.release() function from an atomic context. Fix this by calling this function after releasing the lock. The following log reveals it: [ 44.168226 ] BUG: sleeping function called from invalid context at kernel/workqueue.c:3018 [ 44.168941 ] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 5475, name: modprobe [ 44.169574 ] INFO: lockdep is turned off. [ 44.169899 ] irq event stamp: 0 [ 44.170160 ] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 44.17062

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour
  18. CVE-2021-47466

    Moyenne · CVSS 5.5EPSS 0,21%Correctif disponible

    mm, slub: fix potential memoryleak in kmem_cache_open()

    In the Linux kernel, the following vulnerability has been resolved: mm, slub: fix potential memoryleak in kmem_cache_open() In error path, the random_seq of slub cache might be leaked. Fix this by using __kmem_cache_release() to release all the relevant resources.

    • Mettez à jour vers 5.4.0-1010.11
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →