[Kernel-packages] [Bug 1867559] Re: Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed

[Yosha872]

** Tags added: qca9377 wifi

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

Title:
  Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  rafa@acer:~$ sudo lshw -C network
  [sudo] senha para rafa: 
*-network 
 descrição: Ethernet interface
 produto: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 fabricante: Realtek Semiconductor Co., Ltd.
 ID físico: 0.1
 informações do barramento: pci@:01:00.1
 nome lógico: enp1s0f1
 versão: 12
 serial: 08:97:98:63:7d:2e
 capacidade: 1Gbit/s
 largura: 64 bits
 clock: 33MHz
 capacidades: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuração: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8411-2_0.0.1 07/08/13 latency=0 link=no multicast=yes port=MII
 recursos: irq:16 porta de E/S:3000(tamanho=256) 
memória:b1204000-b1204fff memória:b120-b1203fff
*-network
 descrição: Interface sem fio
 produto: QCA9377 802.11ac Wireless Network Adapter
 fabricante: Qualcomm Atheros
 ID físico: 0
 informações do barramento: pci@:02:00.0
 nome lógico: wlp2s0
 versão: 31
 serial: a4:63:a1:0e:bc:42
 largura: 64 bits
 clock: 33MHz
 capacidades: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuração: broadcast=yes driver=ath10k_pci 
driverversion=5.3.0-40-generic firmware=WLAN.TF.2.1-00021-QCARMSWP-1 
ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 recursos: irq:132 memória:b100-b11f


  Download speed around 100-600Kb/s on 5GHz connection using WPA/WPA2.

  Notebook ACER ASPIRE 3 A315-53-343Y

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880639] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] - Wi-fi automatically disconnecting

[Yosha872]

** Summary changed:

- Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi desconecta 
automaticamente
+ Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] - Wi-fi 
automatically disconnecting

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

Title:
  Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] - Wi-fi
  automatically disconnecting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  English translation: I updated to version 20.04 and since then my
  laptop has been showing an error, automatically disconnecting my wi-fi
  connections.

  Portuguese: Atualizei para a versão 20.04 e desde então meu notebook
  vem apresentando erro, desconectando automaticamente minhas conexões
  wi-fi.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josimar1912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 01:17:39 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  InstallationDate: Installed on 2020-01-17 (129 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3584
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=127ffefc-873d-410c-8d99-aaf1637e14dc ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago)
  dmi.bios.date: 07/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05RCHV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/10/2019:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3584
  dmi.product.sku: 08D1
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1880639] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi desconecta automaticamente

[Yosha872]

** Description changed:

- Atualizei para a versão 20.04 e desde então meu notebook vem
+ English translation: I updated to version 20.04 and since then my laptop
+ has been showing an error, automatically disconnecting my wi-fi
+ connections.
+ 
+ Portuguese: Atualizei para a versão 20.04 e desde então meu notebook vem
  apresentando erro, desconectando automaticamente minhas conexões wi-fi.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  josimar1912 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  josimar1912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 01:17:39 2020
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  InstallationDate: Installed on 2020-01-17 (129 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
-  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
-  Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
+  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3584
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=127ffefc-873d-410c-8d99-aaf1637e14dc ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-31-generic N/A
-  linux-backports-modules-5.4.0-31-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-31-generic N/A
+  linux-backports-modules-5.4.0-31-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago)
  dmi.bios.date: 07/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05RCHV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/10/2019:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3584
  dmi.product.sku: 08D1
  dmi.sys.vendor: Dell Inc.

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

Title:
  Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi
  desconecta automaticamente

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  English translation: I updated to version 20.04 and since then my
  laptop has been showing an error, automatically disconnecting my wi-fi
  connections.

  Portuguese: Atualizei para a versão 20.04 e desde então meu notebook
  vem apresentando erro, desconectando automaticamente minhas conexões
  wi-fi.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josimar1912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 01:17:39 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  InstallationDate: Installed on 2020-01-17 (129 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 

[Kernel-packages] [Bug 1880639] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi desconecta automaticamente

[Yosha872]

** Tags added: qca9377

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

Title:
  Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] O wi-fi
  desconecta automaticamente

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Atualizei para a versão 20.04 e desde então meu notebook vem
  apresentando erro, desconectando automaticamente minhas conexões wi-
  fi.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josimar1912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 26 01:17:39 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
  InstallationDate: Installed on 2020-01-17 (129 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3584
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=127ffefc-873d-410c-8d99-aaf1637e14dc ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-11 (15 days ago)
  dmi.bios.date: 07/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05RCHV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd07/10/2019:svnDellInc.:pnInspiron3584:pvr:rvnDellInc.:rn05RCHV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3584
  dmi.product.sku: 08D1
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760539] Re: QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s (1Mb/s)

[Yosha872]

** Tags added: hwe-networking-wifi

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

Title:
  QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s
  (1Mb/s)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04, development branch, and I have 
  QCA9377 802.11ac Wireless Network Adapter

  When I connect it to WiFi hotspot in 2.4G mode I will get only 1MBps, and 
  When I connect it to WiFi hotspot in   5G mode I will get only 6MBps.

  I think an updated firmware is needed.

  Running:
  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rwd1422 F pulseaudio
   /dev/snd/controlC0:  rwd1422 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. XPS 8930
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=6a5b9e49-0017-4dc7-a2de-43c63fe0a8bb ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd12/12/2017:svnDellInc.:pnXPS8930:pvr1.0.5:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rwd1422 F pulseaudio
   /dev/snd/controlC0:  rwd1422 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. XPS 8930
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=6a5b9e49-0017-4dc7-a2de-43c63fe0a8bb ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd12/12/2017:svnDellInc.:pnXPS8930:pvr1.0.5:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760539] Re: QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s (1Mb/s)

[Yosha872]

Same issue on Ubuntu 22.04.2 (kernel 5.19.0-38-generic).

However, this is NOT the real speed of my WI-FI. This is visible by
doing a speedtest with a ISP (I get 57 Mb/s, fiber), or from terminal by
typing 'iwlconfig'.

Example on my laptop Acer E5-575G:

wlp3s0IEEE 802.11  ESSID:"TP-Link_"  
  Mode:Managed  Frequency:2.417 GHz  Access Point: XX:XX:XX:XX:XX:X   
  Bit Rate=1 Mb/s   Tx-Power=20 dBm   
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Power Management:on
  Link Quality=47/70  Signal level=-63 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:59   Missed beacon:0

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

Title:
  QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s
  (1Mb/s)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04, development branch, and I have 
  QCA9377 802.11ac Wireless Network Adapter

  When I connect it to WiFi hotspot in 2.4G mode I will get only 1MBps, and 
  When I connect it to WiFi hotspot in   5G mode I will get only 6MBps.

  I think an updated firmware is needed.

  Running:
  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rwd1422 F pulseaudio
   /dev/snd/controlC0:  rwd1422 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. XPS 8930
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=6a5b9e49-0017-4dc7-a2de-43c63fe0a8bb ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd12/12/2017:svnDellInc.:pnXPS8930:pvr1.0.5:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rwd1422 F pulseaudio
   /dev/snd/controlC0:  rwd1422 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. XPS 8930
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=6a5b9e49-0017-4dc7-a2de-43c63fe0a8bb ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd12/12/2017:svnDellInc.:pnXPS8930:pvr1.0.5:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   

[Kernel-packages] [Bug 1760539] Re: QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s (1Mb/s)

[Yosha872]

** Summary changed:

- QCA9377 WIFI does not work full speed - runs at lowest biterate 1Mp/s
+ QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s (1Mb/s)

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

Title:
  QCA9377 WIFI does not work full speed - runs at lowest bitrate 1Mp/s
  (1Mb/s)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04, development branch, and I have 
  QCA9377 802.11ac Wireless Network Adapter

  When I connect it to WiFi hotspot in 2.4G mode I will get only 1MBps, and 
  When I connect it to WiFi hotspot in   5G mode I will get only 6MBps.

  I think an updated firmware is needed.

  Running:
  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rwd1422 F pulseaudio
   /dev/snd/controlC0:  rwd1422 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. XPS 8930
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=6a5b9e49-0017-4dc7-a2de-43c63fe0a8bb ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd12/12/2017:svnDellInc.:pnXPS8930:pvr1.0.5:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rwd1422 F pulseaudio
   /dev/snd/controlC0:  rwd1422 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-11 (23 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  MachineType: Dell Inc. XPS 8930
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=6a5b9e49-0017-4dc7-a2de-43c63fe0a8bb ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0DF42J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd12/12/2017:svnDellInc.:pnXPS8930:pvr1.0.5:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start

[Murph]

Same problem with a newly created Ubuntu 20.04 VM (Windows 11 Pro 22H2
Hyper-V), on the linux-generic kernel.  The same 8 logs per 10 seconds
as seen on jammy, for the scripts not found in /usr/libexec/hyperkvpd.

murph@Ubuntu-Virtual-Machine:~$ uname -a
Linux Ubuntu-Virtual-Machine 5.4.0-146-generic #163-Ubuntu SMP Fri Mar 17 
18:26:02 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
murph@Ubuntu-Virtual-Machine:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.6 LTS
Release:20.04
Codename:   focal
murph@Ubuntu-Virtual-Machine:~$ 


** Tags added: focal

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

Title:
  [Hyper-V] KVP daemon fails to start

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Invalid

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  that there are 2 issues with the KVP daemon:

  1. KVP daemon crash after boot. Opened a different bug for this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640

  2. After the KVP daemon is being started the following messages
  appear:

  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dns_info: not found
  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dhcp_info: not found

  The above binaries are present on the system, but the their actual
  path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info.
  Either the hv_get_dhcp_info and hv_get_dns_info binaries should be
  placed in the location where the daemon is looking for
  (/usr/libexec/hypervkvpd/), or the daemon should be set to search for
  the binaries in the /usr/sbin directory.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called

[Po-Hsu Lin]

This is now affecting K-oracle-5.19.0-1020.23, on these two instances like in 
the bug report:
- VM.DenseIO2.8
- VM.Standard2.1

** Tags added: 5.19 kinetic oracle sru-20230320 ubuntu-ltp-kernel-misc

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

Title:
  cmos_interrupt not getting called

Status in linux-oracle-5.15 package in Ubuntu:
  Fix Committed
Status in linux-oracle-5.15 source package in Focal:
  Fix Released
Status in linux-oracle-5.15 source package in Jammy:
  Fix Released

Bug description:
  The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
  regression of the RTC cmos driver on certain Oracle clouds.

  This was observed on jammy:linux-oracle-5.15.0-1031.37.
  - VM.DenseIO2.8
  - VM.Standard2.1

  rtc01   0  TINFO  :  RTC READ TEST:
  rtc01   1  TPASS  :  RTC READ TEST Passed
  rtc01   0  TINFO  :  Current RTC date/time is 16-3-2023, 17:36:04.
  rtc01   0  TINFO  :  RTC ALARM TEST :
  rtc01   0  TINFO  :  Alarm time set to 17:36:09.
  rtc01   0  TINFO  :  Waiting 5 seconds for the alarm...
  rtc01   2  TFAIL  :  rtc01.c:151: Timed out waiting for the alarm
  rtc01   0  TINFO  :  RTC UPDATE INTERRUPTS TEST :
  rtc01   0  TINFO  :  Waiting for  5 update interrupts...
  rtc01   3  TFAIL  :  rtc01.c:208: Timed out waiting for the update 
interrupt
  rtc01   0  TINFO  :  RTC Tests Done!

  Notice that we successfully enable RTC_AIE_ON, unlike
  VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
  bpftrace on -1029 that we see the cmos interrupt (part of ltp
  read_alarm_test)

  sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
  Attaching 1 probe...
  kprobe:cmos_interrupt

  On -1031 no interrupt is detected for both the alarm and update tests.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015515] [NEW] net: sched: allow flower to match erspan options

[Tony Duan]

Public bug reported:

* Explain the bug(s)

In upstream, TCA_POLICE_PKTRATE64 was introduced after
TCA_FLOWER_KEY_ENC_OPTS_ERSPAN. linux-bluefiled only has
TCA_POLICE_PKTRATE64 related support and does not have ERSPAN support
which might cause "ovs" project compile error because of lacking of
ERSPAN related support if ovs supports ERSPAN.

* Brief explanation of fixes

Cherry-pick. No adaptation. Add ERSPAN support for flower to allow flower to 
match ERSPAN options
79b1011cb33d net: sched: allow flower to match erspan options

* How to test

The options can be described in the form:
VER:INDEX:DIR:HWID/VER:INDEX_MASK:DIR_MASK:HWID_MASK. When ver is set to 1, 
index will be applied while dir and hwid will be ignored, and when ver is set 
to 2, dir and hwid will be used while index will be ignored.
Different from geneve, only one option can be set. And also, geneve options, 
vxlan options or erspan options can't be set at the same time.
Here's an example:
  # ip link add name erspan1 type erspan external
  # tc qdisc add dev erspan1 ingress
  # tc filter add dev erspan1 protocol ip parent : \
  flower \
enc_src_ip 10.0.99.192 \
enc_dst_ip 10.0.99.193 \
enc_key_id 11 \
erspan_opts 1:12:0:0/1::0:0 \
ip_proto udp \
action mirred egress redirect dev eth0

* What it could break.

Nothing.

** Affects: linux-bluefield (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  net: sched: allow flower to match erspan options

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Explain the bug(s)

  In upstream, TCA_POLICE_PKTRATE64 was introduced after
  TCA_FLOWER_KEY_ENC_OPTS_ERSPAN. linux-bluefiled only has
  TCA_POLICE_PKTRATE64 related support and does not have ERSPAN support
  which might cause "ovs" project compile error because of lacking of
  ERSPAN related support if ovs supports ERSPAN.

  * Brief explanation of fixes

  Cherry-pick. No adaptation. Add ERSPAN support for flower to allow flower to 
match ERSPAN options
  79b1011cb33d net: sched: allow flower to match erspan options

  * How to test

  The options can be described in the form:
  VER:INDEX:DIR:HWID/VER:INDEX_MASK:DIR_MASK:HWID_MASK. When ver is set to 1, 
index will be applied while dir and hwid will be ignored, and when ver is set 
to 2, dir and hwid will be used while index will be ignored.
  Different from geneve, only one option can be set. And also, geneve options, 
vxlan options or erspan options can't be set at the same time.
  Here's an example:
# ip link add name erspan1 type erspan external
# tc qdisc add dev erspan1 ingress
# tc filter add dev erspan1 protocol ip parent : \
flower \
  enc_src_ip 10.0.99.192 \
  enc_dst_ip 10.0.99.193 \
  enc_key_id 11 \
  erspan_opts 1:12:0:0/1::0:0 \
  ip_proto udp \
  action mirred egress redirect dev eth0

  * What it could break.

  Nothing.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install

[Brian Murray]

I'm only seeing Modaliases for the broadcom-sta-dkms package (and not
bcmwl-kernel-source or broadcom-sta-source)  in Lunar so I don't think
that's the issue.

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

Title:
  Failed to install bcmwl wireless driver during the install

Status in linux-firmware package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Specifically for Lunar - using a Macbook Air 2012, its wireless driver
  was not enabled even though I ticked the wireless tickbox on the
  installer.

  A quick look at the installer logs reveals various issues

  syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [   43.063747] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [   43.063802] 
b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063862] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2
  syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [   43.063908] 
b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with 
error -2

  I will attach the installer logs manually since this was captured
  after the installation

  Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was
  installed correctly during the install so this is a regression with
  the 6.2 kernel

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2007633] Re: amdgpu fails to init with kernel 5.19.0

[grogd]

Yes, cherry picked commit "Fix for BO move issue" worked for me too.
Using jammy-5.19.0-35.36.

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update 2023-03-04: A new version of the 5.19 kernel,
  5.19.0-35-generic, will now boot into a GUI desktop instead of leaving
  me with a completely unusable system, BUT, there is no working Vulkan
  implementation, as if the amdgpu driver still failed to load so the
  new kernel did a fallback to the radeon driver, I would guess.

  Partial output from vulkaninfo with 5.19 kernel:

  --

  Device Properties and Extensions:
  =
  GPU0:
  VkPhysicalDeviceProperties:
  ---
  apiVersion= 4206816 (1.3.224)
  driverVersion = 1 (0x0001)
  vendorID  = 0x10005
  deviceID  = 0x
  deviceType= PHYSICAL_DEVICE_TYPE_CPU
  deviceName= llvmpipe (LLVM 15.0.6, 256 bits)
  pipelineCacheUUID = 76616c2d-2573---

  END of Update 2023-03-04
  

  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 2015511] [NEW] Kinetic update: upstream stable patchset 2023-04-06

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2023-04-06

Ported from the following upstream stable releases:
v5.15.92, v6.1.10
v5.15.93, v6.1.11
v5.15.94, v6.1.12
v5.15.95, v6.1.13

   from git://git.kernel.org/

ARM: dts: imx: Fix pca9547 i2c-mux node name
ARM: dts: vf610: Fix pca9548 i2c-mux node names
arm64: dts: freescale: Fix pca954x i2c-mux node names
arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI
firmware: arm_scmi: Clear stale xfer->hdr.status
bpf: Skip task with pid=1 in send_signal_common()
erofs/zmap.c: Fix incorrect offset calculation
blk-cgroup: fix missing pd_online_fn() while activating policy
HID: playstation: sanity check DualSense calibration data.
dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init
cifs: fix return of uninitialized rc in dfs_cache_update_tgthint()
extcon: usbc-tusb320: fix kernel-doc warning
net: fix NULL pointer in skb_segment_list
net: mctp: purge receive queues on sk destruction
UBUNTU: Upstream stable to v5.15.92, v6.1.10
firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP 
region
bus: sunxi-rsb: Fix error handling in sunxi_rsb_init()
ASoC: Intel: bytcht_es8316: Drop reference count of ACPI device after use
ASoC: Intel: bytcr_rt5651: Drop reference count of ACPI device after use
ASoC: Intel: bytcr_rt5640: Drop reference count of ACPI device after use
ASoC: Intel: bytcr_wm5102: Drop reference count of ACPI device after use
bpf: Fix a possible task gone issue with bpf_send_signal[_thread]() helpers
ALSA: hda/via: Avoid potential array out-of-bound in add_secret_dac_path()
bpf: Fix to preserve reg parent/live fields when copying range info
bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener
arm64: dts: imx8mm: Fix pad control for UART1_DTE_RX
drm/vc4: hdmi: make CEC adapter name unique
scsi: Revert "scsi: core: map PQ=1, PDT=other values to 
SCSI_SCAN_TARGET_PRESENT"
vhost/net: Clear the pending messages when the backend is removed
WRITE is "data source", not destination...
READ is "data destination", not source...
fix iov_iter_bvec() "direction" argument
fix "direction" argument of iov_iter_kvec()
ice: Prevent set_channel from changing queues while RDMA active
qede: execute xdp_do_flush() before napi_complete_done()
virtio-net: execute xdp_do_flush() before napi_complete_done()
dpaa_eth: execute xdp_do_flush() before napi_complete_done()
dpaa2-eth: execute xdp_do_flush() before napi_complete_done()
sfc: correctly advertise tunneled IPv6 segmentation
net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices
block, bfq: replace 0/1 with false/true in bic apis
block, bfq: fix uaf for bfqq in bic_set_bfqq()
netrom: Fix use-after-free caused by accept on already connected socket
drm/i915/guc: Fix locking when searching for a hung request
drm/i915/adlp: Fix typo for reference clock
netfilter: br_netfilter: disable sabotage_in hook after first suppression
squashfs: harden sanity check in squashfs_read_xattr_id_table
net: phy: meson-gxl: Add generic dummy stubs for MMD register access
ip/ip6_gre: Fix changing addr gen mode not generating IPv6 link local address
ip/ip6_gre: Fix non-point-to-point tunnel not generating IPv6 link local address
riscv: kprobe: Fixup kernel panic when probing an illegal position
igc: return an error if the mac type is unknown in igc_ptp_systim_to_hwtstamp()
can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate
ata: libata: Fix sata_down_spd_limit() when no link speed is reported
selftests: net: udpgso_bench_rx: Fix 'used uninitialized' compiler warning
selftests: net: udpgso_bench_rx/tx: Stop when wrong CLI args are provided
selftests: net: udpgso_bench_tx: Cater for pending datagrams zerocopy 
benchmarking
virtio-net: Keep stop() to follow mirror sequence of open()
net: openvswitch: fix flow memory leak in ovs_flow_cmd_new
efi: fix potential NULL deref in efi_mem_reserve_persistent
i2c: designware-pci: Add new PCI IDs for AMD NAVI GPU
i2c: mxs: suppress probe-deferral error message
scsi: target: core: Fix warning on RT kernels
perf/x86/intel: Add Emerald Rapids
scsi: iscsi_tcp: Fix UAF during logout when accessing the shost ipaddress
scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress
i2c: rk3x: fix a bunch of kernel-doc warnings
platform/x86: gigabyte-wmi: add support for B450M DS3H WIFI-CF
net/x25: Fix to not accept on connected socket
drm/amd/display: Fix timing not 

