CVE-2022-50320
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 5.19.17 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.0.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's ACPI FPDT table handling. On certain hardware (like the Packard Bell Dot SC with Intel Atom N2600), the FPDT table contains invalid physical addresses that fall outside the CPU's supported physical address range. When the kernel calls acpi_os_map_memory() on these invalid addresses, it triggers a warning and causes a kernel oops (crash/stacktrace). The issue is fixed by adding verification of the physical address before mapping it to avoid the crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash or produce a stacktrace (kernel oops) when it attempts to map invalid physical memory addresses from the ACPI FPDT table. This can lead to system instability or unexpected reboots on affected hardware, potentially disrupting normal operation.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking the system logs for WARN_ON messages related to invalid physical addresses in ioremap, specifically messages like: '[ 1.226900] ioremap: invalid physical address ...' and kernel oops or stacktrace entries referencing __ioremap_caller.cold. You can use the command 'dmesg | grep -i ioremap' or 'journalctl -k | grep -i ioremap' to search for such warnings in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this issue is fixed, which includes the added code to verify physical addresses before calling acpi_os_map_memory(). Until then, monitoring for the warning messages and avoiding use of affected hardware or firmware updates from the vendor may help reduce risk.