p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости linux-fips · Страница 200

За последние 30 дней в linux-fips опубликовано уязвимостей: 266; в каталоге KEV: 0.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 5095

  1. CVE-2024-36886

    Критический · CVSS 9.8EPSS 1,31%Нет опубликованного исправления

    tipc: fix UAF in error path

    In the Linux kernel, the following vulnerability has been resolved: tipc: fix UAF in error path Sam Page (sam4k) working with Trend Micro Zero Day Initiative reported a UAF in the tipc_buf_append() error path: BUG: KASAN: slab-use-after-free in kfree_skb_list_reason+0x47e/0x4c0 linux/net/core/skbuff.c:1183 Read of size 8 at addr ffff88804d2a7c80 by task poc/8034 CPU: 1 PID: 8034 Comm: poc Not tainted 6.8.2 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-debian-1.16.0-5 04/01/2014 Call Trace: <IRQ> __dump_stack linux/lib/dump_stack.c:88 dump_stack_lvl+0xd9/0x1b0 linux/lib/dump_stack.c:106 print_address_description

  2. CVE-2024-36883

    Высокий · CVSS 7.8EPSS 0,31%Нет опубликованного исправления

    net: fix out-of-bounds access in ops_init

    In the Linux kernel, the following vulnerability has been resolved: net: fix out-of-bounds access in ops_init net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is read twice, first to allocate an array, then to set s.len, which is later used to limit the bounds of the array access. It is possible that the array is allocated and another thread is registering a new pernet ops, increments max_gen_ptrs, which is then used to set s.len with a larger than allocated length for the variable array. Fix it by reading max_gen_ptrs only once in net_alloc_g

  3. CVE-2024-36880

    Высокий · CVSS 7.8EPSS 0,25%Нет опубликованного исправления

    Bluetooth: qca: add missing firmware sanity checks

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: qca: add missing firmware sanity checks Add the missing sanity checks when parsing the firmware files before downloading them to avoid accessing and corrupting memory beyond the vmalloced buffer.

  4. CVE-2024-36016

    Высокий · CVSS 7.8EPSS 0,27%Нет опубликованного исправления

    tty: n_gsm: fix possible out-of-bounds in gsm0_receive()

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() Assuming the following: - side A configures the n_gsm in basic option mode - side B sends the header of a basic option mode frame with data length 1 - side A switches to advanced option mode - side B sends 2 data bytes which exceeds gsm->len Reason: gsm->len is not used in advanced option mode. - side A switches to basic option mode - side B keeps sending until gsm0_receive() writes past gsm->buf Reason: Neither gsm->state nor gsm->len have been reset after reconfiguration. Fix this by changing gsm->count to gs

  5. CVE-2023-52881

    Критический · CVSS 9.8EPSS 0,61%Нет опубликованного исправления

    tcp: do not accept ACK of bytes we never sent

    In the Linux kernel, the following vulnerability has been resolved: tcp: do not accept ACK of bytes we never sent This patch is based on a detailed report and ideas from Yepeng Pan and Christian Rossow. ACK seq validation is currently following RFC 5961 5.2 guidelines: The ACK value is considered acceptable only if it is in the range of ((SND.UNA - MAX.SND.WND) <= SEG.ACK <= SND.NXT). All incoming segments whose ACK value doesn't satisfy the above condition MUST be discarded and an ACK sent back. It needs to be noted that RFC 793 on page 72 (fifth check) says: "If the ACK is a duplicate (SEG.ACK < SND.UNA), it can be i

  6. CVE-2023-52880

    Высокий · CVSS 7.8EPSS 0,24%Нет опубликованного исправления

    tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc

    In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc Any unprivileged user can attach N_GSM0710 ldisc, but it requires CAP_NET_ADMIN to create a GSM network anyway. Require initial namespace CAP_NET_ADMIN to do that.

  7. CVE-2021-47571

    Высокий · CVSS 7.8EPSS 0,21%Нет опубликованного исправления

    staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()

    In the Linux kernel, the following vulnerability has been resolved: staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() The free_rtllib() function frees the "dev" pointer so there is use after free on the next line. Re-arrange things to avoid that.

  8. CVE-2021-47566

    Высокий · CVSS 7.8EPSS 0,23%Нет опубликованного исправления

    proc/vmcore: fix clearing user buffer by properly using clear_user()

    In the Linux kernel, the following vulnerability has been resolved: proc/vmcore: fix clearing user buffer by properly using clear_user() To clear a user buffer we cannot simply use memset, we have to use clear_user(). With a virtio-mem device that registers a vmcore_cb and has some logically unplugged memory inside an added Linux memory block, I can easily trigger a BUG by copying the vmcore via "cp": systemd[1]: Starting Kdump Vmcore Save Service... kdump[420]: Kdump is using the default log level(3). kdump[453]: saving to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[458]: saving vmcore-dmesg.txt to /sysroot/var/crash/

  9. CVE-2021-47565

    Высокий · CVSS 7.8EPSS 0,23%Нет опубликованного исправления

    scsi: mpt3sas: Fix kernel panic during drive powercycle test

    In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix kernel panic during drive powercycle test While looping over shost's sdev list it is possible that one of the drives is getting removed and its sas_target object is freed but its sdev object remains intact. Consequently, a kernel panic can occur while the driver is trying to access the sas_address field of sas_target object without also checking the sas_target object for NULL.

  10. CVE-2021-47547

    Средний · CVSS 4.4EPSS 0,23%Нет опубликованного исправления

    net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound

    In the Linux kernel, the following vulnerability has been resolved: net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound In line 5001, if all id in the array 'lp->phy[8]' is not 0, when the 'for' end, the 'k' is 8. At this time, the array 'lp->phy[8]' may be out of bound.

  11. CVE-2021-47544

    Критический · CVSS 9.8EPSS 0,86%Нет опубликованного исправления

    tcp: fix page frag corruption on page fault

    In the Linux kernel, the following vulnerability has been resolved: tcp: fix page frag corruption on page fault Steffen reported a TCP stream corruption for HTTP requests served by the apache web-server using a cifs mount-point and memory mapping the relevant file. The root cause is quite similar to the one addressed by commit 20eb4f29b602 ("net: fix sk_page_frag() recursion from memory reclaim"). Here the nested access to the task page frag is caused by a page fault on the (mmapped) user-space memory buffer coming from the cifs file. The page fault handler performs an smb transaction on a different socket, inside the same process context

  12. CVE-2021-47542

    Средний · CVSS 5.6EPSS 0,25%Нет опубликованного исправления

    net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings()

    In the Linux kernel, the following vulnerability has been resolved: net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings() In qlcnic_83xx_add_rings(), the indirect function of ahw->hw_ops->alloc_mbx_args will be called to allocate memory for cmd.req.arg, and there is a dereference of it in qlcnic_83xx_add_rings(), which could lead to a NULL pointer dereference on failure of the indirect function like qlcnic_83xx_alloc_mbx_args(). Fix this bug by adding a check of alloc_mbx_args(), this patch imitates the logic of mbx_cmd()'s failure handling. This bug was found by a static analyzer. The analysis employs differentia

  13. CVE-2021-47521

    Высокий · CVSS 7.8EPSS 0,24%Нет опубликованного исправления

    can: sja1000: fix use after free in ems_pcmcia_add_card()

    In the Linux kernel, the following vulnerability has been resolved: can: sja1000: fix use after free in ems_pcmcia_add_card() If the last channel is not available then "dev" is freed. Fortunately, we can just use "pdev->irq" instead. Also we should check if at least one channel was set up.

  14. CVE-2021-47520

    Высокий · CVSS 8.8EPSS 0,34%Нет опубликованного исправления

    can: pch_can: pch_can_rx_normal: fix use after free

    In the Linux kernel, the following vulnerability has been resolved: can: pch_can: pch_can_rx_normal: fix use after free After calling netif_receive_skb(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is dereferenced just after the call netif_receive_skb(skb). Reordering the lines solves the issue.

  15. CVE-2021-47518

    Средний · CVSS 5.7EPSS 0,24%Нет опубликованного исправления

    nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done

    In the Linux kernel, the following vulnerability has been resolved: nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done The done() netlink callback nfc_genl_dump_ses_done() should check if received argument is non-NULL, because its allocation could fail earlier in dumpit() (nfc_genl_dump_ses()).

  16. CVE-2021-47511

    Средний · CVSS 5.5EPSS 0,24%Нет опубликованного исправления

    ALSA: pcm: oss: Fix negative period/buffer sizes

    In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Fix negative period/buffer sizes The period size calculation in OSS layer may receive a negative value as an error, but the code there assumes only the positive values and handle them with size_t. Due to that, a too big value may be passed to the lower layers. This patch changes the code to handle with ssize_t and adds the proper error checks appropriately.

  17. CVE-2021-47509

    Средний · CVSS 5.5EPSS 0,24%Нет опубликованного исправления

    ALSA: pcm: oss: Limit the period size to 16MB

    In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: oss: Limit the period size to 16MB Set the practical limit to the period size (the fragment shift in OSS) instead of a full 31bit; a too large value could lead to the exhaust of memory as we allocate temporary buffers of the period size, too. As of this patch, we set to 16MB limit, which should cover all use cases.

  18. CVE-2021-47506

    Критический · CVSS 9.8EPSS 0,78%Нет опубликованного исправления

    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

  19. CVE-2021-47501

    Средний · CVSS 5.5EPSS 0,24%Нет опубликованного исправления

    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.

  20. CVE-2021-47500

    Высокий · CVSS 7.8EPSS 0,24%Нет опубликованного исправления

    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.

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →