p PatchFirst

PatchFirst · Latest vulnerabilities

linux-fips vulnerabilities · Page 152

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

Filter vulnerabilities
Clear filters

Vulnerabilities: 8368

  1. CVE-2026-63957

    High · CVSS 7.8EPSS 0.17%Fix available

    USB: serial: safe_serial: fix memory corruption with small endpoint

    In the Linux kernel, the following vulnerability has been resolved: USB: serial: safe_serial: fix memory corruption with small endpoint Make sure that the bulk-out buffer size is at least eight bytes to avoid user-controlled slab corruption in "safe" mode should a malicious device report a smaller size.

    • Update to 5.15.0-198.208+fips1
    Published Updated
  2. CVE-2026-63956

    High · CVSS 7.8EPSS 0.17%Fix available

    USB: serial: cypress_m8: fix memory corruption with small endpoint

    In the Linux kernel, the following vulnerability has been resolved: USB: serial: cypress_m8: fix memory corruption with small endpoint Make sure that the interrupt-out endpoint max packet size is at least eight bytes to avoid user-controlled slab corruption or NULL-pointer dereference should a malicious device report a smaller size.

    • Update to 5.15.0-198.208+fips1
    Published Updated
  3. CVE-2026-63948

    Medium · CVSS 5.5EPSS 0.16%Fix available

    Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix chan ref leak in l2cap_chan_timeout() on !conn __set_chan_timer() takes a l2cap_chan reference via l2cap_chan_hold() before scheduling the delayed work. The normal path in l2cap_chan_timeout() drops this reference with l2cap_chan_put() at the end, but the early return when chan->conn is NULL skips the put, leaking the reference. Add the missing l2cap_chan_put() before the early return.

    • Update to 5.15.0-198.208+fips1
    Published Updated
  4. CVE-2026-63947

    High · CVSS 8.8EPSS 0.35%Fix available

    Bluetooth: HIDP: fix missing length checks in hidp_input_report()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: fix missing length checks in hidp_input_report() hidp_input_report() reads keyboard and mouse payload data from an skb without first verifying that skb->len contains enough data. hidp_recv_intr_frame() pulls the 1-byte HIDP header before dispatching to hidp_input_report(). If a paired device sends a truncated packet, the handler reads beyond the valid skb data, resulting in an out-of-bounds read of skb data. The OOB bytes may be interpreted as phantom key presses or spurious mouse movement. Replace the open-coded length tracking and pointer arithmetic wit

    • Update to 5.15.0-198.208+fips1
    Published Updated
  5. CVE-2026-63942

    High · CVSS 7.8EPSS 0.13%Fix available

    parport: Fix race between port and client registration

    In the Linux kernel, the following vulnerability has been resolved: parport: Fix race between port and client registration The parport subsystem registers port devices before they are fully initialised, resulting in a race condition where client drivers such as lp can attach to ports that are not completely initialised or even being torn down. When the port and client drivers are built as modules and loaded around the same time during boot, this occasionally results in a crash. I was able to make this happen reliably in a VM with a PC-style parallel port by patching parport_pc to fail probing: > --- a/drivers/parport/parport_pc.c > +++ b

    • Update to 5.15.0-198.208+fips1
    Published Updated
  6. CVE-2026-63940

    Critical · CVSS 9.3EPSS 0.19%No fix published

    KVM: SEV: Ignore Port I/O requests of length '0'

    In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Ignore Port I/O requests of length '0' Explicitly ignore Port I/O requests of length '0' (or count '0'), so that setting up the software scratch area (and other code) doesn't have to worry about underflowing the length, and to allow for WARNing on trying to configure the scratch area with len==0.

    Published Updated
  7. CVE-2026-63934

    High · CVSS 7.1EPSS 0.16%Fix available

    iio: gyro: itg3200: fix i2c read into the wrong stack location

    In the Linux kernel, the following vulnerability has been resolved: iio: gyro: itg3200: fix i2c read into the wrong stack location itg3200_read_all_channels() takes `__be16 *buf' as a parameter and fills the i2c_msg destination as `(char *)&buf'. Since `buf' is the parameter (a pointer), `&buf' is the address of the local pointer slot on the stack of itg3200_read_all_channels(), not the address of the caller's scan buffer. The (char *) cast hides the type mismatch. i2c_transfer() therefore writes ITG3200_SCAN_ELEMENTS * sizeof(s16) = 8 bytes into the parameter's stack slot, which is discarded when the function returns. The caller's scan bu

    • Update to 5.15.0-198.208+fips1
    Published Updated
  8. CVE-2026-63933

    Medium · CVSS 5.5EPSS 0.16%Fix available

    iio: gyro: adis16260: fix division by zero in write_raw

    In the Linux kernel, the following vulnerability has been resolved: iio: gyro: adis16260: fix division by zero in write_raw Add a validation check for the sampling frequency value before using it as a divisor. A user writing zero to the sampling_frequency sysfs attribute triggers a division by zero in the kernel.

    • Update to 5.15.0-198.208+fips1
    Published Updated
  9. CVE-2026-63931

    Medium · CVSS 5.5EPSS 0.16%Fix available

    iio: chemical: scd30: fix division by zero in write_raw

    In the Linux kernel, the following vulnerability has been resolved: iio: chemical: scd30: fix division by zero in write_raw Add a zero check for val2 before using it as a divisor when setting the sampling frequency. A user writing a zero fractional part to the sampling_frequency sysfs attribute triggers a division by zero in the kernel.

    • Update to 5.15.0-198.208+fips1
    Published Updated
  10. CVE-2026-63930

    High · CVSS 7.8EPSS 0.16%Fix available

    iio: buffer: hw-consumer: fix use-after-free in error path

    In the Linux kernel, the following vulnerability has been resolved: iio: buffer: hw-consumer: fix use-after-free in error path In the err_put_buffers cleanup path of iio_hw_consumer_alloc(), the code was using list_for_each_entry() to iterate through buffers while calling iio_buffer_put() which can free the current buffer if refcount drops to 0. The list_for_each_entry() loop macro then evaluates buf->head.next to continue iteration, accessing the freed buffer. Fix this by using list_for_each_entry_safe().

    • Update to 5.15.0-198.208+fips1
    Published Updated
  11. CVE-2026-63928

    High · CVSS 7.8EPSS 0.17%Fix available

    USB: serial: omninet: fix memory corruption with small endpoint

    In the Linux kernel, the following vulnerability has been resolved: USB: serial: omninet: fix memory corruption with small endpoint Make sure that the bulk-out buffers are at least as large as the hardcoded transfer size to avoid user-controlled slab corruption should a malicious device report a smaller endpoint max packet size than expected.

    • Update to 5.15.0-198.208+fips1
    Published Updated
  12. CVE-2026-63926

    High · CVSS 8.4EPSS 0.19%Fix available

    bpf: sockmap: fix tail fragment offset in bpf_msg_push_data

    In the Linux kernel, the following vulnerability has been resolved: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data When bpf_msg_push_data() inserts data in the middle of a scatterlist entry, it splits the original entry into a left fragment and a right fragment. The right fragment offset is page-local, but the code advances it with `start`, which is the message-global insertion point. For inserts into a non-first SG entry, this over-advances the offset and leaves the split layout inconsistent. Advance the right fragment offset by the fragment-local delta, `start - offset`, which matches the length removed from the front of th

    • Update to 5.15.0-198.208+fips1
    Published Updated
  13. CVE-2026-63925

    High · CVSS 8.1EPSS 0.35%Fix available

    macsec: fix replay protection at XPN lower-PN wrap

    In the Linux kernel, the following vulnerability has been resolved: macsec: fix replay protection at XPN lower-PN wrap In macsec_post_decrypt(), when pn is U32_MAX, pn + 1 overflows u32 to 0 and the first branch never fires. If next_pn_halves.lower is also in the upper half, pn_same_half(pn, lower) is true and the XPN else-if does not fire either, leaving next_pn_halves unchanged. An attacker that captures the legitimate frame carrying pn == 0xFFFFFFFF on an XPN association can then replay it indefinitely, since lowest_pn never rises above the captured pn and macsec_decrypt() reconstructs the same IV. Extend the XPN else-if to also fire wh

    • Update to 5.15.0-198.208+fips1
    Published Updated
  14. CVE-2026-63924

    Critical · CVSS 9.8EPSS 0.71%Fix available

    ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo()

    In the Linux kernel, the following vulnerability has been resolved: ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() ipv6_hop_jumbo() calls pskb_trim_rcsum(), which can change skb pointers. Let's recompute nh pointer to make sure any change won't mess things up.

    • Update to 5.15.0-194.204+fips1
    Published Updated
  15. CVE-2026-63922

    Critical · CVSS 9.8EPSS 0.71%Fix available

    ipv6: exthdrs: refresh nh after handling HAO option

    In the Linux kernel, the following vulnerability has been resolved: ipv6: exthdrs: refresh nh after handling HAO option ip6_parse_tlv() caches skb_network_header(skb) in nh while walking IPv6 TLVs. ipv6_dest_hao() may call pskb_expand_head() for a cloned skb, which can move the skb head and invalidate the cached network header pointer. Refresh nh after ipv6_dest_hao() returns so any trailing padding or TLVs are parsed from the current skb head. This matches the existing pattern used in ip6_parse_tlv() after helpers that can modify skb header storage.

    • Update to 5.15.0-194.204+fips1
    Published Updated
  16. CVE-2026-63921

    High · CVSS 8.8EPSS 0.16%Fix available

    ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().

    In the Linux kernel, the following vulnerability has been resolved: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). After patch 1/2 in this series, vti6_update() unlinks and relinks the tunnel through t->net. vti6_siocdevprivate() still uses dev_net(dev) for the collision lookup. For a tunnel moved through IFLA_NET_NS_FD, dev_net(dev) is the new netns, not t->net. SIOCCHGTUNNEL on a migrated tunnel then runs: net = dev_net(dev) /* migrated netns */ t = vti6_locate(net, &p1, false) /* misses target in t->net */ ... t = netdev_priv(dev) vti6_update(t, &p1, false) /* mutates t->net's hash */

    • Update to 5.15.0-198.208+fips1
    Published Updated
  17. CVE-2026-63920

    High · CVSS 7.1EPSS 0.17%Fix available

    ipv6: validate extension header length before copying to cmsg

    In the Linux kernel, the following vulnerability has been resolved: ipv6: validate extension header length before copying to cmsg ip6_datagram_recv_specific_ctl() builds IPV6_{HOPOPTS,DSTOPTS,RTHDR} cmsgs (and their IPV6_2292* legacy counterparts) by trusting the on-wire hdrlen byte (ptr[1]) when computing the put_cmsg() length. The length was validated only at parse time (ipv6_parse_hopopts(), etc.). An nftables payload-write expression can rewrite hdrlen after parsing and before the skb reaches recvmsg; the write itself is in-bounds but put_cmsg() then reads up to ((hdrlen+1) << 3) = 2040 bytes from an 8-byte header. nftables is reachab

    • Update to 5.15.0-198.208+fips1
    Published Updated
  18. CVE-2026-63919

    High · CVSS 8.8EPSS 0.65%Fix available

    xfrm: input: hold netns during deferred transport reinjection

    In the Linux kernel, the following vulnerability has been resolved: xfrm: input: hold netns during deferred transport reinjection Transport-mode reinjection stores a struct net pointer in skb->cb and uses it later from xfrm_trans_reinject(). That pointer must stay valid until the deferred callback runs. Take a netns reference when queueing deferred reinjection work and drop it after the callback completes. Use maybe_get_net() so the queueing path does not revive a namespace that is already being torn down. This keeps the existing workqueue design and fixes the netns lifetime handling in one place for all users of xfrm_trans_queue_net().

    • Update to 5.15.0-198.208+fips1
    Published Updated

Check your server

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

Check your server →