Back to CVE records
Medium 5.5Published May 8, 2026

CVE-2026-43363x86/apic: Disable x2apic on resume if the kernel expects so

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: x86/apic: Disable x2apic on resume if the kernel expects so When resuming from s2ram, firmware may re-enable x2apic mode, which may have been disabled by the kernel during boot either because it doesn't support IRQ remapping or for other reasons. This causes the kernel to continue using the xapic interface, while the hardware is in x2apic mode, which causes hangs. This happens on defconfig + bare metal + s2ram. Fix this in lapic_resume() by disabling x2apic if the kernel expects it to be disabled, i.e. when x2apic_mode = 0. The ACPI v6.6 spec, Section 16.3 [1] says firmware restores either the pre-sleep configuration or initial boot configuration for each CPU, including MSR state: When executing from the power-on reset vector as a result of waking from an S2 or S3 sleep state, the platform firmware performs only the hardware initialization required to restore the system to either the state the platform was in prior to the initial operating system boot, or to the pre-sleep configuration state. In multiprocessor systems, non-boot processors should be placed in the same state as prior to the initial operating system boot. (further ahead) If this is an S2 or S3 wake, then the platform runtime firmware restores minimum context of the system before jumping to the waking vector. This includes: CPU configuration. Platform runtime firmware restores the pre-sleep configuration or initial boot configuration of each CPU (MSR, MTRR, firmware update, SMBase, and so on). Interrupts must be disabled (for IA-32 processors, disabled by CLI instruction). (and other things) So at least as per the spec, re-enablement of x2apic by the firmware is allowed if "x2apic on" is a part of the initial boot configuration. [1] https://uefi.org/specs/ACPI/6.6/16_Waking_and_Sleeping.html#initialization [ bp: Massage. ]

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Analyzed
Record last updated
May 11, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 6e1cb38a2aef7680975e71f23de187859ee8b158 before a6ad6f2e31b524cbb66b2f370bad0cf17d327e6c; 6e1cb38a2aef7680975e71f23de187859ee8b158 builds before 3dd0812a7c764cd8f3b0182441ac22da0a7f3b09; from 6e1cb38a2aef7680975e71f23de187859ee8b158 before 965289b120cc68cca886c75219c68b8c15751d73; from 6e1cb38a2aef7680975e71f23de187859ee8b158 before f591938072115bf08730b8530c67fab189cc6308; 6e1cb38a2aef7680975e71f23de187859ee8b158 builds before 1a85f84214f9d790216547ac6086bf8033cd9e5a; from 6e1cb38a2aef7680975e71f23de187859ee8b158 before 11712c4eb384098db4cb08792e223c818b908c1a; 6e1cb38a2aef7680975e71f23de187859ee8b158 builds before 1d8440c1e7c49715f937416ac90cf260f1f1712c; from 6e1cb38a2aef7680975e71f23de187859ee8b158 before 8cc7dd77a1466f0ec58c03478b2e735a5b289b96
CNA record
linux linux_kernel
linux:linux_kernel
from 2.6.28 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.167; from 6.2 before 6.6.130; from 6.7 before 6.12.78; from 6.13 before 6.18.19; from 6.19 before 6.19.9; 7.0; and 2 more ranges
NVD

References

  • patch
  • patch
  • patch
  • patch
  • patch
  • patch
  • patch
  • patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.