This bug was fixed in the package linux-azure-6.5 - 6.5.0-1017.17~22.04.1
--------------- linux-azure-6.5 (6.5.0-1017.17~22.04.1) jammy; urgency=medium
* jammy/linux-azure-6.5: 6.5.0-1017.17~22.04.1 -proposed tracker (LP: #2056031)
[ Ubuntu: 6.5.0-1017.17 ]
* mantic/linux-azure: 6.5.0-1017.17 -proposed tracker (LP: #2056032) * mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * CVE-2024-26599 - pwm: Fix out-of-bounds access in of_pwm_single_xlate() * CVE-2024-26597 - net: qualcomm: rmnet: fix global oob in rmnet_policy * CVE-2024-1086 - netfilter: nf_tables: reject QUEUE/DROP verdict parameters * CVE-2024-1085 - netfilter: nf_tables: check if catch-all set element is active in next generation
-- Tim Gardner <email address hidden> Fri, 08 Mar 2024 20:35:08 -0700
This bug was fixed in the package linux-azure-6.5 - 6.5.0-1017. 17~22.04. 1
--------------- 1017.17~ 22.04.1) jammy; urgency=medium
linux-azure-6.5 (6.5.0-
* jammy/linux- azure-6. 5: 6.5.0-1017. 17~22.04. 1 -proposed tracker
(LP: #2056031)
[ Ubuntu: 6.5.0-1017.17 ]
* mantic/linux-azure: 6.5.0-1017.17 -proposed tracker (LP: #2056032) dkms-versions -- update from kernel-versions (main/s2024.02.05) single_ xlate()
* mantic/linux: 6.5.0-26.26 -proposed tracker (LP: #2056049)
* Packaging resync (LP: #1786013)
- [Packaging] update annotations scripts
- debian/
* CVE-2024-26599
- pwm: Fix out-of-bounds access in of_pwm_
* CVE-2024-26597
- net: qualcomm: rmnet: fix global oob in rmnet_policy
* CVE-2024-1086
- netfilter: nf_tables: reject QUEUE/DROP verdict parameters
* CVE-2024-1085
- netfilter: nf_tables: check if catch-all set element is active in next
generation
-- Tim Gardner <email address hidden> Fri, 08 Mar 2024 20:35:08 -0700