[Kernel-packages] [Bug 1887703] Re: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller

[Clinton Fung]

*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956

** Attachment removed: "Canonical - Supermicro - Nvida AI workstation.docx"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+attachment/5661723/+files/Canonical%20-%20Supermicro%20-%20Nvida%20AI%20workstation.docx

** Attachment removed: "image001.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+attachment/5661725/+files/image001.png

** Attachment removed: "image001.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+attachment/5661722/+files/image001.png

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

Title:
  [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE
  controller

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  The Intel x710-TM4 is one of the latest 10GbE controllers from intel
  using the i40e driver.  This particular 4 port comes in a 2x2
  arrangement: 2x SFP+ and 2x RJ-45.  This card is enabled in 5.4 via
  the inbox version of the i40e driver, and hwinfo does show both sides
  of the card but the kernel only sees the two SFP+ ports and cannot
  address or use the two copper ports.

  This is currently blocking certification for one of our hardware
  partners.

  After some investigation we see this works in a more recent version of
  the driver. Intel suggests the commit in FIXES from 5.5 should make
  this work.

  This is a regression from the i40e driver in Bionic (5.3 HWE) that,
  per the tester, does show all four ports.

  [FIXES]

  3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support

  I have a branch here:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710

  [TESTING]
  Boot system, verify four ports are visible and can be addressed and pass data.

  [IMPACT]

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

[Michael Reed]

I have created a test kernel for Kinetic

https://people.canonical.com/~mreed/hpe/lp_2008745_config_numa_emu/kinetic/

** Description changed:

  [Impact]
  Currently Ubuntu kernel has this kernel config disabled.
  But in some case, Intel's SPR-HBM needs this.
  
  Please search the keyword "fake numa" in
  https://community.intel.com/t5/Blogs/Products-and-
  Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-
  Applications-for/post/1335100
  
  [Fix]
  
  Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later
  
  [Test Plan]
  
  [Where problems could occur]
  
  The regression risk is low
  
  [Other Info]
+ Jammy
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu
+ 
+ Kinetic
+ 
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Description changed:

  [Impact]
+ 
  Currently Ubuntu kernel has this kernel config disabled.
- But in some case, Intel's SPR-HBM needs this.
+ But in some cases, Intel's Sapphire Rapids High Bandwith
+ Memory (SPR-HBM) needs this option.
+ 
+ Memory bandwidth has been a bottleneck of increasingly memory bound
+ workloads. Sapphire Rapids plus HBM is specifically targeted to
+ cater to these workloads, traditionally served using overprovisioning
+ of memory devices.
  
  Please search the keyword "fake numa" in
  https://community.intel.com/t5/Blogs/Products-and-
  Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-
  Applications-for/post/1335100
  
  [Fix]
  
  Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later
  
  [Test Plan]
  
  [Where problems could occur]
  
  The regression risk is low
  
  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu
  
  Kinetic
  
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic

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

Title:
  [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  Incomplete

Bug description:
  [Impact]

  Currently Ubuntu kernel has this kernel config disabled.
  But in some cases, Intel's Sapphire Rapids High Bandwith
  Memory (SPR-HBM) needs this option.

  Memory bandwidth has been a bottleneck of increasingly memory bound
  workloads. Sapphire Rapids plus HBM is specifically targeted to
  cater to these workloads, traditionally served using overprovisioning
  of memory devices.

  Please search the keyword "fake numa" in
  https://community.intel.com/t5/Blogs/Products-and-
  Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-
  Applications-for/post/1335100

  [Fix]

  Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later

  [Test Plan]

  [Where problems could occur]

  The regression risk is low

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu

  Kinetic

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015505] [NEW] Nvidia stop worked on this LTS update

[Gudata]

Public bug reported:

I have installed some updates and my external monitor is not working anymore.
By not working I mean that I can see the display and the windows, but my mouse 
and keyboards are not responsive.
when I disconnect the external monitor, everything works. When re-connect, the 
mouse and the keyboard are not able to click or interact to anything displayed 
on the external monitor.

I was on a Lenovo Legion with Nvida enabled when the drivers stopped worked.
I tried to switch to discrete graphis and there it didn't work.
I tried both open and nuvelio drivers - nothing helps.


Description:Ubuntu 22.04.2 LTS
Release:22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.1.0-1008-oem 6.1.0-1008.8
ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14
Uname: Linux 6.1.0-1008-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Apr  6 23:36:49 2023
InstallationDate: Installed on 2022-03-22 (380 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: linux-signed-oem-6.1
UpgradeStatus: Upgraded to jammy on 2023-04-06 (0 days ago)

** Affects: linux-signed-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Nvidia stop worked on this LTS update

Status in linux-signed-oem-6.1 package in Ubuntu:
  New

Bug description:
  I have installed some updates and my external monitor is not working anymore.
  By not working I mean that I can see the display and the windows, but my 
mouse and keyboards are not responsive.
  when I disconnect the external monitor, everything works. When re-connect, 
the mouse and the keyboard are not able to click or interact to anything 
displayed on the external monitor.

  I was on a Lenovo Legion with Nvida enabled when the drivers stopped worked.
  I tried to switch to discrete graphis and there it didn't work.
  I tried both open and nuvelio drivers - nothing helps.

  
  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.1.0-1008-oem 6.1.0-1008.8
  ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14
  Uname: Linux 6.1.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr  6 23:36:49 2023
  InstallationDate: Installed on 2022-03-22 (380 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-oem-6.1
  UpgradeStatus: Upgraded to jammy on 2023-04-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.1/+bug/2015505/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Mauricio Faria de Oliveira]

Marking linux-hwe-5.15 as Invalid as it follows linux 5.15
(will get the fix automatically from linux 5.15 from jammy).

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

** Changed in: linux-hwe-5.15 (Ubuntu)
   Status: New => Invalid

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

Title:
  losetup with mknod fails on jammy with kernel 5.15.0-69-generic

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid

Bug description:
  losetup fails with devices created manually by mknod on kernel
  5.15.0-69-generic

  # fallocate -l 1G test
  # mknod -m 660 /dev/loop8 b 7 8
  # chown root:disk /dev/loop8
  # losetup /dev/loop8 ./test
  losetup: ./test: failed to set up loop device: Device or resource busy

  Possibly as a result of this patch:
  
https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/

  which was introduced in 5.15.0-68:
  
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

  On a machine prior to this change (no issue with losetup):
  # cat /sys/module/loop/parameters/max_loop
  0
  # uname -r
  5.15.0-58-generic

  On a machine after the change (has losetup issue as described above):
  # cat /sys/module/loop/parameters/max_loop
  8
  # uname -r
  5.15.0-69-generic

  So it looks like the default changed and the max amount of loop
  devices that can be created with mknod (not loop-control) is 8. If we
  set max_loop=0 on the kernel command line, it works as before. Cannot
  unload and reload module on a running system to change the parameter
  because it is built into the kernel.

  Another workaround is to use `losetup --find` but that means you
  cannot create with named devices created with mknod.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1887703] Re: Canonical Certification.

[Valerie Noto]

*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956

+Frank Lai  in reference to a recent discussion
about AI/ML.

Valerie Noto
IHV Alliances Business Development Director
valerie.n...@canonical.com | M: +1 619 203 0453




On Thu, Apr 6, 2023 at 12:19 PM Valerie Noto 
wrote:

> Hi William,
> Sorry for not connecting the dots!
>
> @Jeffrey Lane  can you please tell us what you would
> need to certify this platform?
>
> @William Li  I need to build a high level
> business case to justify that we certify the server at no cost. I have
> started the attached document. Can you please review and provide your
> inputs on the highlighted parts?
>
> Thanks!
>
>
> Valerie Noto
> IHV Alliances Business Development Director
> valerie.n...@canonical.com | M: +1 619 203 0453
>
> 
>
>
> On Thu, Apr 6, 2023 at 9:18 AM William Li 
> wrote:
>
>> Hi Valerie,
>>
>>
>>
>> The certification is for the liquid cooled AI Platform we talked about
>> last month.
>>
>> Thank you.
>>
>>
>>
>>
>> https://www.supermicro.com/en/featured/liquid-cooled-ai-development-platform
>>
>>
>>
>> Best Regards,
>>
>> William Li  (Arch Dept.)
>>
>> Super Micro Computer, Inc.
>>
>> www.supermicro.com
>>
>>
>>
>> *From:* Valerie Noto 
>> *Sent:* Thursday, April 6, 2023 6:16 AM
>> *To:* Ly To (Arch) ; Jeffrey Lane ;
>> Andrey Grebennikov 
>> *Cc:* 1887...@bugs.launchpad.net; Benjamin Ringor (Arch) <
>> benjam...@supermicro.com>; William Li (Arch) 
>> *Subject:* Re: Canonical Certification.
>>
>>
>>
>> [*CAUTION: *External Mail]
>>
>> +Andrey Grebennikov 
>>
>>
>>
>> Hi Ly,
>>
>> Supermicro does not participate in the certification program at this
>> time. The mode of operations it to study the certifications on a case by
>> case basis.
>>
>> What is the context of your request? Is there a project behind it? Who is
>> the customer?
>>
>> Based on those elements, we can discuss a path to certification.
>>
>>
>>
>> Thanks!
>>
>> Valerie
>>
>>
>>
>>
>>
>>
>>
>> Valerie Noto
>>
>> IHV Alliances Business Development Director
>>
>> valerie.n...@canonical.com | M: +1 619 203 0453
>>
>>
>>
>> [insights.ubuntu.com]
>> 
>>
>>
>>
>>
>>
>> On Wed, Apr 5, 2023 at 3:24 PM Ly To  wrote:
>>
>> H Valerie / Jeff,
>>
>>
>>
>> Are you still in certification submission review team ?.
>>
>>
>>
>> I have one system model ready to submit for the review.
>>
>>
>>
>> Somehow the used link does not work now .
>>
>>
>>
>> Would you please provide me the access link ?.
>>
>>
>>
>> Thank you,
>>
>> Ly,
>>
>>


** Attachment added: "image001.png"
   
https://bugs.launchpad.net/bugs/1887703/+attachment/5661725/+files/image001.png

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

Title:
  [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE
  controller

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  The Intel x710-TM4 is one of the latest 10GbE controllers from intel
  using the i40e driver.  This particular 4 port comes in a 2x2
  arrangement: 2x SFP+ and 2x RJ-45.  This card is enabled in 5.4 via
  the inbox version of the i40e driver, and hwinfo does show both sides
  of the card but the kernel only sees the two SFP+ ports and cannot
  address or use the two copper ports.

  This is currently blocking certification for one of our hardware
  partners.

  After some investigation we see this works in a more recent version of
  the driver. Intel suggests the commit in FIXES from 5.5 should make
  this work.

  This is a regression from the i40e driver in Bionic (5.3 HWE) that,
  per the tester, does show all four ports.

  [FIXES]

  3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support

  I have a branch here:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710

  [TESTING]
  Boot system, verify four ports are visible and can be addressed and pass data.

  [IMPACT]

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Mauricio Faria de Oliveira]

** Attachment added: "loop-ctl-add.c"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015400/+attachment/5661724/+files/loop-ctl-add.c

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

Title:
  losetup with mknod fails on jammy with kernel 5.15.0-69-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  losetup fails with devices created manually by mknod on kernel
  5.15.0-69-generic

  # fallocate -l 1G test
  # mknod -m 660 /dev/loop8 b 7 8
  # chown root:disk /dev/loop8
  # losetup /dev/loop8 ./test
  losetup: ./test: failed to set up loop device: Device or resource busy

  Possibly as a result of this patch:
  
https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/

  which was introduced in 5.15.0-68:
  
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

  On a machine prior to this change (no issue with losetup):
  # cat /sys/module/loop/parameters/max_loop
  0
  # uname -r
  5.15.0-58-generic

  On a machine after the change (has losetup issue as described above):
  # cat /sys/module/loop/parameters/max_loop
  8
  # uname -r
  5.15.0-69-generic

  So it looks like the default changed and the max amount of loop
  devices that can be created with mknod (not loop-control) is 8. If we
  set max_loop=0 on the kernel command line, it works as before. Cannot
  unload and reload module on a running system to change the parameter
  because it is built into the kernel.

  Another workaround is to use `losetup --find` but that means you
  cannot create with named devices created with mknod.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Mauricio Faria de Oliveira]

Simpler workarounds:

For non-existing /dev/loopN devices, `losetup /dev/loopN image` should
work (i.e., don't do `mknod /dev/loopN`).

For /dev/non-loopN devices, it doesn't (different code path), so the
utility attached should help for now.

Details below.

...

# lsb_release -cs
jammy

# uname -rv
5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023

# cat /sys/module/loop/parameters/max_loop
8

# ls -1 /dev/loop*
/dev/loop-control
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/loop4
/dev/loop5
/dev/loop6
/dev/loop7

# grep loop /proc/devices
  7 loop

# truncate -s 1g test

Case 1) Existing /dev/loopN: LOOP_CTL_ADD is not called, open() fails (non-init 
mutex, apparently).
  
# mknod /dev/loop8 b 7 8
# strace -e openat,ioctl losetup /dev/loop8 test 2>&1 | grep -i loop
openat(AT_FDCWD, "/dev/loop8", O_RDWR|O_CLOEXEC) = -1 ENXIO (No such device or 
address)
openat(AT_FDCWD, "/dev/loop8", O_RDWR|O_CLOEXEC) = -1 ENXIO (No such device or 
address)
losetup: /dev/loop8: failed to set up loop device

Case 2) Non-existing /dev/loopN: LOOP_CTL_ADD is called, open() works.

# rm /dev/loop8

# strace -e openat,ioctl losetup /dev/loop8 test 2>&1 | grep -i loop
openat(AT_FDCWD, "/dev/loop-control", O_RDWR|O_CLOEXEC) = 3
ioctl(3, LOOP_CTL_ADD, 8)   = 8
openat(AT_FDCWD, "/dev/loop8", O_RDWR|O_CLOEXEC) = 4
ioctl(4, LOOP_CONFIGURE, {fd=3, block_size=0, info={lo_offset=0, lo_number=0, 
lo_flags=0, lo_file_name="/root/test", ...}}) = 0

Case 3) Non-existing /dev/non-loopN: LOOP_CTL_ADD is not called, open()
fails.

# strace -e openat,ioctl losetup /dev/mynameX test 2>&1 | grep -i loop
losetup: /dev/mynameX: failed to set up loop device

Case 4) Existing /dev/non-loopN with workaround tool (attached)

# gcc -o loop-ctl-add loop-ctl-add.c

# mknod /dev/mynameX b 7 42

# losetup /dev/mynameX test
losetup: /dev/mynameX: failed to set up loop device: No such device or address

# ./loop-ctl-add 42
Success on ioctl('/dev/loop-control', LOOP_CTL_ADD, 42)

# losetup /dev/mynameX test
#

works!

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

Title:
  losetup with mknod fails on jammy with kernel 5.15.0-69-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  losetup fails with devices created manually by mknod on kernel
  5.15.0-69-generic

  # fallocate -l 1G test
  # mknod -m 660 /dev/loop8 b 7 8
  # chown root:disk /dev/loop8
  # losetup /dev/loop8 ./test
  losetup: ./test: failed to set up loop device: Device or resource busy

  Possibly as a result of this patch:
  
https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/

  which was introduced in 5.15.0-68:
  
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

  On a machine prior to this change (no issue with losetup):
  # cat /sys/module/loop/parameters/max_loop
  0
  # uname -r
  5.15.0-58-generic

  On a machine after the change (has losetup issue as described above):
  # cat /sys/module/loop/parameters/max_loop
  8
  # uname -r
  5.15.0-69-generic

  So it looks like the default changed and the max amount of loop
  devices that can be created with mknod (not loop-control) is 8. If we
  set max_loop=0 on the kernel command line, it works as before. Cannot
  unload and reload module on a running system to change the parameter
  because it is built into the kernel.

  Another workaround is to use `losetup --find` but that means you
  cannot create with named devices created with mknod.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1887703] Re: Canonical Certification.

[Valerie Noto]

*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956

Hi William,
Sorry for not connecting the dots!

@Jeffrey Lane  can you please tell us what you would
need to certify this platform?

@William Li  I need to build a high level
business case to justify that we certify the server at no cost. I have
started the attached document. Can you please review and provide your
inputs on the highlighted parts?

Thanks!


Valerie Noto
IHV Alliances Business Development Director
valerie.n...@canonical.com | M: +1 619 203 0453




On Thu, Apr 6, 2023 at 9:18 AM William Li  wrote:

> Hi Valerie,
>
>
>
> The certification is for the liquid cooled AI Platform we talked about
> last month.
>
> Thank you.
>
>
>
>
> https://www.supermicro.com/en/featured/liquid-cooled-ai-development-platform
>
>
>
> Best Regards,
>
> William Li  (Arch Dept.)
>
> Super Micro Computer, Inc.
>
> www.supermicro.com
>
>
>
> *From:* Valerie Noto 
> *Sent:* Thursday, April 6, 2023 6:16 AM
> *To:* Ly To (Arch) ; Jeffrey Lane ;
> Andrey Grebennikov 
> *Cc:* 1887...@bugs.launchpad.net; Benjamin Ringor (Arch) <
> benjam...@supermicro.com>; William Li (Arch) 
> *Subject:* Re: Canonical Certification.
>
>
>
> [*CAUTION: *External Mail]
>
> +Andrey Grebennikov 
>
>
>
> Hi Ly,
>
> Supermicro does not participate in the certification program at this time.
> The mode of operations it to study the certifications on a case by case
> basis.
>
> What is the context of your request? Is there a project behind it? Who is
> the customer?
>
> Based on those elements, we can discuss a path to certification.
>
>
>
> Thanks!
>
> Valerie
>
>
>
>
>
>
>
> Valerie Noto
>
> IHV Alliances Business Development Director
>
> valerie.n...@canonical.com | M: +1 619 203 0453
>
>
>
> [insights.ubuntu.com]
> 
>
>
>
>
>
> On Wed, Apr 5, 2023 at 3:24 PM Ly To  wrote:
>
> H Valerie / Jeff,
>
>
>
> Are you still in certification submission review team ?.
>
>
>
> I have one system model ready to submit for the review.
>
>
>
> Somehow the used link does not work now .
>
>
>
> Would you please provide me the access link ?.
>
>
>
> Thank you,
>
> Ly,
>
>


** Attachment added: "image001.png"
   
https://bugs.launchpad.net/bugs/1887703/+attachment/5661722/+files/image001.png

** Attachment added: "Canonical - Supermicro - Nvida AI workstation.docx"
   
https://bugs.launchpad.net/bugs/1887703/+attachment/5661723/+files/Canonical%20-%20Supermicro%20-%20Nvida%20AI%20workstation.docx

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

