GHSA-6CJF-8QC7-QPW7
Vulnerability from github – Published: 2025-07-04 15:31 – Updated: 2025-07-04 15:31In the Linux kernel, the following vulnerability has been resolved:
EDAC/igen6: Fix NULL pointer dereference
A kernel panic was reported with the following kernel log:
EDAC igen6: Expected 2 mcs, but only 1 detected. BUG: unable to handle page fault for address: 000000000000d570 ... Hardware name: Notebook V54x_6x_TU/V54x_6x_TU, BIOS Dasharo (coreboot+UEFI) v0.9.0 07/17/2024 RIP: e030:ecclog_handler+0x7e/0xf0 [igen6_edac] ... igen6_probe+0x2a0/0x343 [igen6_edac] ... igen6_init+0xc5/0xff0 [igen6_edac] ...
This issue occurred because one memory controller was disabled by the BIOS but the igen6_edac driver still checked all the memory controllers, including this absent one, to identify the source of the error. Accessing the null MMIO for the absent memory controller resulted in the oops above.
Fix this issue by reverting the configuration structure to non-const and updating the field 'res_cfg->num_imc' to reflect the number of detected memory controllers.
{
"affected": [],
"aliases": [
"CVE-2025-38178"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-07-04T14:15:24Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/igen6: Fix NULL pointer dereference\n\nA kernel panic was reported with the following kernel log:\n\n EDAC igen6: Expected 2 mcs, but only 1 detected.\n BUG: unable to handle page fault for address: 000000000000d570\n ...\n Hardware name: Notebook V54x_6x_TU/V54x_6x_TU, BIOS Dasharo (coreboot+UEFI) v0.9.0 07/17/2024\n RIP: e030:ecclog_handler+0x7e/0xf0 [igen6_edac]\n ...\n igen6_probe+0x2a0/0x343 [igen6_edac]\n ...\n igen6_init+0xc5/0xff0 [igen6_edac]\n ...\n\nThis issue occurred because one memory controller was disabled by\nthe BIOS but the igen6_edac driver still checked all the memory\ncontrollers, including this absent one, to identify the source of\nthe error. Accessing the null MMIO for the absent memory controller\nresulted in the oops above.\n\nFix this issue by reverting the configuration structure to non-const\nand updating the field \u0027res_cfg-\u003enum_imc\u0027 to reflect the number of\ndetected memory controllers.",
"id": "GHSA-6cjf-8qc7-qpw7",
"modified": "2025-07-04T15:31:08Z",
"published": "2025-07-04T15:31:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38178"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/40e69c93d6dadc5355bfe90f3940c402d171289c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/88efa0de3285be66969b71ec137d9dab1ee19e52"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.