p PatchFirst

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

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

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

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

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

  1. CVE-2026-46220

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

    drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission sdma_v4_0_ring_emit_fence() contains two BUG_ON(addr & 0x3) assertions that verify fence writeback addresses are dword-aligned. These assertions can be reached from unprivileged userspace via crafted DRM_IOCTL_AMDGPU_CS submissions, causing a fatal kernel panic in a scheduler worker thread. Replace both BUG_ON() calls with WARN_ON() to log the condition without crashing the kernel. A misaligned fence address at this point indicates a driver bug, but crashing the kernel is never the correct response when the

  2. CVE-2026-46219

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

    spi: mpc52xx: fix use-after-free on unbind

    In the Linux kernel, the following vulnerability has been resolved: spi: mpc52xx: fix use-after-free on unbind The state machine work is scheduled by the interrupt handler and therefore needs to be cancelled after disabling interrupts to avoid a potential use-after-free.

  3. CVE-2026-46218

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

    drm/amdgpu: Add bounds checking to ib_{get,set}_value

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Add bounds checking to ib_{get,set}_value The uvd/vce/vcn code accesses the IB at predefined offsets without checking that the IB is large enough. Check the bounds here. The caller is responsible for making sure it can handle arbitrary return values. Also make the idx a uint32_t to prevent overflows causing the condition to fail.

  4. CVE-2026-46212

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

    batman-adv: bla: prevent use-after-free when deleting claims

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: prevent use-after-free when deleting claims When batadv_bla_del_backbone_claims() removes all claims for a backbone, it does this by dropping the link entry in the hash list. This list entry itself was one of the references which need to be dropped at the same time via batadv_claim_put(). But the batadv_claim_put() must not be done before the last access to the claim object in this function. Otherwise the claim might be freed already by the batadv_claim_release() function before the list entry was dropped.

  5. CVE-2026-46209

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

    drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()

    In the Linux kernel, the following vulnerability has been resolved: drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs() drm_gem_fb_init_with_funcs() computes sub-sampled plane dimensions using plain integer division: unsigned int width = mode_cmd->width / (i ? info->hsub : 1); unsigned int height = mode_cmd->height / (i ? info->vsub : 1); However, the ioctl-level framebuffer_check() in drm_framebuffer.c uses drm_format_info_plane_width/height() which round up dimensions via DIV_ROUND_UP(). This inconsistency corrupts the subsequent GEM object size check for certain pixel format and dimension combina

  6. CVE-2026-46208

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

    batman-adv: stop tp_meter sessions during mesh teardown

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: stop tp_meter sessions during mesh teardown TP meter sessions remain linked on bat_priv->tp_list after the netlink request has already finished. When the mesh interface is removed, batadv_mesh_free() currently tears down the mesh without first draining these sessions. A running sender thread or a late incoming tp_meter packet can then keep processing against a mesh instance which is already shutting down. Synchronize tp_meter with the mesh lifetime by stopping all active sessions from batadv_mesh_free() and waiting for sender threads to exit before teardown con

  7. CVE-2026-46206

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

    batman-adv: reject new tp_meter sessions during teardown

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: reject new tp_meter sessions during teardown Prevent tp_meter from starting new sender or receiver sessions after mesh_state has left BATADV_MESH_ACTIVE.

  8. CVE-2026-46205

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

    staging: media: atomisp: Disallow all private IOCTLs

    In the Linux kernel, the following vulnerability has been resolved: staging: media: atomisp: Disallow all private IOCTLs Disallow all private IOCTLs. These aren't quite as safe as one could assume of IOCTL handlers; disable them for now. Instead of removing the code, return in the beginning of the function if cmd is non-zero in order to keep static checkers happy.

  9. CVE-2026-46200

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

    spi: mpc52xx: fix controller deregistration

    In the Linux kernel, the following vulnerability has been resolved: spi: mpc52xx: fix controller deregistration Make sure to deregister the controller before disabling and releasing underlying resources like interrupts and gpios during driver unbind.

  10. CVE-2026-46198

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

    batman-adv: fix integer overflow on buff_pos

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix integer overflow on buff_pos Fixing an integer overflow present in batadv_iv_ogm_send_to_if. The size check is done using the int type in batadv_iv_ogm_aggr_packet whereas the buff_pos variable uses the s16 type. This could lead to an out-of-bound read.

  11. CVE-2026-46196

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

    tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func()

    In the Linux kernel, the following vulnerability has been resolved: tracepoint: balance regfunc() on func_add() failure in tracepoint_add_func() When a tracepoint goes through the 0 -> 1 transition, tracepoint_add_func() invokes the subsystem's ext->regfunc() before attempting to install the new probe via func_add(). If func_add() then fails (for example, when allocate_probes() cannot allocate a new probe array under memory pressure and returns -ENOMEM), the function returns the error without calling the matching ext->unregfunc(), leaving the side effects of regfunc() behind with no installed probe to justify them. For syscall tracepoints

  12. CVE-2026-46193

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

    xfrm: ah: account for ESN high bits in async callbacks

    In the Linux kernel, the following vulnerability has been resolved: xfrm: ah: account for ESN high bits in async callbacks AH allocates its temporary auth/ICV layout differently when ESN is enabled: the async ahash setup appends a 4-byte seqhi slot before the ICV or auth_data area, but the async completion callbacks still reconstruct the temporary layout as if seqhi were absent. With an async AH implementation selected, that makes AH copy or compare the wrong bytes on both the IPv4 and IPv6 paths. In UML repro on IPv4 AH with ESN and forced async hmac(sha1), ping fails with 100% packet loss, and the callback logs show the pre-fix drift:

  13. CVE-2026-46191

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

    fbcon: Avoid OOB font access if console rotation fails

    In the Linux kernel, the following vulnerability has been resolved: fbcon: Avoid OOB font access if console rotation fails Clear the font buffer if the reallocation during console rotation fails in fbcon_rotate_font(). The putcs implementations for the rotated buffer will return early in this case. See [1] for an example. Currently, fbcon_rotate_font() keeps the old buffer, which is too small for the rotated font. Printing to the rotated console with a high-enough character code will overflow the font buffer. v2: - fix typos in commit message

  14. CVE-2026-46189

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

    RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path

    In the Linux kernel, the following vulnerability has been resolved: RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path Sashiko points out that pvrdma_uar_free() is already called within pvrdma_dealloc_ucontext(), so calling it before triggers a double free.

  15. CVE-2026-46187

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

    wifi: rsi: fix kthread lifetime race between self-exit and external-stop

    In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: fix kthread lifetime race between self-exit and external-stop RSI driver use both self-exit(kthread_complete_and_exit) and external-stop (kthread_stop) when killing a kthread. Generally, kthread_stop() is called first, and in this case, no particular issues occur. However, in rare instances where kthread_complete_and_exit() is called first and then kthread_stop() is called, a UAF occurs because the kthread object, which has already exited and been freed, is accessed again. Therefore, to prevent this with minimal modification, you must remove kthread_stop() and

  16. CVE-2026-46184

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

    sound: ua101: fix division by zero at probe

    In the Linux kernel, the following vulnerability has been resolved: sound: ua101: fix division by zero at probe Add a missing sanity check for bNrChannels in detect_usb_format() to prevent a division by zero in playback_urb_complete() and capture_urb_complete(). USB core does not validate class-specific descriptor fields such as bNrChannels, so drivers must verify them before use. If a device provides bNrChannels = 0, frame_bytes becomes zero and is later used as a divisor in the URB completion handlers, leading to a kernel crash.

  17. CVE-2026-46181

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

    RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event()

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() Sashiko points out the radix_tree itself is RCU safe, but nothing ever frees the mlx4_srq struct with RCU, and it isn't even accessed within the RCU critical section. It also will crash if an event is delivered before the srq object is finished initializing. Use the spinlock since it isn't easy to make RCU work, use refcount_inc_not_zero() to protect against partially initialized objects, and order the refcount_set() to be after the srq is fully initialized.

  18. CVE-2026-46180

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

    wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task

    In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix potential use-after-free issue when stopping watchdog task Watchdog task might end between send_sig() and kthread_stop() calls, what results in the use-after-free issue. Fix this by increasing watchdog task reference count before calling send_sig() and dropping it by switching to kthread_stop_put().

  19. CVE-2026-46178

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

    RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq()

    In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix resource leak on error in mlx4_ib_create_srq() Sashiko points out that mlx4_srq_alloc() was not undone during error unwind, add the missing call to mlx4_srq_free().

  20. CVE-2026-46177

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

    ipmi: Add limits to event and receive message requests

    In the Linux kernel, the following vulnerability has been resolved: ipmi: Add limits to event and receive message requests The driver would just fetch events and receive messages until the BMC said it was done. To avoid issues with BMCs that never say they are done, add a limit of 10 fetches at a time. In addition, an si interface has an attn state it can return from the hardware which is supposed to cause a flag fetch to see if the driver needs to fetch events or message or a few other things. If the attn bit gets stuck, it's a similar problem. So allow messages in between flag fetches so the driver itself doesn't get stuck. This is a

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

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

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