Title:
  [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE
  controller

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [IMPACT]

  The Intel x710-TM4 is one of the latest 10GbE controllers from intel
  using the i40e driver.  This particular 4 port comes in a 2x2
  arrangement: 2x SFP+ and 2x RJ-45.  This card is enabled in 5.4 via
  the inbox version of the i40e driver, and hwinfo does show both sides
  of the card but the kernel only sees the two SFP+ ports and cannot
  address or use the two copper ports.

  This is currently blocking certification for one of our hardware
  partners.

  After some investigation we see this works in a more recent version of
  the driver. Intel suggests the commit in FIXES from 5.5 should make
  this work.

  This is a regression from the i40e driver in Bionic (5.3 HWE) that,
  per the tester, does show all four ports.

  [FIXES]

  3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support

  I have a branch here:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710

  [TESTING]
  Boot system, verify four ports are visible and can be addressed and pass data.

  [IMPACT]

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1 kernel

[Mario Limonciello]

If it's trending to be caused by PSR (which it sounds like it is), try to 
revert this patch:
https://github.com/torvalds/linux/commit/751281c55579f0cb0e56c9797d4663f689909681

> Short, massive flickering while running with parameters
"amdgpu.dcdebugmask=0x10 amdgpu.sg_display=0",

Have a try with this patch:
https://gitlab.freedesktop.org/drm/amd/uploads/ebd02a1dc605110a3f28b9c4eb62c313/0001-drm-
amd-display-fix-flickering-caused-by-S-G-mode.patch (and drop
amdgpu.sg_display=0)

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu

[Roxana Nicolescu]

** Description changed:

  SRU Justification
  
  [Impact]
+ 
+ Intel has introduced support for their new Emerald Rapids CPU.
+ This support is a nice feature to have in Jammy because it is an LTS release 
and enabling extra hardware adds to its usability.
+ 
  Usually backporting new features to existing kernels it's not a common 
practice.
- But these commits were easy to pick. Some of the commits were already applied.
- More information about backporting these commits is addressed inline.
+ But these commits were easy to backport. Most of them were clean cherry 
picks. Some of them were already picked up from upstream stable releases,
+ and some required manual intervention because Jammy did not have some commits 
applied but the actual changes were very minimal.
+  
+ More information about each commit is addressed inline.
  
  [Commits]
  
- 1. Add New CPU Model Number for EMR in Core Kernel: 7beade0dd41d
- Already applied to jammy. Picked up in v5.15.80 upstream stable release
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003122
- 
- 2. Linux kernel: add EMR support to uncore-frequency driver: 9c252ecf3036
+ 1. 9c252ecf3036:
+ "platform/x86: intel-uncore-freq: add Emerald Rapids support"
  Had to adjust the path to uncore-frequency.c
  In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to 
uncore-frequency dir
  
- 3. PMU Update to Support New EMR CPU model Number:
- 3.1 5268a2842066c227e6ccd94bac562f1e1000244f already applied from 5.15.91 
upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011467
- 3.2 5a8a05f165fb18d37526062419774d9088c2a9b9
- Small adjustment needed because saphire, raptor changes were not there.
- done in 528c9f1daf20d "perf/x86/cstate: Add SAPPHIRERAPIDS_X CPU support"
+ 2. 5a8a05f165fb18d37526062419774d9088c2a9b9
+ TODO explain 
  
- 3.3 6795e558e9cc6123c24e2100a2ebe88e58a792bc already applied from 5.15.93 
upstream
- https://bugs.launchpad.net/bugs/2012665
- 3.4 69ced4160969025821f2999ff92163ed26568f1c already applied in 5.15.91
- https://bugs.launchpad.net/bugs/2011467
+ 3. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
+ Manually solved small conflicts due to missing
+ - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL 
domain"
+ - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N"
+ - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake"
+ - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake"
  
- 4. Perf RAPL PMU support on EMR: 57512b57dcfaf63c52d8ad2fb35321328cde31b0
- Manually solved small conflict due to missing 80275ca9e525c
- where a fixed DRAM domain energy unit is introduced
- TODO not sure if this one is correct.
- 
- 5. linux kernel: add EMR support to the intel_idle driver: 
74528edfbc664f9d2c927c4e5a44f1285598ed0f
+ 4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f
  clean cherry-pick
  
- 6. intel-speed-select tool support for EMR: 
61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
+ 5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5
  clean cherry-pick
  
- 7. Turbostat support on EMR: 93cac4150727dae0ee89f501dd75413b88eedec0
+ 6. 93cac4150727dae0ee89f501dd75413b88eedec0
  clean cherry-pick
  
- 8. intel-RAPL drivers to support new EMR CPU model number: 
7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
+ 7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb
  clean cherry-pick
  
- 9. Provide accel-config for EMR : TODO userspace
-    - this is user-space code, not kernel code (accel-config seems the
-  package that we already have in lunar, sync'ed from Debian, not
-  sure if we need to provide additional changes applied or if we
-  need to backport the whole user-space package to jammy)
- 
- 10. Enable in-field Array BIST for EMR
- code is still in the process of being reviewed, we shouldn't apply/backport 
this for now
- 
- 11. CXL 1.1 Compatibility ECN
- Very big patch -- won't port it to jammy
- 
- 12. Split Lock detection change for EMR:
- d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 linux-next
- Had to apply the following:
- - 727209376f499 x86/split_lock: Add sysctl to control the misery mode
- - b041b525dab95 x86/split_lock: Make life miserable for split lockers
- - 054ed6349c1bd Documentation/x86: Update split lock documentation
- And manually solved a conflict due to missing:
- - d3287fb0d3c8a x86/microcode/intel: Expose collect_cpu_info_early() for IFS
- - 3f2adf00f52b5 x86/cpu: Use MSR_IA32_MISC_ENABLE constants
- - ef79970d7ccdc x86/split-lock: Remove unused TIF_SLD bit
- 
- which are just small improvements and not critical.
- TODO more explanation here
- 
- 13. Add Emerald Rapids CPU model number ID for EDAC driver support: 
e4b2bc6616e21
+ 8. e4b2bc6616e21
  clean cherry-pick
  
- Testing:
- Kernel was built on cbd. roxanan-jammy-cd5956c49599-A3Ur
  
- Regression potential
- Very very low, these are new features, nothing to regress here.
+ [Testing]
+ Kernel was built on cbd and boot tested on a VM.
+ TODO ask for help from intel.
+ 
+ [Regression 

[Kernel-packages] [Bug 2015498] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2015498

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Focal)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Jammy)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Kinetic)
   Status: New => Incomplete

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

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Kinetic:
  Incomplete
Status in linux source package in Lunar:
  Incomplete

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start

[Murph]

** Changed in: linux-azure (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  [Hyper-V] KVP daemon fails to start

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Invalid

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  that there are 2 issues with the KVP daemon:

  1. KVP daemon crash after boot. Opened a different bug for this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640

  2. After the KVP daemon is being started the following messages
  appear:

  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dns_info: not found
  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dhcp_info: not found

  The above binaries are present on the system, but the their actual
  path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info.
  Either the hv_get_dhcp_info and hv_get_dns_info binaries should be
  placed in the location where the daemon is looking for
  (/usr/libexec/hypervkvpd/), or the daemon should be set to search for
  the binaries in the /usr/sbin directory.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Mauricio Faria de Oliveira]

Possible workaround w/ losetup.

# uname -rv
5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023

# cat /sys/module/loop/parameters/max_loop
8

# losetup -nl | sort
/dev/loop0 0  0 1  1 /var/lib/snapd/snaps/lxd_24322.snap
 0 512
/dev/loop1 0  0 1  1 /var/lib/snapd/snaps/snapd_18357.snap  
 0 512
/dev/loop2 0  0 1  1 /var/lib/snapd/snaps/core20_1822.snap  
 0 512

# ls -1 /dev/loop*
/dev/loop-control
/dev/loop0
/dev/loop1
/dev/loop2
/dev/loop3
/dev/loop4
/dev/loop5
/dev/loop6
/dev/loop7

# truncate -s 1g test1
# truncate -s 1g test2
# ls -lh test1 test2
-rw-r--r-- 1 root root 1.0G Apr  6 17:40 test1
-rw-r--r-- 1 root root 1.0G Apr  6 17:40 test2

# losetup /dev/loop7 test1
# losetup /dev/loop8 test2
losetup: /dev/loop8: failed to set up loop device: No such device or address

...

# losetup --show --find test1
/dev/loop3
# losetup --show --find test1
/dev/loop4
# losetup --show --find test1
/dev/loop5
# losetup --show --find test1
/dev/loop6
# losetup --show --find test1
/dev/loop8
# losetup --show --find test1
/dev/loop9
# losetup --show --find test1
/dev/loop10
# losetup --show --find test1
/dev/loop11
# losetup --show --find test1
/dev/loop12
# losetup --show --find test1
/dev/loop13
# strace -e ioctl losetup --show --find test1
ioctl(3, LOOP_CTL_GET_FREE) = 14
ioctl(4, LOOP_CONFIGURE, {fd=3, block_size=0, info={lo_offset=0, lo_number=0, 
lo_flags=0, lo_file_name="/root/test1", ...}}) = 0
/dev/loop14
+++ exited with 0 +++

# losetup -d /dev/loop3
# losetup -d /dev/loop4
# losetup -d /dev/loop5
# losetup -d /dev/loop6
# losetup -d /dev/loop8
# losetup -d /dev/loop9
# losetup -d /dev/loop10
# losetup -d /dev/loop11
# losetup -d /dev/loop12
# losetup -d /dev/loop13

# losetup /dev/loop8 test2
#

works now.

# cat /sys/module/loop/parameters/max_loop
8

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

Title:
  losetup with mknod fails on jammy with kernel 5.15.0-69-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  losetup fails with devices created manually by mknod on kernel
  5.15.0-69-generic

  # fallocate -l 1G test
  # mknod -m 660 /dev/loop8 b 7 8
  # chown root:disk /dev/loop8
  # losetup /dev/loop8 ./test
  losetup: ./test: failed to set up loop device: Device or resource busy

  Possibly as a result of this patch:
  
