CVE-2026-64510ACPI: NFIT: core: Fix acpi_nfit_init() error cleanup
- 7.0HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 96% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.
Affected products
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < ee82078e776ae31266cc70fdf62ac17c3c6f100a
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < 6ff054cc02a763914773b026cacb429e5fbf64fa
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < b07d22a2d17ad6465c87bd5752bc70e4c16e0ee4
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < c127dbd832bd4b9aef8a749d9f491b74042f9b47
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < df7c92216a1583a76cb0cbf2f21cd68870609b05
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < 3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < 7d69235bdc581a4346e9bcd6a8bea37d3e1abd25
- affected a61fe6f7902ecaa89d5e6c709490fc4324927134 – < 38bf27511ef41bffebd157ec3eba41fc89ba59cd
- affected 4.6
- unaffected < 4.6
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/ee82078e776ae31266cc70fdf62ac17c3c6f100a (opens in a new tab)
- https://git.kernel.org/stable/c/6ff054cc02a763914773b026cacb429e5fbf64fa (opens in a new tab)
- https://git.kernel.org/stable/c/b07d22a2d17ad6465c87bd5752bc70e4c16e0ee4 (opens in a new tab)
- https://git.kernel.org/stable/c/c127dbd832bd4b9aef8a749d9f491b74042f9b47 (opens in a new tab)
- https://git.kernel.org/stable/c/df7c92216a1583a76cb0cbf2f21cd68870609b05 (opens in a new tab)
- https://git.kernel.org/stable/c/3b2628f7682aea8d9ce09ad4b9a3bd144b451eaa (opens in a new tab)
- https://git.kernel.org/stable/c/7d69235bdc581a4346e9bcd6a8bea37d3e1abd25 (opens in a new tab)
- https://git.kernel.org/stable/c/38bf27511ef41bffebd157ec3eba41fc89ba59cd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-48854 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64510)Record last updated .