LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22044: acpi: nfit: fix narrowing conversion in acpi_nfit_ctl

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]

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel’s ACPI NFIT/NVDIMM control path can mishandle a specially formed local input because a 64-bit value is narrowed before validation finishes. This may cause undefined kernel behavior, potentially exposing sensitive data or disrupting the system. The supplied CVSS score is 7.1, but exploitation requires local, low-privileged access.

Executive priority

Treat this as a high-priority kernel maintenance issue for exposed multi-user or persistent-memory systems, but not as an internet-wide emergency. Schedule prompt vendor-kernel updates, focusing first on hosts where untrusted local users or workloads can access the affected interface.

Technical view

acpi_nfit_ctl() checks the original u64 nd_family for zero, then narrows it to int before later validation. A nonzero value whose lower 32 bits are zero can consequently become NVDIMM_BUS_FAMILY_NFIT and reach an invalid path. The correction validates the original u64 and rejects invalid input with EINVAL before conversion or further processing.

Likely exposure

Exposure is most likely on affected Linux systems where a local user can reach the ACPI NFIT/NVDIMM control interface. Internet reachability alone does not expose this local attack path. The supplied affected-version data is not a reliable clean boundary, so installed distribution kernels should be checked against vendor advisories and referenced stable fixes.

Exploitation context

The CVSS vector indicates local access, low privileges, no user interaction, and potential high confidentiality and availability impact. The issue was found by Syzkaller. The bundle marks it absent from KEV and provides no evidence of active exploitation or a public weaponized exploit.

Researcher notes

The security boundary failure is a time-of-validation/type-conversion mismatch rather than a direct zero check omission. The sources describe warnings and possible further undefined behavior but do not establish a specific disclosure or crash primitive. Version metadata in the supplied bundle appears ambiguous; confirm ancestry or vendor backports instead of relying only on version strings.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable upstream or stable fix.
  • Use Debian’s referenced security updates where those advisories match the deployed release.
  • Prioritize shared or multi-user systems exposing NFIT/NVDIMM functionality.
  • Check current distribution guidance if an updated kernel is not yet available.

Validation and detection

  • Inventory kernel versions and identify systems using ACPI NFIT or NVDIMM functionality.
  • Compare distribution package revisions with vendor advisories and the referenced stable commits.
  • Confirm the installed kernel includes validation of the original u64 nd_family value.
  • After updating, verify systems boot normally and relevant persistent-memory functions remain operational.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22044 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-22044Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0f, 6450ddbd5d8e83ea9927c7f9076a21f829699e0funaffected
LinuxLinux5.9, 0, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.