This bug was fixed in the package linux-aws - 5.4.0-1136.146

---------------
linux-aws (5.4.0-1136.146) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1136.146 -proposed tracker (LP: #2086406)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log

  * [AWS]  Fix interrupt mappings which are set to a bad default after certain
    ENI operations (LP: #2085159)
    - genirq: Provide new interfaces for affinity hints
    - UBUNTU SAUCE: (no-up) linux/ena: Add NUMA aware interrupt allocation

  [ Ubuntu: 5.4.0-202.222 ]

  * focal/linux: 5.4.0-202.222 -proposed tracker (LP: #2086451)
    - [Packaging] resync git-ubuntu-log
  * CVE-2021-47501
    - i40e: Fix NULL pointer dereference in i40e_dbg_dump_desc
  * CVE-2024-46724
    - drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number
  * CVE-2024-42240
    - x86/bhi: Avoid warning in #DB handler due to BHI mitigation
  * CVE-2024-42077
    - ocfs2: fix DIO failure due to insufficient transaction credits
  * CVE-2024-42068
    - bpf: Take return from set_memory_ro() into account with bpf_prog_lock_ro()
  * CVE-2024-36968
    - Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()
  * CVE-2024-35904
    - selinux: avoid dereference of garbage after mount failure
  * CVE-2023-52498
    - PM: sleep: Avoid calling put_device() under dpm_list_mtx
    - PM: sleep: Fix error handling in dpm_prepare()
    - async: Split async_schedule_node_domain()
    - async: Introduce async_schedule_dev_nocall()
    - PM: sleep: Fix possible deadlocks in core system-wide PM code
  * CVE-2023-52488
    - serial: sc16is7xx: convert from _raw_ to _noinc_ regmap functions for FIFO
  * CVE-2022-48938
    - CDC-NCM: avoid overflow in sanity checking
  * CVE-2024-42156
    - s390/pkey: Wipe copies of clear-key structures on failure
  * CVE-2024-44942
    - f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC
  * CVE-2024-38538
    - net: bridge: xmit: make sure we have at least eth header len bytes
  * CVE-2021-47076
    - RDMA/rxe: Return CQE error if invalid lkey was supplied
  * CVE-2024-36938
    - bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue
  * CVE-2024-44940
    - fou: remove warn in gue_gro_receive on unsupported protocol
  * CVE-2024-35951
    - drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr()
  * CVE-2023-52497
    - erofs: fix lz4 inplace decompression
  * CVE-2024-36953
    - KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr()
  * CVE-2022-48943
    - KVM: x86/mmu: make apf token non-zero to fix bug
  * CVE-2024-26947
    - ARM: 9359/1: flush: check if the folio is reserved for no-mapping 
addresses
  * CVE-2022-48733
    - btrfs: fix use-after-free after failure to create a snapshot
  * CVE-2023-52639
    - KVM: s390: vsie: fix race during shadow creation

 -- Philip Cox <[email protected]>  Tue, 12 Nov 2024 12:46:44
-0500

** Changed in: linux-aws (Ubuntu Focal)
       Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-47076

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-47501

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-48733

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-48938

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-48943

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52488

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52497

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52498

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52639

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26947

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-35904

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-35951

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-36938

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-36953

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-36968

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-38538

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-42068

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-42077

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-42156

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-42240

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-44940

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-44942

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2085159

Title:
  [AWS]  Fix interrupt mappings which are set to a bad default after
  certain ENI operations

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Released
Status in linux-aws source package in Oracular:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]
  Interrupt mapping is set to a bad default after certain ENI operations

  After using ethtool to update the (rx) ring buffer settings on an ENI,
  the interrupt CPU affinity for all tx-rx queues is reset to a bad
  default - CPU 0-31 - even if the ENI is on a different CPU socket
  (NUMA node). Another operation that causes the interrupt mapping to be
  reset to CPU 0-31 is moving an interface to a network namespace.

  [Fix]

  ENA driver version 2.12.3g. They mentioned that this commit in the ENA
  code looks like it addresses the bug: https://github.com/amzn/amzn-
  drivers/commit/ed7754cdf6ca0d4fb3d76906abc17718cc3ffa23

  It's included starting in driver version 2.12.0.

  I have back ported the patch from the AWS OOT driver, as well as any
  existing prerequisites needed.

  [Test Plan]

  I have tested this, as has AWS.

  [Where problems could occur]

  As this is an Ubuntu Sauce patch, if these changes make their was into
  the stable trees, or any patches touching this area of code,  they may
  cause merge conflicts, or changes in behaviour which are unexpected.

  
  [Other]
  SF# f00396266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2085159/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to