CVE-2026-98248
arm64: percpu: Fix LSE operations on {8,16}-bit types
No known exploitation. EPSS puts it in the 9th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 959bf2fd03b59fc107584c21425f3dc73c49f762, < d69ab4480e49bf925f4781afcc9f284affcb96b6Upgrade to: d69ab4480e49bf925f4781afcc9f284affcb96b6Affected: ≥ 959bf2fd03b59fc107584c21425f3dc73c49f762, < 390742871a723b52de9b92a94c0d1c85a2531e3eUpgrade to: 390742871a723b52de9b92a94c0d1c85a2531e3eAffected: ≥ 959bf2fd03b59fc107584c21425f3dc73c49f762, < 843ace1d0a39e9b1cfcbfb3856a7b0fbdd9cd003Upgrade to: 843ace1d0a39e9b1cfcbfb3856a7b0fbdd9cd003Affected: ≥ 959bf2fd03b59fc107584c21425f3dc73c49f762, < 8cf2093f5372952a9ebc805c418d45df7112cd14Upgrade to: 8cf2093f5372952a9ebc805c418d45df7112cd14Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: arm64: percpu: Fix LSE operations on {8,16}-bit types The assembly for __percpu_##name##_case_##sz() and __percpu_##name##_return_case_##sz() doesn't use the 'sfx' macro argument to form the LSE instruction. Without 'sfx', a W register argument will imply a 32-bit memory location, and consequently {8,16}-bit ops will erroneously read and write 32 bits of memory when the LSE instruction is used. Fix this by appending 'sfx' to 'op_lse' to LSE instruction. It is not necessary (and not valid) to append 'sfx' to 'op_llsc', as 'op_llsc' is a register-register operation which does not access memory (and does not take a size suffix).
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 9th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/d69ab4480e49bf925f4781afcc9f284affcb96b6
- git.kernel.org/stable/c/390742871a723b52de9b92a94c0d1c85a2531e3e
- git.kernel.org/stable/c/843ace1d0a39e9b1cfcbfb3856a7b0fbdd9cd003
And 1 more reference. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI