almalinux/kernel-rt-debug-core

Vulnerabilities (1,249)

• CVE-2024-57993MedFeb 27, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check syzbot has found a type mismatch between a USB pipe and the transfer endpoint, which is triggered by the hid-thrustmaster driver

• CVE-2024-57990HigFeb 27, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix off by one in mt7925_load_clc() This comparison should be >= instead of > to prevent an out of bounds read and write.

• CVE-2024-57989MedFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links In mt7925_change_vif_links() devm_kzalloc() may return NULL but this returned value is not checked.

• CVE-2024-57988MedFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btbcm: Fix NULL deref in btbcm_get_board_name() devm_kstrdup() can return a NULL pointer on failure,but this returned value in btbcm_get_board_name() is not checked. Add NULL check in btbcm_get_board

• CVE-2024-57987MedFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: check for NULL in btrtl_setup_realtek() If insert an USB dongle which chip is not maintained in ic_id_table, it will hit the NULL point accessed. Add a null point check to avoid the Kernel Oop

• CVE-2024-57986HigFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections A report in 2019 by the syzbot fuzzer was found to be connected to two errors in the HID core associated with Resolution Mult

• CVE-2024-57984HigFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition In dw_i3c_common_probe, &master->hj_work is bound with dw_i3c_hj_work. And dw_i3c_master_irq_handler can call dw_i3c_master_irq_handle_i

• CVE-2024-57981MedFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix NULL pointer dereference on certain command aborts If a command is queued to the final usable TRB of a ring segment, the enqueue pointer is advanced to the subsequent link TRB and no further. If

• CVE-2024-57980HigFeb 27, 2025
  affected < 4.18.0-553.62.1.rt7.403.el8_10fixed 4.18.0-553.62.1.rt7.403.el8_10

  In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix double free in error path If the uvc_status_init() function fails to allocate the int_urb, it will free the dev->status pointer but doesn't reset the pointer to NULL. This results in the kf

• CVE-2024-57979HigFeb 27, 2025
  affected < 4.18.0-553.44.1.rt7.385.el8_10fixed 4.18.0-553.44.1.rt7.385.el8_10

  In the Linux kernel, the following vulnerability has been resolved: pps: Fix a use-after-free On a board running ntpd and gpsd, I'm seeing a consistent use-after-free in sys_exit() from gpsd when rebooting: pps pps1: removed ------------[ cut here ]------------ kob

• CVE-2024-57977MedFeb 27, 2025
  affected < 6.12.0-124.8.1.el10_1fixed 6.12.0-124.8.1.el10_1

  In the Linux kernel, the following vulnerability has been resolved: memcg: fix soft lockup in the OOM process A soft lockup issue was found in the product with about 56,000 tasks were in the OOM cgroup, it was traversing them when the soft lockup was triggered. watchdog: BUG:

• CVE-2022-49672HigFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: net: tun: unlink NAPI from device on destruction Syzbot found a race between tun file and device destruction. NAPIs live in struct tun_file which can get destroyed before the netdev so we have to del them expli

• CVE-2022-49670HigFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio == 0. CallTrace: Hardware name: H3C R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880

• CVE-2022-49657MedFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: usbnet: fix memory leak in error case usbnet_write_cmd_async() mixed up which buffers need to be freed in which error case. v2: add Fixes tag v3: fix uninitialized buf pointer

• CVE-2022-49648MedFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 ("tracing: fix double free") said, the "double free" problem reported by clang s

• CVE-2022-49643HigFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: ima: Fix a potential integer overflow in ima_appraise_measurement When the ima-modsig is enabled, the rc passed to evm_verifyxattr() may be negative, which may cause the integer overflow problem.

• CVE-2022-49627MedFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid

• CVE-2022-49623HigFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: powerpc/xive/spapr: correct bitmap allocation size kasan detects access beyond the end of the xibm->bitmap allocation: BUG: KASAN: slab-out-of-bounds in _find_first_zero_bit+0x40/0x140 Read of size 8 at addr c

• CVE-2022-49443MedFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses t

• CVE-2022-49437MedFeb 26, 2025
  affected < 5.14.0-611.5.1.el9_7fixed 5.14.0-611.5.1.el9_7

  In the Linux kernel, the following vulnerability has been resolved: powerpc/xive: Fix refcount leak in xive_spapr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid ref