Fix UBSAN in Intel EDAC driver
Bug #2028746 reported by
Kai-Heng Feng
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HWE Next |
New
|
Undecided
|
Unassigned | ||
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
| Lunar |
Won't Fix
|
Low
|
Unassigned | ||
| linux-oem-6.1 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Low
|
Unassigned | ||
| Lunar |
Invalid
|
Undecided
|
Unassigned | ||
| linux-oem-6.5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
| Lunar |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
UBSAN complains shift-out-
[ 13.875276] UBSAN: shift-out-of-bounds in drivers/
[ 13.875279] shift exponent -66 is negative
[Fix]
Skip the absent memory controllers so ~0 won't be used.
[Test]
Boot system with patch applied, no more UBSAN error in dmesg.
[Where problems could occur]
The fix itself is trivial, however the dependency patches may bring
behavioural changes as new platform support is also added.
| Changed in linux (Ubuntu Jammy): | |
| status: | New → Won't Fix |
| Changed in linux (Ubuntu Lunar): | |
| status: | New → Confirmed |
| Changed in linux-oem-6.1 (Ubuntu): | |
| status: | New → Invalid |
| Changed in linux-oem-6.1 (Ubuntu Jammy): | |
| status: | New → Confirmed |
| Changed in linux-oem-6.1 (Ubuntu Lunar): | |
| status: | New → Invalid |
| Changed in linux-oem-6.1 (Ubuntu Jammy): | |
| importance: | Undecided → Low |
| Changed in linux (Ubuntu Lunar): | |
| importance: | Undecided → Low |
| tags: | added: oem-priority originate-from-1990358 somerville |
| Changed in linux (Ubuntu Lunar): | |
| status: | Confirmed → Fix Committed |
| Changed in linux (Ubuntu): | |
| status: | New → Fix Released |
| tags: |
added: verification-done-lunar-linux removed: verification-needed-lunar-linux |
| Changed in linux-oem-6.5 (Ubuntu): | |
| status: | New → Invalid |
| Changed in linux-oem-6.5 (Ubuntu Lunar): | |
| status: | New → Invalid |
| Changed in linux-oem-6.5 (Ubuntu Jammy): | |
| status: | New → Fix Committed |
| Changed in linux-oem-6.1 (Ubuntu Jammy): | |
| status: | Confirmed → Fix Committed |
| tags: |
added: verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 removed: verification-needed-jammy-linux-oem-6.1 verification-needed-jammy-linux-oem-6.5 |
| Changed in linux-oem-6.5 (Ubuntu Jammy): | |
| status: | Fix Committed → Fix Released |
| tags: | added: kernel-daily-bug |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 6.5/6.5. 0-1002. 2 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!