https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/

  which was introduced in 5.15.0-68:
  
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

  On a machine prior to this change (no issue with losetup):
  # cat /sys/module/loop/parameters/max_loop
  0
  # uname -r
  5.15.0-58-generic

  On a machine after the change (has losetup issue as described above):
  # cat /sys/module/loop/parameters/max_loop
  8
  # uname -r
  5.15.0-69-generic

  So it looks like the default changed and the max amount of loop
  devices that can be created with mknod (not loop-control) is 8. If we
  set max_loop=0 on the kernel command line, it works as before. Cannot
  unload and reload module on a running system to change the parameter
  because it is built into the kernel.

  Another workaround is to use `losetup --find` but that means you
  cannot create with named devices created with mknod.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions

[Roxana Nicolescu]

** Description changed:

  SRU justification
  
  [Impact]
  
  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.
  
  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.
  
  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.
  
  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
- When debian packages are prepared, you'll notice the file has changed its 
permission back to 755. 
+ When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.
  
  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  New

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages

[Dan]

Same issue here (very similar to above)

System-manufacturer : LENOVO
System-product-name : 20SUS51107
System-version : ThinkPad T15g Gen 1
Bios-release-date : 12/14/2022
Bios-version : N30ET49W (1.32)

5.19.0-38-generic #39~22.04.1-Ubuntu

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

