LoongArch: Add spectre boundry for syscall dispatch table
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.16% (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 07040904ad217545be096d4280ed33c02f6a3750, 0c965d2784fbbd7f8e3b96d875c9cfdf7c00da3d, 108f2cd13577a410c0ad6ea00708596d9d0dfc90; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
Low priority for now. Upgrade to Linux Linux 07040904ad217545be096d4280ed33c02f6a3750, 0c965d2784fbbd7f8e3b96d875c9cfdf7c00da3d, 108f2cd13577a410c0ad6ea00708596d9d0dfc90; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 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: LoongArch: Add spectre boundry for syscall dispatch table The LoongArch syscall number is directly controlled by userspace, but does not have a array_index_nospec() boundry to prevent access past the syscall function pointer tables.
- Published
- May 27, 2026
- Updated
- Jun 19, 2026
- EPSS
- 0.1% · 5th 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 kernel5.19 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.86
- linux linux kernel6.13 and later · before 6.18.27
- linux linux kernel6.19 and later · before 7.0.4
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
- 5.19affected
- be769645a2aef577f07afdcb4de8fad20b6d57c0 and later · before c8a8e863928424046b8fd328f02c359baa0a0c3faffected · git
- be769645a2aef577f07afdcb4de8fad20b6d57c0 and later · before 108f2cd13577a410c0ad6ea00708596d9d0dfc90affected · git
- be769645a2aef577f07afdcb4de8fad20b6d57c0 and later · before 07040904ad217545be096d4280ed33c02f6a3750affected · git
- be769645a2aef577f07afdcb4de8fad20b6d57c0 and later · before 85cbf7fb568af5358aae61925c4e66b8f5e1439daffected · git
- be769645a2aef577f07afdcb4de8fad20b6d57c0 and later · before bc84a109c2082dd0c4b38e8d923c046b41977533affected · git
- be769645a2aef577f07afdcb4de8fad20b6d57c0 and later · before 0c965d2784fbbd7f8e3b96d875c9cfdf7c00da3daffected · git
- before 5.19not affected · semver
- 6.1.176 and later · up to and including 6.1.*not affected · semver
- 6.6.140 and later · up to and including 6.6.*not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.86-1 | 6.12.86-1 |
| Debian:14 | linux | before 7.0.4-1 | 7.0.4-1 |
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
Published before and after this one in the same product
- ← EarlierCVE-2026-45989May 27, 2026 · of: unittest: fix use-after-free in testdrv_probe()31Monitor
- ← EarlierCVE-2026-45990May 27, 2026 · slub: fix data loss and overflow in krealloc()22Monitor
- Later →CVE-2026-45994May 27, 2026 · ibmasm: fix OOB reads in command_file_write due to missing size checks28Monitor
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 | 07040904ad217545be096d4280ed33c02f6a3750 | Vendor (CNA) |
| Linux Linux | 0c965d2784fbbd7f8e3b96d875c9cfdf7c00da3d | Vendor (CNA) |
| Linux Linux | 108f2cd13577a410c0ad6ea00708596d9d0dfc90 | Vendor (CNA) |
| Linux Linux | 85cbf7fb568af5358aae61925c4e66b8f5e1439d | Vendor (CNA) |
| Linux Linux | bc84a109c2082dd0c4b38e8d923c046b41977533 | Vendor (CNA) |
| Linux Linux | c8a8e863928424046b8fd328f02c359baa0a0c3f | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.86-1 · Debian:13 | Package registry (OSV) |
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).
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 (5 more)Show less
- git.kernel.org/stable/c/0c965d2784fbbd7f8e3b96d875c9cfdf7c00da3d
- git.kernel.org/stable/c/108f2cd13577a410c0ad6ea00708596d9d0dfc90
- git.kernel.org/stable/c/85cbf7fb568af5358aae61925c4e66b8f5e1439d
- git.kernel.org/stable/c/bc84a109c2082dd0c4b38e8d923c046b41977533
- git.kernel.org/stable/c/c8a8e863928424046b8fd328f02c359baa0a0c3f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.