suse/kernel-default-base&distro=SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS

Vulnerabilities (2,843)

• CVE-2022-49381MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_do_fill_super If jffs2_iget() or d_make_root() in jffs2_do_fill_super() returns an error, we can observe the following kmemleak report: -----------------------------------------

• CVE-2022-49379MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: driver core: Fix wait_for_device_probe() & deferred_probe_timeout interaction Mounting NFS rootfs was timing out when deferred_probe_timeout was non-zero [1]. This was because ip_auto_config() initcall times o

• CVE-2022-49378MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: sfc: fix considering that all channels have TX queues Normally, all channels have RX and TX queues, but this is not true if modparam efx_separate_tx_channels=1 is used. In that cases, some channels only have RX

• CVE-2022-49377HigFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: blk-mq: don't touch ->tagset in blk_mq_get_sq_hctx blk_mq_run_hw_queues() could be run when there isn't queued request and after queue is cleaned up, at that time tagset is freed, because tagset lifetime is cov

• CVE-2022-49376MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: scsi: sd: Fix potential NULL pointer dereference If sd_probe() sees an early error before sdkp->device is initialized, sd_zbc_release_disk() is called. This causes a NULL pointer dereference when sd_is_zoned()

• CVE-2022-49375MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: rtc: mt6397: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value.

• CVE-2022-49373MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() in some e

• CVE-2022-49371MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock holding logic is as follows: ... __device_attach device_lock(dev) // get lock dev async_schedule_dev(__device_attach_asy

• CVE-2022-49370MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error,

• CVE-2022-49368HigFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: out of bounds read in mtk_hwlro_get_fdir_entry() The "fsp->location" variable comes from user via ethtool_get_rxnfc(). Check that it is valid to prevent an out of bounds read.

• CVE-2022-49367MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. mv88e6xxx_mdio_register(

• CVE-2022-49357MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: efi: Do not import certificates from UEFI Secure Boot for T2 Macs On Apple T2 Macs, when Linux attempts to read the db and dbx efi variables at early boot to load UEFI Secure Boot certificates, a page fault occ

• CVE-2022-49356CriFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Trap RDMA segment overflows Prevent svc_rdma_build_writes() from walking off the end of a Write chunk's segment array. Caught with KASAN. The test that this fix replaces is invalid, and might have been

• CVE-2022-49354MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore. Add missing put_device() to avoid refcount lea

• CVE-2022-49352MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: fix warning in ext4_handle_inode_extension We got issue as follows: EXT4-fs error (device loop0) in ext4_reserve_inode_write:5741: Out of memory EXT4-fs error (device loop0): ext4_setattr:5462: inode #13:

• CVE-2022-49351MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: net: altera: Fix refcount leak in altera_tse_mdio_create Every iteration of for_each_child_of_node() decrements the reference count of the previous node. When break from a for_each_child_of_node() loop, we need

• CVE-2022-49350MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotate

• CVE-2022-49349HigFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_rename_dir_prepare We got issue as follows: EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue ext4_get_first_dir_block: bh->b_data=0xffff88810bee6000 l

• CVE-2022-49348MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state The EXT4_FC_REPLAY bit in sbi->s_mount_state is used to indicate that we are in the middle of replay the fast commit journal. This was actu

• CVE-2022-49347MedFeb 26, 2025
  affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

  In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in ext4_writepages we got issue as follows: EXT4-fs error (device loop0): ext4_mb_generate_buddy:1141: group 0, block bitmap and bg descriptor inconsistent: 25 vs 31513 free cls ------------[ c