p PatchFirst

PatchFirst · Latest vulnerabilities

linux-ibm-5.15 vulnerabilities · Page 21

Vulnerabilities published for linux-ibm-5.15 in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 2543

  1. CVE-2023-53400

    Medium · CVSS 5.5EPSS 0.15%Fix available

    ALSA: hda: Fix Oops by 9.1 surround channel names

    In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix Oops by 9.1 surround channel names get_line_out_pfx() may trigger an Oops by overflowing the static array with more than 8 channels. This was reported for MacBookPro 12,1 with Cirrus codec. As a workaround, extend for the 9.1 channels and also fix the potential Oops by unifying the code paths accessing the same array with the proper size check.

    • Update to 5.15.0-1037.40~20.04.1
    Published Updated
  2. CVE-2023-53399

    High · CVSS 7.5EPSS 0.29%Fix available

    ksmbd: fix NULL pointer dereference in smb2_get_info_filesystem()

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix NULL pointer dereference in smb2_get_info_filesystem() If share is , share->path is NULL and it cause NULL pointer dereference issue.

    • Update to 5.15.0-1036.39~20.04.1
    Published Updated
  3. CVE-2023-53396

    Medium · CVSS 5.5EPSS 0.15%Fix available

    ubifs: Fix memory leak in do_rename

    In the Linux kernel, the following vulnerability has been resolved: ubifs: Fix memory leak in do_rename If renaming a file in an encrypted directory, function fscrypt_setup_filename allocates memory for a file name. This name is never used, and before returning to the caller the memory for it is not freed. When running kmemleak on it we see that it is registered as a leak. The report below is triggered by a simple program 'rename' that renames a file in an encrypted directory: unreferenced object 0xffff888101502840 (size 32): comm "rename", pid 9404, jiffies 4302582475 (age 435.735s) backtrace: __kmem_cache_alloc_node

    • Update to 5.15.0-1037.40~20.04.1
    Published Updated
  4. CVE-2023-53395

    High · CVSS 7.8EPSS 0.16%Fix available

    ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer

    In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer ACPICA commit 90310989a0790032f5a0140741ff09b545af4bc5 According to the ACPI specification 19.6.134, no argument is required to be passed for ASL Timer instruction. For taking care of no argument, AML_NO_OPERAND_RESOLVE flag is added to ASL Timer instruction opcode. When ASL timer instruction interpreted by ACPI interpreter, getting error. After adding AML_NO_OPERAND_RESOLVE flag to ASL Timer instruction opcode, issue is not observed. ============================================================= UBSAN: array-index-out-of-b

    • Update to 5.15.0-1046.49~20.04.1
    Published Updated
  5. CVE-2023-53391

    Medium · CVSS 5.5EPSS 0.15%Fix available

    shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs

    In the Linux kernel, the following vulnerability has been resolved: shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs As the ramfs-based tmpfs uses ramfs_init_fs_context() for the init_fs_context method, which allocates fc->s_fs_info, use ramfs_kill_sb() to free it and avoid a memory leak.

    • Update to 5.15.0-1040.43~20.04.1
    Published Updated
  6. CVE-2023-53390

    Medium · CVSS 5.5EPSS 0.15%Fix available

    drivers: base: dd: fix memory leak with using debugfs_lookup()

    In the Linux kernel, the following vulnerability has been resolved: drivers: base: dd: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once.

    • Update to 5.15.0-1036.39~20.04.1
    Published Updated
  7. CVE-2023-53386

    High · CVSS 7.8EPSS 0.15%Fix available

    Bluetooth: Fix potential use-after-free when clear keys

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix potential use-after-free when clear keys Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call.

    • Update to 5.15.0-1046.49~20.04.1
    Published Updated
  8. CVE-2023-53384

    Medium · CVSS 5.5EPSS 0.15%Fix available

    wifi: mwifiex: avoid possible NULL skb pointer dereference

    In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: avoid possible NULL skb pointer dereference In 'mwifiex_handle_uap_rx_forward()', always check the value returned by 'skb_copy()' to avoid potential NULL pointer dereference in 'mwifiex_uap_queue_bridged_pkt()', and drop original skb in case of copying failure. Found by Linux Verification Center (linuxtesting.org) with SVACE.

    • Update to 5.15.0-1046.49~20.04.1
    Published Updated
  9. CVE-2023-53381

    High · CVSS 7.5EPSS 0.29%Fix available

    NFSD: fix leaked reference count of nfsd4_ssc_umount_item

    In the Linux kernel, the following vulnerability has been resolved: NFSD: fix leaked reference count of nfsd4_ssc_umount_item The reference count of nfsd4_ssc_umount_item is not decremented on error conditions. This prevents the laundromat from unmounting the vfsmount of the source file. This patch decrements the reference count of nfsd4_ssc_umount_item on error.

    • Update to 5.15.0-1058.61~20.04.1
    Published Updated
  10. CVE-2023-53380

    Medium · CVSS 5.5EPSS 0.15%Fix available

    md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request

    In the Linux kernel, the following vulnerability has been resolved: md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request There are two check of 'mreplace' in raid10_sync_request(). In the first check, 'need_replace' will be set and 'mreplace' will be used later if no-Faulty 'mreplace' exists, In the second check, 'mreplace' will be set to NULL if it is Faulty, but 'need_replace' will not be changed accordingly. null-ptr-deref occurs if Faulty is set between two check. Fix it by merging two checks into one. And replace 'need_replace' with 'mreplace' because their values are always the same.

    • Update to 5.15.0-1040.43~20.04.1
    Published Updated
  11. CVE-2023-53379

    Medium · CVSS 5.5EPSS 0.15%Fix available

    usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe()

    In the Linux kernel, the following vulnerability has been resolved: usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Smatch reports: drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe() warn: missing unwind goto? After geting irq, if ret < 0, it will return without error handling to free memory. Just add error handling to fix this problem.

    • Update to 5.15.0-1040.43~20.04.1
    Published Updated
  12. CVE-2023-53375

    Medium · CVSS 5.5EPSS 0.16%Fix available

    tracing: Free error logs of tracing instances

    In the Linux kernel, the following vulnerability has been resolved: tracing: Free error logs of tracing instances When a tracing instance is removed, the error messages that hold errors that occurred in the instance needs to be freed. The following reports a memory leak: # cd /sys/kernel/tracing # mkdir instances/foo # echo 'hist:keys=x' > instances/foo/events/sched/sched_switch/trigger # cat instances/foo/error_log [ 117.404795] hist:sched:sched_switch: error: Couldn't find field Command: hist:keys=x ^ # rmdir instances/foo Then check for memory leaks: # echo scan > /sys/kernel/debug/kmemleak # cat /sys

    • Update to 5.15.0-1036.39~20.04.1
    Published Updated
  13. CVE-2023-53372

    High · CVSS 8.2EPSS 0.39%Fix available

    sctp: fix a potential overflow in sctp_ifwdtsn_skip

    In the Linux kernel, the following vulnerability has been resolved: sctp: fix a potential overflow in sctp_ifwdtsn_skip Currently, when traversing ifwdtsn skips with _sctp_walk_ifwdtsn, it only checks the pos against the end of the chunk. However, the data left for the last pos may be < sizeof(struct sctp_ifwdtsn_skip), and dereference it as struct sctp_ifwdtsn_skip may cause coverflow. This patch fixes it by checking the pos against "the end of the chunk - sizeof(struct sctp_ifwdtsn_skip)" in sctp_ifwdtsn_skip, similar to sctp_fwdtsn_skip.

    • Update to 5.15.0-1036.39~20.04.1
    Published Updated
  14. CVE-2023-53369

    Medium · CVSS 5.5EPSS 0.18%Fix available

    net: dcb: choose correct policy to parse DCB_ATTR_BCN

    In the Linux kernel, the following vulnerability has been resolved: net: dcb: choose correct policy to parse DCB_ATTR_BCN The dcbnl_bcn_setcfg uses erroneous policy to parse tb[DCB_ATTR_BCN], which is introduced in commit 859ee3c43812 ("DCB: Add support for DCB BCN"). Please see the comment in below code static int dcbnl_bcn_setcfg(...) { ... ret = nla_parse_nested_deprecated(..., dcbnl_pfc_up_nest, .. ) // !!! dcbnl_pfc_up_nest for attributes // DCB_PFC_UP_ATTR_0 to DCB_PFC_UP_ATTR_ALL in enum dcbnl_pfc_up_attrs ... for (i = DCB_BCN_ATTR_RP_0; i <= DCB_BCN_ATTR_RP_7; i++) { // !!! DCB_BCN_ATTR_RP_0 to DCB_BCN_ATTR_RP_7 in e

    • Update to 5.15.0-1042.45~20.04.1
    Published Updated
  15. CVE-2023-53368

    Medium · CVSS 4.7EPSS 0.14%Fix available

    tracing: Fix race issue between cpu buffer write and swap

    In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race issue between cpu buffer write and swap Warning happened in rb_end_commit() at code: if (RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))) WARNING: CPU: 0 PID: 139 at kernel/trace/ring_buffer.c:3142 rb_commit+0x402/0x4a0 Call Trace: ring_buffer_unlock_commit+0x42/0x250 trace_buffer_unlock_commit_regs+0x3b/0x250 trace_event_buffer_commit+0xe5/0x440 trace_event_buffer_reserve+0x11c/0x150 trace_event_raw_event_sched_switch+0x23c/0x2c0 __traceiter_sched_switch+0x59/0x80 __schedule+0x72b/0x1580 schedule+0x92/0x120 w

    • Update to 5.15.0-1046.49~20.04.1
    Published Updated
  16. CVE-2023-53365

    Medium · CVSS 5.5EPSS 0.19%Fix available

    ip6mr: Fix skb_under_panic in ip6mr_cache_report()

    In the Linux kernel, the following vulnerability has been resolved: ip6mr: Fix skb_under_panic in ip6mr_cache_report() skbuff: skb_under_panic: text:ffffffff88771f69 len:56 put:-4 head:ffff88805f86a800 data:ffff887f5f86a850 tail:0x88 end:0x2c0 dev:pim6reg ------------[ cut here ]------------ kernel BUG at net/core/skbuff.c:192! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 2 PID: 22968 Comm: kworker/2:11 Not tainted 6.5.0-rc3-00044-g0a8db05b571a #236 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:skb_panic+0x152/0x1d0 Call Trace: <TASK> skb

    • Update to 5.15.0-1042.45~20.04.1
    Published Updated
  17. CVE-2023-53359

    Medium · CVSS 5.5EPSS 0.19%Fix available

    USB: fix memory leak with using debugfs_lookup()

    In the Linux kernel, the following vulnerability has been resolved: USB: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once.

    • Update to 5.15.0-1036.39~20.04.1
    Published Updated
  18. CVE-2023-53358

    High · CVSS 8.8EPSS 0.38%Fix available

    ksmbd: fix racy issue under cocurrent smb2 tree disconnect

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix racy issue under cocurrent smb2 tree disconnect There is UAF issue under cocurrent smb2 tree disconnect. This patch introduce TREE_CONN_EXPIRE flags for tcon to avoid cocurrent access.

    • Update to 5.15.0-1050.53~20.04.1
    Published Updated
  19. CVE-2023-53357

    High · CVSS 7.1EPSS 0.2%Fix available

    md/raid10: check slab-out-of-bounds in md_bitmap_get_counter

    In the Linux kernel, the following vulnerability has been resolved: md/raid10: check slab-out-of-bounds in md_bitmap_get_counter If we write a large number to md/bitmap_set_bits, md_bitmap_checkpage() will return -EINVAL because 'page >= bitmap->pages', but the return value was not checked immediately in md_bitmap_get_counter() in order to set *blocks value and slab-out-of-bounds occurs. Move check of 'page >= bitmap->pages' to md_bitmap_get_counter() and return directly if true.

    • Update to 5.15.0-1040.43~20.04.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →