This bug was fixed in the package linux-oem-6.0 - 6.0.0-1019.19
---------------
linux-oem-6.0 (6.0.0-1019.19) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1019.19 -proposed tracker (LP: #2024151)
* CVE-2023-2430
- io_uring: get rid of double locking
- io_uring: extract a io_msg_install_complete helper
- io_uring/msg_ring: move double lock/unlock helpers higher up
- io_uring/msg_ring: fix missing lock on overflow for IOPOLL
* Various backlight issues with the 6.0 kernel (LP: #2023638)
- ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type()
- ACPI: video: Make acpi_backlight=video work independent from GPU driver
- SAUCE: ACPI: video: Stop trying to use vendor backlight control on laptops
from after ~2012
* CVE-2022-4842
- fs/ntfs3: Fix attr_punch_hole() null pointer derenference
* CVE-2023-2124
- xfs: verify buffer contents when we skip log replay
* CVE-2023-0597
- x86/kasan: Map shadow for percpu pages on demand
- x86/mm: Randomize per-cpu entry area
- x86/mm: Recompute physical address for every page of per-CPU CEA mapping
- x86/mm: Populate KASAN shadow for entire per-CPU range of CPU entry area
- x86/mm: Do not shuffle CPU entry areas without KASLR
* cls_flower: off-by-one in fl_set_geneve_opt (LP: #2023577)
- net/sched: flower: fix possible OOB write in fl_set_geneve_opt()
* Some INVLPG implementations can leave Global translations unflushed when
PCIDs are enabled (LP: #2023220)
- x86/mm: Avoid incomplete Global INVLPG flushes
* CVE-2023-2176
- RDMA/core: Refactor rdma_bind_addr
* Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C
dongle (LP: #2021949)
- thunderbolt: Increase timeout of DP OUT adapter handshake
- thunderbolt: Do not touch CL state configuration during discovery
- thunderbolt: Increase DisplayPort Connection Manager handshake timeout
* CVE-2023-1073
- HID: check empty report_list in hid_validate_values()
* CVE-2023-0459
- uaccess: Add speculation barrier to copy_from_user()
* selftest: fib_tests: Always cleanup before exit (LP: #2015956)
- selftest: fib_tests: Always cleanup before exit
-- Timo Aaltonen <timo.aalto...@canonical.com> Tue, 20 Jun 2023
12:57:07 +0300
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4842
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0459
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0597
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-1073
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2124
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2176
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2430
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2023638
Title:
Various backlight issues with the 6.0/6.1 kernel
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
There are some new patches for new method to decide which backlight driver
should be registered introduced since 6.1. And we backport some of them to
6.0-oem kernel which are not enough to solved all backlight issues.
1. dell_laptop created a non-working backlight driver before nvidia is
loaded, that leads to the system can't adjust the display brightness.
2. acpi_backlight0 sometimes will be generated together with intel_backlight.
[Fix]
Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being
registered automatically(which have been included into ubuntu kernels through
stable update)
e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU
driver
78dfc9d1d1ab ACPI: video: Add auto_detect arg to
__acpi_video_get_backlight_type()
Below patch prevents platform driver(dell_laptop) from creating backlight
driver after win8.
aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on
laptops from after ~2012
https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/
[Test]
Verified on the dell platform which reports this issue.
[Where problems could occur]
The assumption of the not-yet-upstreamed commit regarding backlight control
is that, after Windows 8, all laptop backlights are controlled either by ACPI
or the native graphics driver. It impacts the laptops that do not follow the
assumption and will lead to broken backlight interface.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023638/+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