Title:
  [i915] Intermittent freezing and LSPCON init failed kernel messages

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-oem-5.14 package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Lenovo ThinkPad model 20ST0055AU

  Boot messages show:
  [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on 
minor 0

  During normal operation there will intermittently be a freeze for a
  second or two and then more of these messages display in the kernel
  logs:

  [  505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D
  [  506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  The system will then become operational again.

  The system is still usable, but it is annoying.

  I've switched onto this OEM kernel from the generic kernel (5.13), as
  I had other problems with 5.13 regarding external displays not coming
  back after idle timeouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40
  ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21
  Uname: Linux 5.14.0-1036-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 10:29:31 2022
  InstallationDate: Installed on 2021-05-05 (371 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015498] [NEW] Debian autoreconstruct Fix restoration of execute permissions

[Roxana Nicolescu]

Public bug reported:

SRU justification

[Impact]

Debian source package diffs cannot represent that a file should
be executable.
gen-auto-reconstruct detects when a commit adds a script that is supposed to be 
invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

But, if a file removes its execute permission, this will change it back.
This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
removed the execute permission for a header file but then our scripts brought 
it back.

[Fix]
Andy proposed the following fix
https://dpaste.com/6SJ8YR3BM
Basically it checks if the permission was added or removed and uses either +x 
or -x.

[Test plan]
Easily tested with jammy-kvm, latest release where a rebase picked this commit
"treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
When debian packages are prepared, you'll notice the file has changed its 
permission back to 755. 
With the fix, it should be the same.

[Regression potential]
Low, it is a small fix. Scripts will still have execute permission.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Lunar)
 Importance: Undecided
 Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  New

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755. 
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

[Jaromir Obr]

@pyabo I solved it by installation of kernel 6.2:
https://github.com/pimlie/ubuntu-mainline-kernel.sh. So far no other
issue appeared, I'm using Ubuntu 22.10.

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Triaged
Status in linux-oem-6.1 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-525 -
525.105.17-0ubuntu1

---
libnvidia-nscq-525 (525.105.17-0ubuntu1) lunar; urgency=medium

  * New upstream release (LP: #2012529).
  * debian/rules:
- Fix the objdump path so that it is not for amd64 only. This
  gets the correct soname, and fixes the nscq provides.
  * debian/templates/libnvidia-nscq-BRANCH.install.in:
- Add the cli tools and include folders.

 -- Alberto Milone   Mon, 27 Mar 2023
19:34:42 +

** Changed in: libnvidia-nscq-525 (Ubuntu)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status 

[Kernel-packages] [Bug 2012743] Re: Support Nvidia BlueField-3 GPIO driver and pin controller

[Bartlomiej Zolnierkiewicz]

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Support Nvidia BlueField-3 GPIO driver and pin controller

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Support the BlueField-3 SoC GPIO driver for handling interrupts and providing 
the option to change the direction and value of a GPIO.
  Support the BlueField-3 SoC pin controller driver for allowing a select 
number of GPIO pins to be manipulated from userspace or the kernel.

  All these changes have been accepted for upstream but most of them are
  not yet in the tree/branches.

  PLEASE NOTE: This change is dependent on changes done in the ACPI
  tables. So the UEFI image needs to be updated accordingly.

  [Fix]

  * Add support for the BlueField-3 SoC GPIO driver.
  This driver configures and handles GPIO interrupts. It also enables a user to 
manipulate certain GPIO pins via libgpiod tools or other kernel drivers.
  The usable pins are defined via the "gpio-reserved-ranges" property.

  * NVIDIA BlueField-3 SoC has a few pins that can be used as GPIOs or
  take the default hardware functionality. Add a driver for the pin
  muxing.

  * The following gpiolib commits are bug fixes and are required for the gpio 
driver to work:
  443a0a0f0cf4f432c7af6654b7f2f920d411d379

  Although the following have been accepted by maintainers, they are not 
present in any tree/branch yet so
  these will be pushed as SAUCE for now:
  [PATCH v4] gpio: mmio: handle "ngpios" properly in bgpio_init()
  [PATCH v1] gpio: mmio: fix calculation of bgpio_bits

  [Test Case]

  * Check if the gpio-mlxbf3 driver is loaded
  * Check if the pinctrl-mlxbf3 driver is loaded
  * check if the mlxbf-gige driver is loaded
  * check if the pwr-mlxbf driver is loaded
  * Check that the oob_net0 interface is up and operational
  * Do reset and powercycle and check the oob_net0 interface again
  * Test power GPIO interrupt on BF3.

  [Regression Potential]

  * The Mellanox drivers could fail to be loaded.
  * The mlxbf-gige PHY interrupt or pwr-mlxbf interrupt could fail.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015455] acpidump.txt

[MRATT]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661676/+files/acpidump.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 

[Kernel-packages] [Bug 2015455] WifiSyslog.txt

[MRATT]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661675/+files/WifiSyslog.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 

[Kernel-packages] [Bug 2015455] ProcModules.txt

[MRATT]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661673/+files/ProcModules.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 

[Kernel-packages] [Bug 2015455] UdevDb.txt

[MRATT]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2015455/+attachment/5661674/+files/UdevDb.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 
prctl
    

[Kernel-packages] [Bug 2015455] ProcCpuinfoMinimal.txt

[MRATT]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661671/+files/ProcCpuinfoMinimal.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store 

[Kernel-packages] [Bug 2015455] ProcInterrupts.txt

[MRATT]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661672/+files/ProcInterrupts.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass 

[Kernel-packages] [Bug 2015455] ProcCpuinfo.txt

[MRATT]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661670/+files/ProcCpuinfo.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 

[Kernel-packages] [Bug 2015455] Lsusb-v.txt

[MRATT]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661669/+files/Lsusb-v.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 
prctl
 

[Kernel-packages] [Bug 2015455] Lsusb.txt

[MRATT]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2015455/+attachment/5661667/+files/Lsusb.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 
prctl
    

[Kernel-packages] [Bug 2015455] Lsusb-t.txt

[MRATT]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661668/+files/Lsusb-t.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 
prctl
 

[Kernel-packages] [Bug 2015455] Lspci.txt

[MRATT]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2015455/+attachment/5661665/+files/Lspci.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 
prctl
    

[Kernel-packages] [Bug 2015455] Lspci-vt.txt

[MRATT]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2015455/+attachment/5661666/+files/Lspci-vt.txt

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

Title:
  Intel PET not available on recent kernel causing QEMU VM crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi

  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.

  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.

  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html

  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021

  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520

  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.

  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 

[Kernel-packages] [Bug 2015455] Re: Intel PET not available on recent kernel causing QEMU VM crashes

[MRATT]

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  Hi
  
  Following a recent kernel update on Ubuntu Server 22.04.2 x86_64 to
  5.19.0-35 (& ..0-38), QEMU (via LXD) Windows Server 2022 VMs are
  crashing every day.
  
  The CPU has Intel PET feature, but I've had to disable tdp_mmu using
  modprobe so stabilise the VMs.
  
  The platform:
  -
  Linux 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 
21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
  
  The CPU tech specs on Dell R620:
  
https://www.intel.com/content/www/us/en/products/sku/75277/intel-xeon-processor-e52680-v2-25m-cache-2-80-ghz/specifications.html
  
  The work-around (success with modprobe):
  
  
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#KVM:_entry_failed.2C_hardware_error_0x8021
  
  LXD Issue:
  --
  https://github.com/lxc/lxd/issues/11520
  
  The QEMU log:
  -
  someadmin@us2204-iph-lxd03:/home/someadmin# cat 
/var/snap/lxd/common/lxd/logs/mw2022-ivm-test01/qemu.log.old
  qemu-system-x86_64: Issue while setting TUNSETSTEERINGEBPF: Invalid argument 
with fd: 48, prog_fd: -1
  KVM: entry failed, hardware error 0x8021
  
  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.
  
  EAX=0008 EBX=00040ee0 ECX=83ac EDX=
  ESI=32e2f000 EDI=32e26040 EBP=813d2810 ESP=813d2790
  EIP=8000 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=1 HLT=0
  ES =   00809300
  CS =8000 7ff8  00809300
  SS =   00809300
  DS =   00809300
  FS =   00809300
  GS =   00809300
  LDT=   
  TR =0040 ff2a 0067 8b00
  GDT= ff2a1fb0 0057
  IDT=  
  CR0=00050032 CR2=7c3fa0b0 CR3=001ae002 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=qemu-system-x86_64: ../hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: 
Assertion `ret < cpu->num_ases && ret >= 0' failed.
  
  The CPU via lscpu:
  --
  Architecture:x86_64
    CPU op-mode(s):32-bit, 64-bit
    Address sizes: 46 bits physical, 48 bits virtual
    Byte Order:Little Endian
  CPU(s):  40
    On-line CPU(s) list:   0-39
  Vendor ID:   GenuineIntel
    Model name:Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
  CPU family:  6
  Model:   62
  Thread(s) per core:  2
  Core(s) per socket:  10
  Socket(s):   2
  Stepping:4
  CPU max MHz: 3600.
  CPU min MHz: 1200.
  BogoMIPS:5599.96
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs 
ibpb stibp tpr_shad
   ow vnmi flexpriority ept vpid fsgsbase smep erms 
xsaveopt dtherm ida arat pln pts md_clear flush_l1d
  Virtualization features:
    Virtualization:VT-x
  Caches (sum of all):
    L1d:   640 KiB (20 instances)
    L1i:   640 KiB (20 instances)
    L2:5 MiB (20 instances)
    L3:50 MiB (2 instances)
  NUMA:
    NUMA node(s):  2
    NUMA node0 CPU(s): 
0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38
    NUMA node1 CPU(s): 
1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39
  Vulnerabilities:
    Itlb multihit: KVM: Mitigation: Split huge pages
    L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
    Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
    Meltdown:  Mitigation; PTI
    Mmio stale data:   Unknown: No mitigations
    Retbleed:  Not affected
    Spec store bypass: Mitigation; Speculative Store Bypass disabled via 
prctl
    Spectre v1:Mitigation; usercopy/swapgs barriers and __user 
pointer sanitization
    Spectre v2:Mitigation; Retpolines, IBPB conditional, IBRS_FW, 
STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
    Srbds: Not affected
    Tsx async abort:   Not affected
  
  QEMU 

[Kernel-packages] [Bug 2015292] Re: Missing ACPI device info in mlxbf_pka module

[Bartlomiej Zolnierkiewicz]

** Description changed:

- Config regarding BF ACPI devices and Window RAM is missing.
+ SRU Justification
+ 
+ [Impact]
+ Bluefield 3 ACPI/Window RAM configuration and related code is missing. This 
affects BF3 functionality w/ PKA Ring character devices being created correctly.
+ 
+ [Fix]
+ * Added ACPI config and code to detect BF3 hardware and provision the Ring 
devices correctly.
+ 
+ [Test Case]
+ * Tested on BF3 with mlxbf-pka module load and check the /dev/pka/ Ring 
char devices are created with correct number of entries.
+ * Tested with "openssl speed -engine pka -async_jobs 8 rsa" and verified the 
performance number show the PKA acceleration in place.
+ 
+ [Potential Regression]
+ * This fix has been tested with varieties of BF3: MB and HB cards.

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux-bluefield (Ubuntu)
   Status: In Progress => Invalid

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => Shih-Yi Chen (shihyic)

** Changed in: linux-bluefield (Ubuntu)
 Assignee: Shih-Yi Chen (shihyic) => (unassigned)

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

Title:
  Missing ACPI device info in mlxbf_pka module

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  Bluefield 3 ACPI/Window RAM configuration and related code is missing. This 
affects BF3 functionality w/ PKA Ring character devices being created correctly.

  [Fix]
  * Added ACPI config and code to detect BF3 hardware and provision the Ring 
devices correctly.

  [Test Case]
  * Tested on BF3 with mlxbf-pka module load and check the /dev/pka/ Ring 
char devices are created with correct number of entries.
  * Tested with "openssl speed -engine pka -async_jobs 8 rsa" and verified the 
performance number show the PKA acceleration in place.

  [Potential Regression]
  * This fix has been tested with varieties of BF3: MB and HB cards.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015491] [NEW] Introduce the 530 (UDA) NVIDIA driver series in Bionic, Focal, Jammy, Kinetic, Lunar

[Alberto Milone]

Public bug reported:

[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates

Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.

[Discussion]

[Changelog]

** Affects: nvidia-graphics-drivers-525 (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-525 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-525 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-525 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Affects: nvidia-graphics-drivers-525 (Ubuntu Kinetic)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

** Package changed: nvidia-graphics-drivers-525-server (Ubuntu) =>
nvidia-graphics-drivers-525 (Ubuntu)

** Also affects: nvidia-graphics-drivers-525 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-525 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-525 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-525 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-525-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2015491

Title:
  Introduce the 530 (UDA) NVIDIA driver series in Bionic, Focal, Jammy,
  Kinetic, Lunar

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2015491/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015307] Re: mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3

[Bartlomiej Zolnierkiewicz]

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux-bluefield (Ubuntu)
   Status: New => Invalid

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => Liming Sun (limings)

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

Title:
  mmc: sdhci-of-dwcmshc: Add runtime PM operations for BlueField-3

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to avoid unnecessary eMMC GPIO toggling when eMMC is 
idle

  [Fix]
  The fix implements the runtime PM operations for BlueField-3 SoC to disable 
the card clock when idle.

  [Test Case]
  Same functionality and testing as on BlueField-1/2.

  [Regression Potential]
  Same behavior from user perspective.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2013383] Re: mlxbf-bootctl: support SMC call for setting ARM boot state

[Bartlomiej Zolnierkiewicz]

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  mlxbf-bootctl: support SMC call for setting ARM boot state

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  In Progress
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Add a new SMC call which allows setting the ARM boot progress state to
  "OS is up".

  [Fix]

  * Add a new SMC call in mlxbf-bootctl which allows setting the ARM
  boot progress state to "OS is up".

  [Test Case]

  * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists

  [Regression Potential]

  * No known regression because it is just adding a sysfs entry. It is
  backward compatible with older TAF images. If the SMC call is not
  supported by ATF, it is ignored.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2011738] Re: Add ATX related reporting nodes in mlxbf-ptm debugfs driver

[Bartlomiej Zolnierkiewicz]

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Add ATX related reporting nodes in mlxbf-ptm debugfs driver

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  mlxbf-ptm is a kernel driver that provides debufgs interface for
  system software to monitor Bluefield devices' power and thermal
  management parameters.

  [Fix]

  * This change adds additional debugfs nodes that provide ATX status
  and power profile data. Replaces S_IRUGO with 0444 inline with
  checkpatch expectation.

  [Test Case]

  * After installing the kernel module, debugfs entry at 
/sys/kernel/debug/mlxbf-ptm will be created
  * monitors/status folder contains read-only parameters reported from the 
Bluefield device

  [Regression Potential]

  * Minimal - as these are read-only parameters that report Bluefield
  device information.

  [Other]
  * This code is likely to change depending on feedback we received from 
maintainers.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2012649] Re: mlxbf_gige: need to replace SAUCE patches with upstream commits

[Bartlomiej Zolnierkiewicz]

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  mlxbf_gige: need to replace SAUCE patches with upstream commits

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
  patches that enable BlueField-3 support.  This same functionality
  is contained in upstream commits and Jammy repo should utilize them.

  [Fix]
  The BlueField-3 support will be provided in the form of a set
  of upstream patches, to be sent in as a pull request.

  [Test Case]
  Should test on both BlueField-2 & BlueField-3: 
 Boot platform and bring up "oob_net0" interface properly
 Test that network traffic works properly

  [Regression Potential]
  The upstream commits have been reviewed and tested well,
  so there should be low risk of regression.

  [Other]
  n/a

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  kernel: fix __clear_user() inline assembly constraints

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  In Progress

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * In case clear_user() crosses two pages and faults on the second page
 the kernel may write lowcore contents to the first page, instead of
     clearing it.

   * The __clear_user() inline assembly misses earlyclobber constraint
     modifiers. Depending on compiler and compiler options this may lead to
     incorrect code which copies kernel lowcore contents to user space 
 instead of clearing memory, in case clear_user() faults.

  [Fix]

   * For Kinetic and Jammy cherrypick of
 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3
 "s390/uaccess: add missing earlyclobber annotations to __clear_user()"

   * For Focal and Bionic a backport of the above commit is needed:
 https://launchpadlibrarian.net/659551648/s390-uaccess.patch

  [ Test Plan ]

   * A test program in C is needed and used for testing.

   * The test will be done by IBM.

  [ Where problems could occur ]

   * The modification is limited to function 'long __clear_user'.

   * And there, just to one inline assembly constraints line.

   * This is usually difficult to trace.

   * A erroneous modification may lead to a wrong behavior in
     'long __clear_user',

   * and maybe returning a wrong size (in uaccess.c).

  [ Other Info ]

   * This affects all Ubuntu releases in service, down to 18.04.

   * Since we are close to 23.04 kernel freeze, I submit a patch request for
     23.04 separately, and submit the SRU request for the all other
     Ubuntu releases later.

  __

  Description:   kernel: fix __clear_user() inline assembly constraints

  Symptom:   In case clear_user() crosses two pages and faults on the
     second page the kernel may write lowcore contents to the
     first page, instead of clearing it.

  Problem:   The __clear_user() inline assembly misses earlyclobber
     constraint modifiers. Depending on compiler and compiler
     options this may lead to incorrect code which copies kernel
     lowcore contents to user space instead of clearing memory,
     in case clear_user() faults.

  Solution:  Add missing earlyclobber constraint modifiers.
  Preventive:yes

  Upstream-ID:   89aba4c26fae4e459f755a18912845c348ee48f3

  Affected Releases:
     18.04
     20.04
     22.04
     22.10
     23.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015352] Re: System hangs during boot, When the Intel E810 NIC driver is used to create bonding.

[Chris Stone]

This is impacting us too, and we found that there was no issue in the
5.15.0-67 kernel, but the issue is present in 5.15.0-69. Building and
installing the 1.10.1.2.2 ice driver from Intel prior to running
'netplan apply' seems to prevent the hang.

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

Title:
  System hangs during boot, When the Intel E810 NIC driver is used to
  create bonding.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description: 
  On a Dell EMC PE system configured with Intel E810 card installed with Ubuntu 
22.04.2. 
  When bonding is enabled on the server, the system will hang at the 
initialization of OS.
  The kernel loads, but the system hang around the time it starts the Network 
Services by reporting below messages.

  echo 0 > /proc/sys/kernel/hung_task_timeout_secs”  disables this message.
  INFO: task systemd-network:1769 blocked for more than 120 seconds
   not tained 5.15.0-69-generic #76-ubuntu

  Steps to reproduce:
  1. Configure Dell EMC PE system with Intel E-810 NIC.
  2. Install Ubuntu 22.04.2 and boot into OS.
  3. Create a bonding interface by editing netplan configuration file as below.
  bonds:
  bond0:
dhcp4: true
interfaces: [enp209s0f0, enp209s0f1]
parameters:
  mode: active-backup
  Where [enp209s0f0, enp209s0f1] are Intel E-810 Interfaces.
  4. Execute #Netplan apply and reboot the system.
  5. Observe system hangs at starting Network Services.

  Actual Results:
  System hang is observed.

  Expected results:
  No system hang should be Observe.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-oracle/5.15.0-1033.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-oracle verification-needed-jammy

-- 
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/2009325

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command 

[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

[Tim Gardner]

** Tags removed: verification-needed-bionic verification-needed-focal 
verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-bionic verification-done-focal 
verification-done-jammy verification-done-kinetic

-- 
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/2009325

Title:
  NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-aws source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Invalid

Bug description:
  After updating on the kernel 
  5.4.0-144.161 at Ubuntu 18 and 
  5.15.0-67.74 at Ubuntu 20, 
  we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our 
NFS servers.

  All clients are extremely slow when it comes to access to the NFS
  resources.

  Restart and use older kernel, fixed the problem.
  Ubuntu 18 5.4.0-139-generic
  Ubuntu 20 5.15.0-60-Generic
  I don't have a NFS problem with this kernel.

  Problem came with the last releas on March 3rd, 2023
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:00 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-67-generic N/A
   linux-backports-modules-5.15.0-67-generic  N/A
   linux-firmware 1.187.36
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal
  Uname: Linux 5.15.0-67-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mär  4 15:03 seq
   crw-rw 1 root audio 116, 33 Mär  4 15:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic 
root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto 
elevator=noop
  ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-43-generic N/A
   linux-backports-modules-5.0.0-43-generic  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-450 -
450.236.01-0ubuntu0.18.04.1

---
fabric-manager-450 (450.236.01-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:04:21 +

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-470 -
470.182.03-0ubuntu0.18.04.1

---
fabric-manager-470 (470.182.03-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:13:26 +

** Changed in: fabric-manager-450 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-525 -
525.105.17-0ubuntu0.18.04.1

---
fabric-manager-525 (525.105.17-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
18:59:58 +

** Changed in: fabric-manager-515 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-515 -
515.105.01-0ubuntu0.18.04.1

---
fabric-manager-515 (515.105.01-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:27:45 +

** Changed in: fabric-manager-470 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-450 -
450.236.01-0ubuntu0.18.04.1

---
libnvidia-nscq-450 (450.236.01-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
15:51:07 +

** Changed in: fabric-manager-525 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-470 -
470.182.03-0ubuntu0.18.04.1

---
libnvidia-nscq-470 (470.182.03-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
16:07:46 +

** Changed in: libnvidia-nscq-450 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.182.03-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-470 (470.182.03-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
09:43:25 +

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.236.01-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-450-server (450.236.01-0ubuntu0.18.04.1) bionic; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Thu, 23 Mar 2023
11:34:48 +

** Changed in: libnvidia-nscq-515 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-515 -
515.105.01-0ubuntu0.18.04.1

---
libnvidia-nscq-515 (515.105.01-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
16:35:07 +

** Changed in: libnvidia-nscq-470 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.182.03-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-470-server (470.182.03-0ubuntu0.18.04.1) bionic; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Fri, 24 Mar 2023
14:09:28 +

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515 -
515.105.01-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-515 (515.105.01-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).
  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.

 -- Alberto Milone   Mon, 27 Mar 2023
10:21:50 +

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515-server -
515.105.01-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-515-server (515.105.01-0ubuntu0.18.04.1) bionic; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Fri, 24 Mar 2023
15:48:11 +

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.105.17-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-525 (525.105.17-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
11:41:32 +

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-515 -
515.105.01-0ubuntu0.20.04.1

---
fabric-manager-515 (515.105.01-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:27:20 +

** Changed in: fabric-manager-470 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.105.17-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-525-server (525.105.17-0ubuntu0.18.04.1) bionic; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
18:36:26 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-470 -
470.182.03-0ubuntu0.20.04.1

---
fabric-manager-470 (470.182.03-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:13:04 +

** Changed in: fabric-manager-450 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-450 -
450.236.01-0ubuntu0.20.04.1

---
fabric-manager-450 (450.236.01-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:03:51 +

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-525 -
525.105.17-0ubuntu0.20.04.1

---
fabric-manager-525 (525.105.17-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
18:59:29 +

** Changed in: fabric-manager-515 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-450 -
450.236.01-0ubuntu0.20.04.1

---
libnvidia-nscq-450 (450.236.01-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
15:47:26 +

** Changed in: fabric-manager-525 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-515 -
515.105.01-0ubuntu0.20.04.1

---
libnvidia-nscq-515 (515.105.01-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
16:32:41 +

** Changed in: libnvidia-nscq-470 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-470 -
470.182.03-0ubuntu0.20.04.1

---
libnvidia-nscq-470 (470.182.03-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
16:06:24 +

** Changed in: libnvidia-nscq-450 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.236.01-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-450-server (450.236.01-0ubuntu0.20.04.1) focal; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Thu, 23 Mar 2023
11:33:01 +

** Changed in: libnvidia-nscq-515 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515-server -
515.105.01-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-515-server (515.105.01-0ubuntu0.20.04.1) focal; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Fri, 24 Mar 2023
15:36:26 +

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515 -
515.105.01-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-515 (515.105.01-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).
  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.

 -- Alberto Milone   Mon, 27 Mar 2023
10:17:44 +

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.182.03-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-470 (470.182.03-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
09:41:57 +

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.182.03-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-470-server (470.182.03-0ubuntu0.20.04.1) focal; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Fri, 24 Mar 2023
14:04:10 +

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.105.17-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-525-server (525.105.17-0ubuntu0.20.04.1) focal; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
18:35:52 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-450 -
450.236.01-0ubuntu0.22.04.1

---
fabric-manager-450 (450.236.01-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:02:29 +

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-470 -
470.182.03-0ubuntu0.22.04.1

---
fabric-manager-470 (470.182.03-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:12:26 +

** Changed in: fabric-manager-450 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.105.17-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-525 (525.105.17-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
11:40:24 +

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Focal)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-515 -
515.105.01-0ubuntu0.22.04.1

---
fabric-manager-515 (515.105.01-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:26:48 +

** Changed in: fabric-manager-470 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-525 -
525.105.17-0ubuntu0.22.04.1

---
fabric-manager-525 (525.105.17-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
18:59:11 +

** Changed in: fabric-manager-515 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-450 -
450.236.01-0ubuntu0.22.04.1

---
libnvidia-nscq-450 (450.236.01-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
15:45:41 +

** Changed in: fabric-manager-525 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-515 -
515.105.01-0ubuntu0.22.04.1

---
libnvidia-nscq-515 (515.105.01-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
16:30:26 +

** Changed in: libnvidia-nscq-470 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package libnvidia-nscq-470 -
470.182.03-0ubuntu0.22.04.1

---
libnvidia-nscq-470 (470.182.03-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
16:04:23 +

** Changed in: libnvidia-nscq-450 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Fix 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470 -
470.182.03-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-470 (470.182.03-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
09:40:36 +

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.236.01-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-450-server (450.236.01-0ubuntu0.22.04.1) jammy; 
urgency=medium

  * New upstream release (LP: #2012529).
  * debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch:
- Fix build issues with Linux 6.2.

 -- Alberto Milone   Thu, 23 Mar 2023
11:31:12 +

** Changed in: libnvidia-nscq-515 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515 -
515.105.01-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-515 (515.105.01-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).
  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.
- Switch to libcuda.so.1 and libnvidia-ml.so.1 provides.

 -- Alberto Milone   Mon, 27 Mar 2023
10:15:38 +

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.182.03-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-470-server (470.182.03-0ubuntu0.22.04.1) jammy; 
urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Fri, 24 Mar 2023
14:00:16 +

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-515-server -
515.105.01-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-515-server (515.105.01-0ubuntu0.22.04.1) jammy; 
urgency=medium

  * New upstream release (LP: #2012529).
  * debian/templates/control.in:
- Switch to libcuda.so.1 and libnvidia-ml.so.1 provides.

 -- Alberto Milone   Fri, 24 Mar 2023
14:47:42 +

** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.105.17-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-525 (525.105.17-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
11:39:05 +

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-470 -
470.182.03-0ubuntu0.22.10.1

---
fabric-manager-470 (470.182.03-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:12:03 +

** Changed in: fabric-manager-450 (Ubuntu Kinetic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-450 -
450.236.01-0ubuntu0.22.10.1

---
fabric-manager-450 (450.236.01-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:01:59 +

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.105.17-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-525-server (525.105.17-0ubuntu0.22.04.1) jammy; 
urgency=medium

  * New upstream release (LP: #2012529).
  * debian/templates/control.in:
- Switch to libcuda.so.1 and libnvidia-ml.so.1 provides.

 -- Alberto Milone   Mon, 27 Mar 2023
18:33:41 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in 

[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}

[Launchpad Bug Tracker]

This bug was fixed in the package fabric-manager-515 -
515.105.01-0ubuntu0.22.10.1

---
fabric-manager-515 (515.105.01-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream release (LP: #2012529).

 -- Alberto Milone   Mon, 27 Mar 2023
17:26:00 +

** Changed in: fabric-manager-470 (Ubuntu Kinetic)
   Status: New => Fix Released

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

Title:
  NVIDIA CVE-2023-{0180 to 0195}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Fix Released
Status in fabric-manager-525 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-525 source package in Bionic:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in fabric-manager-515 source package in Focal:
  Fix Released
Status in fabric-manager-525 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-515 source package in Focal:
  Fix Released
Status in libnvidia-nscq-525 source package in Focal:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Jammy:
  Fix Released
Status in fabric-manager-470 source package in Jammy:
  Fix Released
Status in fabric-manager-515 source package in Jammy:
  Fix Released
Status in fabric-manager-525 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-525 source package in Jammy:
  New
Status in linux-restricted-modules source package in Jammy:
  New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy: