[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy

[Robie Basak]

Hello William, or anyone else affected,

Accepted linux-firmware-raspi2 into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/linux-firmware-raspi2/4-0ubuntu0~20.10.1 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
       Status: New => Fix Committed

** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1925971

Title:
  SRU bluetooth fixes and CVEs to focal and groovy

Status in linux-firmware-raspi2 package in Ubuntu:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Fix Committed
Status in linux-firmware-raspi2 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the CM4 and Pi 400

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a CM4.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Repeat the above steps for the Pi 400

  [Regression Potential]

  There are some diversions and other firmware updates that could
  potentially cause issues. These have been tested on lots of different
  pi hardware and no issues have been discovered. There is also an
  included Spectra CVE fix which is very low risk.

  [Original Description]
  Hirsute has some patches that address CVEs and enable bluetooth/wifi on the CM4 and 400. They need to be SRU'd to focal and groovy.

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