Answer in brief
CVE-2025-22044 records a Unknown severity vulnerability in acpi: nfit: fix narrowing conversion in acpi_nfit_ctl. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-22044 records a Unknown severity vulnerability in acpi: nfit: fix narrowing conversion in acpi_nfit_ctl. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <4b65cff06a004ac54f6ea8886060f0d07b1ca055 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <92ba06aef65522483784dcbd6697629ddbd4c4f9 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <bae5b55e0f327102e78f6a66fb127275e9bc91b6 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <c90402d2a226ff7afbe1d0650bee8ecc15a91049 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <e71a57c5aaa389d4c3c82f920761262efdd18d38 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <73851cfceb00cc77d7a0851bc10f2263394c3e87 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <85f11291658ab907c4294319c8102450cc75bb96 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <2ff0e408db36c21ed3fa5e3c1e0e687c82cf132f | 4b65cff06a004ac54f6ea8886060f0d07b1ca055, 92ba06aef65522483784dcbd6697629ddbd4c4f9, bae5b55e0f327102e78f6a66fb127275e9bc91b6, c90402d2a226ff7afbe1d0650bee8ecc15a91049, e71a57c5aaa389d4c3c82f920761262efdd18d38, 73851cfceb00cc77d7a0851bc10f2263394c3e87, 85f11291658ab907c4294319c8102450cc75bb96, 2ff0e408db36c21ed3fa5e3c1e0e687c82cf132f |
| Linux/Linuxgeneric | 5.9 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: acpi: nfit: fix narrowing conversion in acpi_nfit_ctl Syzkaller has reported a warning in to_nfit_bus_uuid(): "only secondary bus families can be translated". This warning is emited if the argument is equal to NVDIMM_BUS_FAMILY_NFIT == 0. Function acpi_nfit_ctl() first verifies that a user-provided value call_pkg->nd_family of type u64 is not equal to 0. Then the value is converted to int, and only after that is compared to NVDIMM_BUS_FAMILY_MAX. This can lead to passing an invalid argument to acpi_nfit_ctl(), if call_pkg->nd_family is non-zero, while the lower 32 bits are zero. Furthermore, it is best to return EINVAL immediately upon seeing the invalid user input. The WARNING is insufficient to prevent further undefined behavior based on other invalid user input. All checks of the input value should be applied to the original variable call_pkg->nd_family. [iweiny: update commit message]
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <4b65cff06a004ac54f6ea8886060f0d07b1ca055 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <92ba06aef65522483784dcbd6697629ddbd4c4f9 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <bae5b55e0f327102e78f6a66fb127275e9bc91b6 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <c90402d2a226ff7afbe1d0650bee8ecc15a91049 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <e71a57c5aaa389d4c3c82f920761262efdd18d38 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <73851cfceb00cc77d7a0851bc10f2263394c3e87 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <85f11291658ab907c4294319c8102450cc75bb96 || >=6450ddbd5d8e83ea9927c7f9076a21f829699e0f <2ff0e408db36c21ed3fa5e3c1e0e687c82cf132f | 4b65cff06a004ac54f6ea8886060f0d07b1ca055, 92ba06aef65522483784dcbd6697629ddbd4c4f9, bae5b55e0f327102e78f6a66fb127275e9bc91b6, c90402d2a226ff7afbe1d0650bee8ecc15a91049, e71a57c5aaa389d4c3c82f920761262efdd18d38, 73851cfceb00cc77d7a0851bc10f2263394c3e87, 85f11291658ab907c4294319c8102450cc75bb96, 2ff0e408db36c21ed3fa5e3c1e0e687c82cf132f |
| Linux/Linuxgeneric | 5.9 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: acpi: nfit: fix narrowing conversion in acpi_nfit_ctl Syzkaller has reported a warning in to_nfit_bus_uuid(): "only secondary bus families can be translated". This warning is emited if the argument is equal to NVDIMM_BUS_FAMILY_NFIT == 0. Function acpi_nfit_ctl() first verifies that a user-provided value call_pkg->nd_family of type u64 is not equal to 0. Then the value is converted to int, and only after that is compared to NVDIMM_BUS_FAMILY_MAX. This can lead to passing an invalid argument to acpi_nfit_ctl(), if call_pkg->nd_family is non-zero, while the lower 32 bits are zero. Furthermore, it is best to return EINVAL immediately upon seeing the invalid user input. The WARNING is insufficient to prevent further undefined behavior based on other invalid user input. All checks of the input value should be applied to the original variable call_pkg->nd_family. [iweiny: update commit message]
Quoted source text, attributed separately from HOL analysis.