This bug was fixed in the package linux-lowlatency-hwe-6.5 - 6.5.0-26.26.1~22.04.1
--------------- linux-lowlatency-hwe-6.5 (6.5.0-26.26.1~22.04.1) jammy; urgency=medium
* jammy/linux-lowlatency-hwe-6.5: 6.5.0-26.26.1~22.04.1 -proposed tracker (LP: #2056036)
[ Ubuntu: 6.5.0-26.26.1 ]
* mantic/linux-lowlatency: 6.5.0-26.26.1 -proposed tracker (LP: #2056037) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/s2024.02.05) * 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
-- Roxana Nicolescu <email address hidden> Wed, 13 Mar 2024 10:29:44 +0100
This bug was fixed in the package linux-lowlatenc y-hwe-6. 5 - 6.5.0-26. 26.1~22. 04.1
--------------- y-hwe-6. 5 (6.5.0- 26.26.1~ 22.04.1) jammy; urgency=medium
linux-lowlatenc
* jammy/linux- lowlatency- hwe-6.5: 6.5.0-26. 26.1~22. 04.1 -proposed tracker
(LP: #2056036)
[ Ubuntu: 6.5.0-26.26.1 ]
* mantic/ linux-lowlatenc y: 6.5.0-26.26.1 -proposed tracker (LP: #2056037) dkms-versions -- update from kernel-versions (main/s2024.02.05) dkms-versions -- update from kernel-versions (main/s2024.02.05) single_ xlate()
* Packaging resync (LP: #1786013)
- debian/
* 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
-- Roxana Nicolescu <email address hidden> Wed, 13 Mar 2024 10:29:44 +0100