Linux Kernel up to 7.1.3 Nfit Core acpi_nfit_init use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k3.88-

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.3. It has been declared as very critical. The affected element is the function acpi_nfit_init of the component Nfit Core. Such manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2026-64510. Local access is required to approach this attack. No exploit exists.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.1.3. Affected by this issue is the function acpi_nfit_init of the component Nfit Core. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: ACPI: NFIT: core: Fix acpi_nfit_init() error cleanup If acpi_nfit_init() fails after adding the acpi_desc object to the acpi_descs list, that object is never removed from that list because the acpi_nfit_shutdown() devm action is not added for the NFIT device in that case. Next, the acpi_nfit_init() failure causes acpi_nfit_probe() to fail, the acpi_desc object is freed, and a dangling pointer is left behind in the acpi_descs. Any subsequent ACPI Machine Check Exception will trigger nfit_handle_mce() which iterates over acpi_descs and so a use-after-free will occur. Moreover, if acpi_nfit_probe() returns 0 after installing a notify handler for the NFIT device and without allocating the acpi_desc object and setting the NFIT device's driver data pointer, the acpi_desc object will be allocated by acpi_nfit_update_notify() and acpi_nfit_init() will be called to initialize it. Regardless of whether or not acpi_nfit_init() fails in that case, the acpi_nfit_shutdown() devm action is not added for the NFIT device and acpi_desc is never removed from the acpi_descs list. If the acpi_desc object is freed subsequently on driver removal, any subsequent ACPI MCE will lead to a use-after-free like in the previous case. To address the first issue mentioned above, make acpi_nfit_probe() call acpi_nfit_shutdown() directly on acpi_nfit_init() failures and to address the other one, add a remove callback to the driver and make it call acpi_nfit_shutdown(). Also, since it is now possible to pass NULL to acpi_nfit_shutdown() or the acpi_desc object passed to it may not have been initialized, add checks against NULL for acpi_desc and its nvdimm_bus field to that function and make acpi_nfit_unregister() clear the latter after unregistering the NVDIMM bus.

The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-64510 since 07/19/2026. The exploitation is known to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/26/2026).

The vulnerability scanner Nessus provides a plugin with the ID 329994 (Linux Distros Unpatched Vulnerability : CVE-2026-64510), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.4 or 7.2-rc1 eliminates this vulnerability. Applying the patch ee82078e776ae31266cc70fdf62ac17c3c6f100a/6ff054cc02a763914773b026cacb429e5fbf64fa/b07d22a2d17ad6465c87bd5752bc70e4c16e0ee4/c127dbd832bd4b9aef8a749d9f491b74042f9b47/df7c92216a1583a76cb0cbf2f21cd68870609b05/3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa/7d69235bdc581a4346e9bcd6a8bea37d3e1abd25/38bf27511ef41bffebd157ec3eba41fc89ba59cd is able to eliminate this problem.

The vulnerability is also documented in the databases at Tenable (329994) and EUVD (EUVD-2026-48854). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 329994
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-64510

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.4/7.2-rc1
Patch: ee82078e776ae31266cc70fdf62ac17c3c6f100a/6ff054cc02a763914773b026cacb429e5fbf64fa/b07d22a2d17ad6465c87bd5752bc70e4c16e0ee4/c127dbd832bd4b9aef8a749d9f491b74042f9b47/df7c92216a1583a76cb0cbf2f21cd68870609b05/3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa/7d69235bdc581a4346e9bcd6a8bea37d3e1abd25/38bf27511ef41bffebd157ec3eba41fc89ba59cd

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/26/2026 +1 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64510 (🔒)
GCVE (CVE): GCVE-0-2026-64510
GCVE (VulDB): GCVE-100-383312
EUVD: 🔒

Entryinfo

Created: 07/25/2026 19:27
Updated: 07/26/2026 06:34
Changes: 07/25/2026 19:27 (59), 07/26/2026 02:04 (1), 07/26/2026 06:34 (2)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!