x86/apic: Disable x2apic on resume if the kernel expects so
Noroxi assessment
Priority: Monitor (action score 22/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 11712c4eb384098db4cb08792e223c818b908c1a, 1a85f84214f9d790216547ac6086bf8033cd9e5a, 1d8440c1e7c49715f937416ac90cf260f1f1712c.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 11712c4eb384098db4cb08792e223c818b908c1a, 1a85f84214f9d790216547ac6086bf8033cd9e5a, 1d8440c1e7c49715f937416ac90cf260f1f1712c 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: 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. ]
- Published
- May 8, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.28 and later · before 5.10.253
- linux linux kernel5.11 and later · before 5.15.203
- linux linux kernel5.16 and later · before 6.1.167
- linux linux kernel6.2 and later · before 6.6.130
- linux linux kernel6.7 and later · before 6.12.78
- linux linux kernel6.13 and later · before 6.18.19
- linux linux kernel6.19 and later · before 6.19.9
- linux linux kernel7.0
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
- 2.6.28affected
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before a6ad6f2e31b524cbb66b2f370bad0cf17d327e6caffected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before 3dd0812a7c764cd8f3b0182441ac22da0a7f3b09affected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before 965289b120cc68cca886c75219c68b8c15751d73affected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before f591938072115bf08730b8530c67fab189cc6308affected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before 1a85f84214f9d790216547ac6086bf8033cd9e5aaffected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before 11712c4eb384098db4cb08792e223c818b908c1aaffected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before 1d8440c1e7c49715f937416ac90cf260f1f1712caffected · git
- 6e1cb38a2aef7680975e71f23de187859ee8b158 and later · before 8cc7dd77a1466f0ec58c03478b2e735a5b289b96affected · git
- before 2.6.28not 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.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.10-1 | 6.19.10-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.38.1.160000.2.22 | 6.12.0-160000.38.1.160000.2.22 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.328.1 | 4.12.14-122.328.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_87 | before 1-8.5.1 | 1-8.5.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-source | before 4.12.14-122.328.1 | 4.12.14-122.328.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-syms | before 4.12.14-122.328.1 | 4.12.14-122.328.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
+8
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 11712c4eb384098db4cb08792e223c818b908c1a | Vendor (CNA) |
| Linux Linux | 1a85f84214f9d790216547ac6086bf8033cd9e5a | Vendor (CNA) |
| Linux Linux | 1d8440c1e7c49715f937416ac90cf260f1f1712c | Vendor (CNA) |
| Linux Linux | 3dd0812a7c764cd8f3b0182441ac22da0a7f3b09 | Vendor (CNA) |
| Linux Linux | 8cc7dd77a1466f0ec58c03478b2e735a5b289b96 | Vendor (CNA) |
| Linux Linux | 965289b120cc68cca886c75219c68b8c15751d73 | Vendor (CNA) |
| Linux Linux | a6ad6f2e31b524cbb66b2f370bad0cf17d327e6c | Vendor (CNA) |
| Linux Linux | f591938072115bf08730b8530c67fab189cc6308 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.38.1.160000.2.22 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.38.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.328.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.38.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.38.1.160000.2.23 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.38.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
+7
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.
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 researchersFinders, 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.
No nightly-computed relations.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0213 · May 12, 2026(Linux Kernel Güvenlik Bildirimi)
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1a85f84214f9d790216547ac6086bf8033cd9e5a
- git.kernel.org/stable/c/1d8440c1e7c49715f937416ac90cf260f1f1712c
- git.kernel.org/stable/c/3dd0812a7c764cd8f3b0182441ac22da0a7f3b09
- git.kernel.org/stable/c/8cc7dd77a1466f0ec58c03478b2e735a5b289b96
- git.kernel.org/stable/c/965289b120cc68cca886c75219c68b8c15751d73
- git.kernel.org/stable/c/a6ad6f2e31b524cbb66b2f370bad0cf17d327e6c
- git.kernel.org/stable/c/f591938072115bf08730b8530c67fab189cc6308
Vendor advisories and official records. Exploit/PoC links are deliberately left out.