Comment 2 for bug 1997384

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-azure-5.4 - 5.4.0-1098.104~18.04.2

---------------
linux-azure-5.4 (5.4.0-1098.104~18.04.2) bionic; urgency=medium

  * bionic/linux-azure-5.4: 5.4.0-1098.104~18.04.2 -proposed tracker
    (LP: #1997384)

  [ Ubuntu: 5.4.0-1098.104 ]

  * focal/linux-azure: 5.4.0-1098.104 -proposed tracker (LP: #1997385)
  * focal/linux: 5.4.0-135.152 -proposed tracker (LP: #1997412)
  * containerd sporadic timeouts (LP: #1996678)
    - epoll: call final ep_events_available() check under the lock
    - epoll: check for events when removing a timed out thread from the wait queue
    - Revert "fs: check FMODE_LSEEK to control internal pipe splicing"
  * CVE-2022-3621
    - nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
  * CVE-2022-3565
    - mISDN: fix use-after-free bugs in l1oip timer handlers
  * CVE-2022-3566
    - tcp: Fix data races around icsk->icsk_af_ops.
  * CVE-2022-3567
    - ipv6: annotate some data-races around sk->sk_prot
    - ipv6: Fix data races around sk->sk_prot.
  * CVE-2022-3564
    - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu
  * CVE-2022-3524
    - tcp/udp: Fix memory leak in ipv6_renew_options().
  * CVE-2022-3594
    - r8152: Rate limit overflow messages
  * CVE-2022-42703
    - mm/rmap.c: don't reuse anon_vma if we just want a copy

 -- Thadeu Lima de Souza Cascardo <email address hidden> Tue, 29 Nov 2022 08:41:33 -0300