p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux · Seite 160

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux: 252. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4217

  1. CVE-2021-47435

    Mittel · CVSS 4.7EPSS 0,24%Keine Korrektur veröffentlicht

    dm: fix mempool NULL pointer race when completing IO

    In the Linux kernel, the following vulnerability has been resolved: dm: fix mempool NULL pointer race when completing IO dm_io_dec_pending() calls end_io_acct() first and will then dec md in-flight pending count. But if a task is swapping DM table at same time this can result in a crash due to mempool->elements being NULL: task1 task2 do_resume ->do_suspend ->dm_wait_for_completion bio_endio ->clone_endio ->dm_io_dec_pending ->end_io_acct ->wakeup task1 ->dm_swap_table ->__bind ->__bind_mempools ->bioset_exit ->mempool_exit

    Veröffentlicht Aktualisiert
  2. CVE-2021-47434

    Mittel · CVSS 5.5EPSS 0,24%Keine Korrektur veröffentlicht

    xhci: Fix command ring pointer corruption while aborting a command

    In the Linux kernel, the following vulnerability has been resolved: xhci: Fix command ring pointer corruption while aborting a command The command ring pointer is located at [6:63] bits of the command ring control register (CRCR). All the control bits like command stop, abort are located at [0:3] bits. While aborting a command, we read the CRCR and set the abort bit and write to the CRCR. The read will always give command ring pointer as all zeros. So we essentially write only the control bits. Since we split the 64 bit write into two 32 bit writes, there is a possibility of xHC command ring stopped before the upper dword (all zeros) is wri

    Veröffentlicht Aktualisiert
  3. CVE-2023-52878

    Mittel · CVSS 5.5EPSS 0,24%Keine Korrektur veröffentlicht

    can: dev: can_put_echo_skb(): don't crash kernel if can_priv::echo_skb is accessed out of bounds

    In the Linux kernel, the following vulnerability has been resolved: can: dev: can_put_echo_skb(): don't crash kernel if can_priv::echo_skb is accessed out of bounds If the "struct can_priv::echoo_skb" is accessed out of bounds, this would cause a kernel crash. Instead, issue a meaningful warning message and return with an error.

    Veröffentlicht Aktualisiert
  4. CVE-2023-52868

    Hoch · CVSS 7.8EPSS 0,24%Keine Korrektur veröffentlicht

    thermal: core: prevent potential string overflow

    In the Linux kernel, the following vulnerability has been resolved: thermal: core: prevent potential string overflow The dev->id value comes from ida_alloc() so it's a number between zero and INT_MAX. If it's too high then these sprintf()s will overflow.

    Veröffentlicht Aktualisiert
  5. CVE-2023-52843

    Mittel · CVSS 5.5EPSS 0,24%Keine Korrektur veröffentlicht

    llc: verify mac len before reading mac header

    In the Linux kernel, the following vulnerability has been resolved: llc: verify mac len before reading mac header LLC reads the mac header with eth_hdr without verifying that the skb has an Ethernet header. Syzbot was able to enter llc_rcv on a tun device. Tun can insert packets without mac len and with user configurable skb->protocol (passing a tun_pi header when not configuring IFF_NO_PI). BUG: KMSAN: uninit-value in llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline] BUG: KMSAN: uninit-value in llc_station_rcv+0x6fb/0x1290 net/llc/llc_station.c:111 llc_station_ac_send_test_r net/llc/llc_station.c:81 [inline] ll

    Veröffentlicht Aktualisiert
  6. CVE-2023-52834

    Hoch · CVSS 7.5EPSS 0,65%Keine Korrektur veröffentlicht

    atl1c: Work around the DMA RX overflow issue

    In the Linux kernel, the following vulnerability has been resolved: atl1c: Work around the DMA RX overflow issue This is based on alx driver commit 881d0327db37 ("net: alx: Work around the DMA RX overflow issue"). The alx and atl1c drivers had RX overflow error which was why a custom allocator was created to avoid certain addresses. The simpler workaround then created for alx driver, but not for atl1c due to lack of tester. Instead of using a custom allocator, check the allocated skb address and use skb_reserve() to move away from problematic 0x...fc0 address. Tested on AR8131 on Acer 4540.

    Veröffentlicht Aktualisiert
  7. CVE-2023-52813

    Mittel · CVSS 5.5EPSS 0,29%Keine Korrektur veröffentlicht

    crypto: pcrypt - Fix hungtask for PADATA_RESET

    In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix hungtask for PADATA_RESET We found a hungtask bug in test_aead_vec_cfg as follows: INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kth

    Veröffentlicht Aktualisiert
  8. CVE-2023-52811

    Mittel · CVSS 5.5EPSS 0,25%Keine Korrektur veröffentlicht

    scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool

    In the Linux kernel, the following vulnerability has been resolved: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool In practice the driver should never send more commands than are allocated to a queue's event pool. In the unlikely event that this happens, the code asserts a BUG_ON, and in the case that the kernel is not configured to crash on panic returns a junk event pointer from the empty event list causing things to spiral from there. This BUG_ON is a historical artifact of the ibmvfc driver first being upstreamed, and it is well known now that the use of BUG_ON is bad practice except in the most unrecoverable scenario. T

    Veröffentlicht Aktualisiert
  9. CVE-2023-52810

    Hoch · CVSS 7.8EPSS 0,26%Keine Korrektur veröffentlicht

    fs/jfs: Add check for negative db_l2nbperpage

    In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add check for negative db_l2nbperpage l2nbperpage is log2(number of blks per page), and the minimum legal value should be 0, not negative. In the case of l2nbperpage being negative, an error will occur when subsequently used as shift exponent. Syzbot reported this bug: UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:799:12 shift exponent -16777216 is negative

    Veröffentlicht Aktualisiert
  10. CVE-2023-52809

    Mittel · CVSS 6EPSS 0,25%Keine Korrektur veröffentlicht

    scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()

    In the Linux kernel, the following vulnerability has been resolved: scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() fc_lport_ptp_setup() did not check the return value of fc_rport_create() which can return NULL and would cause a NULL pointer dereference. Address this issue by checking return value of fc_rport_create() and log error message on fc_rport_create() failed.

    Veröffentlicht Aktualisiert
  11. CVE-2023-52806

    Mittel · CVSS 5.5EPSS 0,26%Keine Korrektur veröffentlicht

    ALSA: hda: Fix possible null-ptr-deref when assigning a stream

    In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix possible null-ptr-deref when assigning a stream While AudioDSP drivers assign streams exclusively of HOST or LINK type, nothing blocks a user to attempt to assign a COUPLED stream. As supplied substream instance may be a stub, what is the case when code-loading, such scenario ends with null-ptr-deref.

    Veröffentlicht Aktualisiert
  12. CVE-2023-52805

    Hoch · CVSS 7.8EPSS 0,26%Keine Korrektur veröffentlicht

    jfs: fix array-index-out-of-bounds in diAlloc

    In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in diAlloc Currently there is not check against the agno of the iag while allocating new inodes to avoid fragmentation problem. Added the check which is required.

    Veröffentlicht Aktualisiert
  13. CVE-2023-52804

    Hoch · CVSS 7.8EPSS 0,26%Keine Korrektur veröffentlicht

    fs/jfs: Add validity check for db_maxag and db_agpref

    In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add validity check for db_maxag and db_agpref Both db_maxag and db_agpref are used as the index of the db_agfree array, but there is currently no validity check for db_maxag and db_agpref, which can lead to errors. The following is related bug reported by Syzbot: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:639:20 index 7936 is out of range for type 'atomic_t[128]' Add checking that the values of db_maxag and db_agpref are valid indexes for the db_agfree array.

    Veröffentlicht Aktualisiert
  14. CVE-2023-52803

    Mittel · CVSS 5.5EPSS 0,24%Keine Korrektur veröffentlicht

    SUNRPC: Fix RPC client cleaned up the freed pipefs dentries

    In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix RPC client cleaned up the freed pipefs dentries RPC client pipefs dentries cleanup is in separated rpc_remove_pipedir() workqueue,which takes care about pipefs superblock locking. In some special scenarios, when kernel frees the pipefs sb of the current client and immediately alloctes a new pipefs sb, rpc_remove_pipedir function would misjudge the existence of pipefs sb which is not the one it used to hold. As a result, the rpc_remove_pipedir would clean the released freed pipefs dentries. To fix this issue, rpc_remove_pipedir should check whether the current p

    Veröffentlicht Aktualisiert
  15. CVE-2023-52799

    Hoch · CVSS 7.8EPSS 0,26%Keine Korrektur veröffentlicht

    jfs: fix array-index-out-of-bounds in dbFindLeaf

    In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in dbFindLeaf Currently while searching for dmtree_t for sufficient free blocks there is an array out of bounds while getting element in tp->dm_stree. To add the required check for out of bound we first need to determine the type of dmtree. Thus added an extra parameter to dbFindLeaf so that the type of tree can be determined and the required check can be applied.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →