How to Fix CVE-2026-23443: Linux (Bundle Sibling)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | Not verified, see advisory |
|---|---|
| Actively exploited? | No |
| Affected | Linux (06724a60cfa9767ea90b0f5d3dfb5cdd251b64f5 < 68408e8f9e366ad9850a66ac65cb569f13bf6cd4, ad86ac604f8391c0212a91412d4f764c7a85f254 < 2e369ba9eb7b8a06e9cc35a3e7fe73e59272f8c2); Linux (5.15.202 < 5.15.203, 6.1.165 < 6.1.167) |
| Fixed in | Same patched build as CVE-2026-23401 |
| Type (CWE) | Not verified |
CVE-2026-23443 is a sibling vulnerability in the same Linux Linux advisory bundle as CVE-2026-23401. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-23443 matches the primary write-up.
What is different about CVE-2026-23443?
In the Linux kernel, the following vulnerability has been resolved:
ACPI: processor: Fix previous acpi_processor_errata_piix4() fix
After commi f132e089fe89 ("ACPI: processor: Fix NULL-pointer dereference
in acpi_processor_errata_piix4()"), device pointers may be dereferenced
after dropping references to the device objects pointed to by them,
which may cause a use-after-free to occur. And debug messages about enabling the errata may be printed
if the errata flags corresponding to them...
Impact is consistent with the bundle: use-after-free that can lead to heap corruption and code execution. The patched build closes every code path in the advisory in one update.
How to fix CVE-2026-23443
Apply the patched build per the primary write-up: How to Fix CVE-2026-23401.
For a quick check, confirm the running version of Linux:
# Confirm the installed version via your package manager
dpkg -l | grep -i linux # Debian/Ubuntu
rpm -qa | grep -i linux # RHEL/CentOS/Rocky
Frequently asked questions
Is CVE-2026-23443 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-23443?
CVSS has not been published in the data sources used for this page. Refer to the vendor advisory and NVD for any score updates.
Do I have to take Linux offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-23443 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://git.kernel.org/stable/c/68408e8f9e366ad9850a66ac65cb569f13bf6cd4
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-23443
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-23401
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Linux Linux advisory bundle. Full procedure at how-to-fix-cve-2026-23401.*