Fix acpi_power_meter accessing IPMI region before it's ready
Bug #2059263 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Committed
|
Medium
|
Unassigned | ||
Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Medium
|
Unassigned | ||
Noble |
Fix Released
|
Medium
|
Unassigned | ||
linux-oem-6.5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned | ||
Mantic |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
ACPI error can be found in kernel message:
[ 3.717920] ACPI Error: No handler for Region [SYSI] (00000000ab9e62c5) [IPMI] (20230628/
[Fix]
On Dell systems that have IPI0001 device, ensure IPMI region is ready
before acpi_power_meter invokes any ACPI method.
[Test]
With the patch applied, no such error can be found in kernel message.
acpi_power_meter sysfs also works correctly.
[Where problems could occur]
If asynchronous probe is disabled, the device drivers that probe after
acpi_power_meter needs to wait until the completion is done, hence the
boot time might be slower.
CVE References
- 2023-52880
- 2023-6270
- 2024-21823
- 2024-23307
- 2024-24861
- 2024-26593
- 2024-26642
- 2024-26643
- 2024-26694
- 2024-26710
- 2024-26712
- 2024-26733
- 2024-26734
- 2024-26735
- 2024-26736
- 2024-26748
- 2024-26782
- 2024-26789
- 2024-26790
- 2024-26792
- 2024-26798
- 2024-26802
- 2024-26803
- 2024-26809
- 2024-26838
- 2024-26889
- 2024-26890
- 2024-26922
- 2024-26923
- 2024-26924
- 2024-26925
- 2024-26926
Changed in linux (Ubuntu Noble): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Mantic): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Noble): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Jammy): | |
status: | New → Won't Fix |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | New → Confirmed |
Changed in linux-oem-6.5 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Noble): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
importance: | Undecided → Medium |
tags: | added: oem-priority originate-from-2045933 somerville |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-jammy-linux-oem-6.5 removed: verification-needed-jammy-linux-oem-6.5 |
Changed in linux (Ubuntu Mantic): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu Noble): | |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done-noble-linux removed: verification-needed-noble-linux |
tags: |
added: verification-done-mantic-linux removed: verification-needed-mantic-linux |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 6.5/6.5. 0-1021. 22 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-linux- oem-6.5' to 'verification- done-jammy- linux-oem- 6.5'. If the problem still exists, change the tag 'verification- needed- jammy-linux- oem-6.5' to 'verification- failed- jammy-linux- oem-6.5' .
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!