The system with VMD enabled may encounter hang
Bug #2110178 reported by
AceLan Kao
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux-oem-6.11 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
AceLan Kao | ||
linux-oem-6.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
AceLan Kao |
Bug Description
[Impact]
After 6.11.0-1009-oem kernel, we merged the sauce patch of the VMD PCH support, and it may lead to a system hang when trying to access /proc/iomem directly.
[Fix]
The VMD PCH support patches still didn't find its way to the upstream, and Intel need more time to process it. So, we simply fix this issue by using static strings.
[Test]
1. Boot up the machine with VMD enabled
2. Run `sudo fwts -q --stdout-summary -r mtrr mtrr` to make it access /proc/iomem directly
3. It should show FAILED_MEDIUM
4. Reboot and re-try step 2 for around 10 times
5. If it fails, it shows Killed
[Where problems could occur]
Only change the strings to static, it increases the kernel size a couple bytes.
CVE References
- 2025-37797
- 2025-37799
- 2025-37800
- 2025-37801
- 2025-37802
- 2025-37803
- 2025-37804
- 2025-37805
- 2025-37806
- 2025-37807
- 2025-37808
- 2025-37809
- 2025-37810
- 2025-37811
- 2025-37812
- 2025-37813
- 2025-37814
- 2025-37815
- 2025-37816
- 2025-37817
- 2025-37818
- 2025-37819
- 2025-37820
- 2025-37821
- 2025-37822
- 2025-37823
- 2025-37824
- 2025-37825
- 2025-37826
- 2025-37827
- 2025-37828
- 2025-37829
- 2025-37830
- 2025-37831
- 2025-37832
- 2025-37833
- 2025-37834
- 2025-37876
- 2025-37877
- 2025-37878
- 2025-37879
- 2025-37880
- 2025-37881
- 2025-37882
- 2025-37883
- 2025-37884
- 2025-37885
- 2025-37886
- 2025-37887
- 2025-37888
Changed in linux-oem-6.11 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-6.11 (Ubuntu Noble): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-noble-linux-oem-6.11 removed: verification-needed-noble-linux-oem-6.11 |
Changed in linux-oem-6.14 (Ubuntu Noble): | |
status: | New → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-6.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-6.14 (Ubuntu Noble): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-noble-linux-oem-6.14 removed: verification-needed-noble-linux-oem-6.14 |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 6.11/6. 11.0-1023. 23 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- noble-linux- oem-6.11' to 'verification- done-noble- linux-oem- 6.11'. If the problem still exists, change the tag 'verification- needed- noble-linux- oem-6.11' to 'verification- failed- noble-linux- oem-6.11' .
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!