CVE-2026-23354: x86/fred: Correct speculative safety in fred_extint()
Noroxi assessment
Priority: Monitor (action score 31/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.13% (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 3bc5887b0a2b06d2d9c22f1f4f8500490b3ae643, 92caa5274b99cb6729177232a029ce0dfa6c5f7b, aa280a08e7d8fae58557acc345b36b3dc329d595.
Low priority for now. Upgrade to Linux Linux 3bc5887b0a2b06d2d9c22f1f4f8500490b3ae643, 92caa5274b99cb6729177232a029ce0dfa6c5f7b, aa280a08e7d8fae58557acc345b36b3dc329d595 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/fred: Correct speculative safety in fred_extint() array_index_nospec() is no use if the result gets spilled to the stack, as it makes the believed safe-under-speculation value subject to memory predictions. For all practical purposes, this means array_index_nospec() must be used in the expression that accesses the array. As the code currently stands, it's the wrong side of irqentry_enter(), and 'index' is put into %ebp across the function call. Remove the index variable and reposition array_index_nospec(), so it's calculated immediately before the array access.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-129
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 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.
Is your version affected? Check itNoroxi 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 |
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
- 6.9affected
- 14619d912b658ecd9573fb88400d3830a29cadcb and later · before 3bc5887b0a2b06d2d9c22f1f4f8500490b3ae643affected · git
- 14619d912b658ecd9573fb88400d3830a29cadcb and later · before e58f1a9b0677de24dcfee0b21393446ec92ff120affected · git
- 14619d912b658ecd9573fb88400d3830a29cadcb and later · before 92caa5274b99cb6729177232a029ce0dfa6c5f7baffected · git
- 14619d912b658ecd9573fb88400d3830a29cadcb and later · before aa280a08e7d8fae58557acc345b36b3dc329d595affected · git
- before 6.9not affected · semver
- 6.12.77 and later · up to and including 6.12.*not affected · semver
- 6.18.17 and later · up to and including 6.18.*not affected · semver
- 6.19.7 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.9.1 and later · before 6.12.77
- linux linux kernel6.13 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel6.9
- linux linux kernel7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.8-1 | 6.19.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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
Published before and after this one in the same product
- ← EarlierCVE-2026-23349Mar 25, 2026 · HID: pidff: Fix condition effect bit clearing22Monitor
- ← EarlierCVE-2026-23350Mar 25, 2026 · drm/xe/queue: Call fini on exec queue creation fail31Monitor
- Later →CVE-2026-23360Mar 25, 2026 · nvme: fix admin queue leak on controller reset22Monitor
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 | 3bc5887b0a2b06d2d9c22f1f4f8500490b3ae643 | Vendor (CNA) |
| Linux Linux | 92caa5274b99cb6729177232a029ce0dfa6c5f7b | Vendor (CNA) |
| Linux Linux | aa280a08e7d8fae58557acc345b36b3dc329d595 | Vendor (CNA) |
| Linux Linux | e58f1a9b0677de24dcfee0b21393446ec92ff120 | Vendor (CNA) |
| debian:linux | 6.12.85-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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-64018116 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access37Monitor
- CVE-2026-232467 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration35Monitor
- CVE-2026-4311042 days apartwifi: brcmfmac: validate bsscfg indices in IF events35Monitor
- CVE-2026-4317242 days apartwifi: iwlwifi: fix 22000 series SMEM parsing35Monitor
- CVE-2026-234479 days apartnet: usb: cdc_ncm: add ndpoffset to NDP32 nframes bounds check31Monitor
- CVE-2026-234489 days apartnet: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check31Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.