Linux Kernel up to 6.12.76/6.18.16/6.19.6/7.0-rc1 fred_extint stack-based overflow

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability labeled as critical has been found in Linux Kernel up to 6.12.76/6.18.16/6.19.6/7.0-rc1. Affected by this issue is the function fred_extint. Such manipulation leads to stack-based overflow. This vulnerability is referenced as CVE-2026-23354. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.12.76/6.18.16/6.19.6/7.0-rc1. Affected by this issue is the function fred_extint. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-23354 since 01/13/2026. The exploitation is known to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 06/20/2026).

The vulnerability scanner Nessus provides a plugin with the ID 318102 (openSUSE 16 Security Update : kernel (openSUSE-SU-2026:20826-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.77, 6.18.17, 6.19.7 or 7.0-rc2 eliminates this vulnerability. Applying the patch 3bc5887b0a2b06d2d9c22f1f4f8500490b3ae643/e58f1a9b0677de24dcfee0b21393446ec92ff120/92caa5274b99cb6729177232a029ce0dfa6c5f7b/aa280a08e7d8fae58557acc345b36b3dc329d595 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (318102) and CERT Bund (WID-SEC-2026-0861). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Google Cloud Platform
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 318102
Nessus Name: openSUSE 16 Security Update : kernel (openSUSE-SU-2026:20826-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.77/6.18.17/6.19.7/7.0-rc2
Patch: 3bc5887b0a2b06d2d9c22f1f4f8500490b3ae643/e58f1a9b0677de24dcfee0b21393446ec92ff120/92caa5274b99cb6729177232a029ce0dfa6c5f7b/aa280a08e7d8fae58557acc345b36b3dc329d595

Timelineinfo

01/13/2026 CVE reserved
03/25/2026 +71 days Advisory disclosed
03/25/2026 +0 days VulDB entry created
06/20/2026 +87 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23354 (🔒)
GCVE (CVE): GCVE-0-2026-23354
GCVE (VulDB): GCVE-100-353090
CERT Bund: WID-SEC-2026-0861 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 03/25/2026 13:29
Updated: 06/20/2026 13:41
Changes: 03/25/2026 13:29 (58), 03/30/2026 10:38 (1), 06/02/2026 04:51 (2), 06/20/2026 13:41 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!