p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-aws-fips · Seite 81

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6962

  1. CVE-2026-68142

    Hoch · CVSS 8.8EPSS 0,12%Keine Korrektur veröffentlicht

    geneve: require CAP_NET_ADMIN in the device netns for changelink

    In the Linux kernel, the following vulnerability has been resolved: geneve: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the sticky underlay netns geneve->net. They differ once the device is created in or moved to a netns other than the one the request runs in. The rtnl changelink path checks CAP_NET_ADMIN only against dev_net(dev), so a caller privileged there but not in geneve->net can rewrite a geneve device whose underlay lives in geneve->net. geneve_changelink() applies the new configuration against geneve->net: geneve_link_config() and the geneve_quiesc

    Veröffentlicht Aktualisiert
  2. CVE-2026-68141

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

    net/af_iucv: fix NULL deref in afiucv_hs_callback_syn()

    In the Linux kernel, the following vulnerability has been resolved: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() afiucv_hs_callback_syn() allocates the child socket with GFP_ATOMIC. If the allocation fails, nsk is NULL. The connection-refused path is entered when the listen state check fails, the accept backlog is full, or nsk is NULL. The code unconditionally calls iucv_sock_kill(nsk) in that path. iucv_sock_kill() does not accept a NULL socket pointer and immediately dereferences sk via sock_flag(sk, SOCK_ZAPPED). When nsk is NULL, calling iucv_sock_kill(nsk) results in a NULL pointer dereference. Only call iucv_sock_kill()

    Veröffentlicht Aktualisiert
  3. CVE-2026-68140

    Hoch · CVSS 8.8EPSS 0,27%Keine Korrektur veröffentlicht

    net/iucv: fix use-after-free of a severed iucv_path

    In the Linux kernel, the following vulnerability has been resolved: net/iucv: fix use-after-free of a severed iucv_path af_iucv queues not-yet-received message notifications on iucv->message_q, each holding a raw pointer to the connection's iucv_path. When the peer severs the connection, iucv_sever_path() frees that path with iucv_path_free() but leaves the notifications queued. A later recvmsg() drains message_q via iucv_process_message_q() and hands the stale path to message_receive() -- a use-after-free of the freed iucv_path. Drop the queued notifications when the path is severed; once the path is gone they can no longer be received.

    Veröffentlicht Aktualisiert
  4. CVE-2026-68135

    Nicht bewertetEPSS 0,18%Keine Korrektur veröffentlicht

    net: hip04: fix RX buffer leak on build_skb failure

    In the Linux kernel, the following vulnerability has been resolved: net: hip04: fix RX buffer leak on build_skb failure When build_skb() fails in hip04_rx_poll(), the driver jumps to the refill path without releasing the current RX buffer and its DMA mapping. Installing a replacement buffer then overwrites the slot references and leaks both resources. Keep the current slot intact and return budget so NAPI retries the same buffer. Also free a newly allocated RX fragment when dma_map_single() fails. This issue was found by an in-house static analysis tool.

    Veröffentlicht Aktualisiert
  5. CVE-2026-68127

    Kritisch · CVSS 9.8EPSS 0,54%Keine Korrektur veröffentlicht

    ila: reload IPv6 header after pskb_may_pull in checksum adjust

    In the Linux kernel, the following vulnerability has been resolved: ila: reload IPv6 header after pskb_may_pull in checksum adjust ila_csum_adjust_transport() caches ip6h = ipv6_hdr(skb) before calling pskb_may_pull(). On a non-linear skb whose transport header sits in a page fragment, pskb_may_pull() can call __pskb_pull_tail() / pskb_expand_head() and free the old skb head, leaving ip6h dangling; the following get_csum_diff(ip6h, p) then reads freed memory. ila_update_ipv6_locator() uses ip6h (and the iaddr derived from it) again after the csum-adjust call and additionally writes the new locator through that pointer. Impact: a remote IPv

    Veröffentlicht Aktualisiert
  6. CVE-2026-68125

    Hoch · CVSS 8.8EPSS 0,32%Keine Korrektur veröffentlicht

    mac802154: llsec: reject frames shorter than the authentication tag

    In the Linux kernel, the following vulnerability has been resolved: mac802154: llsec: reject frames shorter than the authentication tag llsec_do_decrypt_auth() computes the associated-data length for the AEAD request as assoclen += datalen - authlen; where datalen is the number of bytes after the MAC header and authlen (4, 8 or 16) is the length of the authentication tag. Nothing verifies that the frame actually carries at least authlen payload bytes. A secured frame whose payload is shorter than the tag makes datalen - authlen negative; assoclen is then passed to aead_request_set_ad() as an unsigned value close to 4 GiB, so crypto_aead_

    Veröffentlicht Aktualisiert
  7. CVE-2026-68123

    Kritisch · CVSS 9.8EPSS 0,55%Keine Korrektur veröffentlicht

    openvswitch: fix GSO userspace truncation underflow

    In the Linux kernel, the following vulnerability has been resolved: openvswitch: fix GSO userspace truncation underflow OVS_ACTION_ATTR_TRUNC currently stores a delta from the original skb length in OVS_CB(skb)->cutlen. When a later userspace action segments a GSO skb, queue_gso_packets() reuses that delta for each smaller segment. A segment can then reach queue_userspace_packet() with cutlen greater than skb->len, underflowing the length passed to skb_zerocopy(). Store the maximum preserved length instead and bound each consumer against the current skb length. Use U32_MAX as the no-truncation sentinel so the value remains valid if skb geo

    Veröffentlicht Aktualisiert
  8. CVE-2026-68121

    Hoch · CVSS 7.8EPSS 0,37%Öffentlicher ExploitKeine Korrektur veröffentlicht

    pppoe: reload header pointer after dev_hard_header()

    In the Linux kernel, the following vulnerability has been resolved: pppoe: reload header pointer after dev_hard_header() pppoe_sendmsg() saves a pointer to the PPPoE header before calling dev_hard_header(). Device header callbacks are allowed to reallocate the skb head, invalidating pointers into it. This can happen when a send is blocked in copy_from_user() while the first non-Ethernet port is added to an empty team device. The team's delegated GRE header callback then expands the skb head. PPPoE subsequently writes six bytes through the stale pointer into the freed head. Reload the PPPoE header through the skb's network-header offset af

    Veröffentlicht Aktualisiert
  9. CVE-2026-68118

    Hoch · CVSS 8.2EPSS 0,4%Keine Korrektur veröffentlicht

    tcp: challenge ACK for non-exact RST in SYN-RECEIVED

    In the Linux kernel, the following vulnerability has been resolved: tcp: challenge ACK for non-exact RST in SYN-RECEIVED The SYN-RECEIVED request-socket path in tcp_check_req() accepts an in-window RST without requiring SEG.SEQ to exactly match RCV.NXT. A non-exact RST therefore removes the request instead of eliciting a challenge ACK. RFC 9293 section 3.10.7.4 applies the RFC 5961 reset check in SYN-RECEIVED: an exact RST resets the connection, while a non-exact in-window RST must trigger a challenge ACK and be dropped. Apply that check before the ACK-field validation, following the RFC sequence-number, RST, then ACK processing order.

    Veröffentlicht Aktualisiert
  10. CVE-2026-68115

    Nicht bewertetEPSS 0,18%Keine Korrektur veröffentlicht

    drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit ac6f00beb658239bced4aaed9efbb04a35348d48)

    Veröffentlicht Aktualisiert
  11. CVE-2026-68114

    Mittel · CVSS 6.8EPSS 0,15%Keine Korrektur veröffentlicht

    drm/amdgpu/gfx12.1: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx12.1: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit e4d99e04b2e9b13b97d3b17804c735f62689db23)

    Veröffentlicht Aktualisiert
  12. CVE-2026-68113

    Mittel · CVSS 6.8EPSS 0,17%Keine Korrektur veröffentlicht

    drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit f952076f76d62f783e8ba4995a7c400d39354ccf)

    Veröffentlicht Aktualisiert
  13. CVE-2026-68112

    Mittel · CVSS 6.8EPSS 0,17%Keine Korrektur veröffentlicht

    drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit 5676593d08998d7a6d9e2d51d6b54b3820e3755c)

    Veröffentlicht Aktualisiert
  14. CVE-2026-68111

    Nicht bewertetEPSS 0,18%Keine Korrektur veröffentlicht

    drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit b71604f8685b0eba07866f4e8dc30f93e1931054)

    Veröffentlicht Aktualisiert
  15. CVE-2026-68110

    Mittel · CVSS 6.8EPSS 0,17%Keine Korrektur veröffentlicht

    drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit fa4f86a148271e325e95287630a3a15a9cd35fdc)

    Veröffentlicht Aktualisiert
  16. CVE-2026-68109

    Mittel · CVSS 6.8EPSS 0,15%Keine Korrektur veröffentlicht

    drm/amdgpu/sdma7.1: replace BUG_ON() with WARN_ON()

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/sdma7.1: replace BUG_ON() with WARN_ON() There's no need to crash the kernel for these cases. (cherry picked from commit c4f230b51cf2d3e7e8b1c800331f3dbed2a9e3f5)

    Veröffentlicht Aktualisiert
  17. CVE-2026-68108

    Hoch · CVSS 8.8EPSS 0,14%Keine Korrektur veröffentlicht

    drm/amdgpu/vce: fix integer overflow in image size

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce: fix integer overflow in image size Fix a security vulnerability where malicious VCE command streams with oversized dimensions (e.g. 65536×65536) cause 32-bit integer overflow, wrapping the calculated buffer size to 0. This bypasses validation and allows GPU firmware to perform out-of-bound memory access. The fix uses 64-bit arithmetic to detect overflow and rejects invalid dimensions before they reach the hardware. V2: remove redundant check V3: modify max height value V4: remove size64 (cherry picked from commit cbe408dba581755ad1279a487ec786d8927d778d)

    Veröffentlicht Aktualisiert
  18. CVE-2026-68107

    Hoch · CVSS 8.8EPSS 0,1%Keine Korrektur veröffentlicht

    drm/amdgpu/vcn4: avoid rereading IB param length

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn4: avoid rereading IB param length Reuse the parameter length returned by vcn_v4_0_enc_find_ib_param() instead of rereading it from the IB. This avoids a potential TOCTOU issue if the IB contents change between reads. (cherry picked from commit dbb02b4755f8c1f3773263f2d779872c1c0c073a)

    Veröffentlicht Aktualisiert
  19. CVE-2026-68106

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

    drm/amdgpu: fix division by zero with invalid uvd dimensions

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix division by zero with invalid uvd dimensions When width or height is less than 16, width_in_mb or height_in_mb becomes 0, leading to fs_in_mb being 0. This causes a division by zero when calculating num_dpb_buffer in H264 and H264 Perf decode paths. Add validation to reject frames with width < 16 or height < 16 before performing any calculations that depend on these values. V2: Format change - move up all vaiable definitions. V3: Use warn_once to avoid spam. (cherry picked from commit 3e41d26c70b0a459d041cc19482a226c4b7423cb)

    Veröffentlicht Aktualisiert
  20. CVE-2026-68105

    Nicht bewertetEPSS 0,17%Keine Korrektur veröffentlicht

    drm/amdgpu: Fix kernel panic during driver load failure

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix kernel panic during driver load failure Avoid kernel panic if MES init fails during driver load. The KIQ ring is falsely marked as ready as ASICs that use MES, KIQ is owned by MES. BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:gfx_v12_1_wait_reg_mem+0x5a/0x1f0 [amdgpu] Call Trace: gfx_v12_1_ring_emit_reg_write_reg_wait+0x1f/0x30 [amdgpu] amdgpu_gmc_fw_reg_write_reg_wait+0xb2/0x190 [amdgpu] amdgpu_gmc_flush_gpu_tlb+0x1cc/0x230 [amdgpu] amdgpu_gart_invalidate_tlb+0x81/0xa0 [amdgpu] amdgpu_gart_unbind+0x72/0x90 [amdgpu] amdgpu

    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 →