NVD / CVE Program· CNA Linux

CVE-2026-64510: ACPI: NFIT: core: Fix acpi_nfit_init() error cleanup

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Linux Linux 38bf27511ef41bffebd157ec3eba41fc89ba59cd, 3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa, 6ff054cc02a763914773b026cacb429e5fbf64fa; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 38bf27511ef41bffebd157ec3eba41fc89ba59cd, 3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa, 6ff054cc02a763914773b026cacb429e5fbf64fa; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.0 · v3.1—No exploit Fix available

Memory safety

Published: Jul 25, 2026
Updated: Nov 3, 2026
EPSS: 0.1% · 3th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · Linux: 7.0; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.6affected
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before ee82078e776ae31266cc70fdf62ac17c3c6f100aaffected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before 6ff054cc02a763914773b026cacb429e5fbf64faaffected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before b07d22a2d17ad6465c87bd5752bc70e4c16e0ee4affected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before c127dbd832bd4b9aef8a749d9f491b74042f9b47affected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before df7c92216a1583a76cb0cbf2f21cd68870609b05affected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before 3b2628f7682aea8d9ce09ad4b9a3bd144b451eaaaffected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before 7d69235bdc581a4346e9bcd6a8bea37d3e1abd25affected · git
- a61fe6f7902ecaa89d5e6c709490fc4324927134 and later · before 38bf27511ef41bffebd157ec3eba41fc89ba59cdaffected · git
- before 4.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.180-1	6.1.180-1
Debian:12	linux-6.12	before 6.12.100-1~deb12u1	6.12.100-1~deb12u1
Debian:13	linux	before 6.12.100-1	6.12.100-1
Debian:14	linux	before 7.1.4-1	7.1.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-64508Jul 25, 2026 · bpf: Support for hardening against JIT spraying
0Monitor
← EarlierCVE-2026-64509Jul 25, 2026 · rust: block: fix GenDisk cleanup paths
0Monitor
Later →CVE-2026-64511Jul 25, 2026 · ACPI: NFIT: core: Fix possible NULL pointer dereference
0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	38bf27511ef41bffebd157ec3eba41fc89ba59cd	Vendor (CNA)
Linux Linux	3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa	Vendor (CNA)
Linux Linux	6ff054cc02a763914773b026cacb429e5fbf64fa	Vendor (CNA)
Linux Linux	7d69235bdc581a4346e9bcd6a8bea37d3e1abd25	Vendor (CNA)
Linux Linux	b07d22a2d17ad6465c87bd5752bc70e4c16e0ee4	Vendor (CNA)
Linux Linux	c127dbd832bd4b9aef8a749d9f491b74042f9b47	Vendor (CNA)
Linux Linux	df7c92216a1583a76cb0cbf2f21cd68870609b05	Vendor (CNA)
Linux Linux	ee82078e776ae31266cc70fdf62ac17c3c6f100a	Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.0	6.6.145.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.180-1 · Debian:12	Package registry (OSV)
debian:linux-6.12	6.12.100-1~deb12u1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-645230 days apartnet/handshake: Take a long-lived file reference at submit
39Monitor
CVE-2026-645301 days apartnet/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle
39Monitor
CVE-2026-645412 days apartnet/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket
39Monitor
CVE-2026-639796 days apartnet/handshake: hand off the pinned file reference to accept_doit
39Monitor
CVE-2026-6456410 days apartsctp: don't free the ASCONF's own transport in DEL-IP processing
39Monitor
CVE-2026-6811716 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

SSVC exploitation— → noneOct 16, 2026, 5:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/38bf27511ef41bffebd157ec3eba41fc89ba59cd

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records