Linux Kernel up to 6.19.2 fbdev nv3_arb state issue

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.
4.9$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.19.2. Affected is the function nv3_arb of the component fbdev. The manipulation results in state issue. This vulnerability is known as CVE-2026-23266. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.19.2. Affected is the function nv3_arb of the component fbdev. The manipulation with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: fbdev: rivafb: fix divide error in nv3_arb() A userspace program can trigger the RIVA NV3 arbitration code by calling the FBIOPUT_VSCREENINFO ioctl on /dev/fb*. When doing so, the driver recomputes FIFO arbitration parameters in nv3_arb(), using state->mclk_khz (derived from the PRAMDAC MCLK PLL) as a divisor without validating it first. In a normal setup, state->mclk_khz is provided by the real hardware and is non-zero. However, an attacker can construct a malicious or misconfigured device (e.g. a crafted/emulated PCI device) that exposes a bogus PLL configuration, causing state->mclk_khz to become zero. Once nv3_get_param() calls nv3_arb(), the division by state->mclk_khz in the gns calculation causes a divide error and crashes the kernel. Fix this by checking whether state->mclk_khz is zero and bailing out before doing the division. The following log reveals it: rivafb: setting virtual Y resolution to 2184 divide error: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 2187 Comm: syz-executor.0 Not tainted 5.18.0-rc1+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 RIP: 0010:nv3_arb drivers/video/fbdev/riva/riva_hw.c:439 [inline] RIP: 0010:nv3_get_param+0x3ab/0x13b0 drivers/video/fbdev/riva/riva_hw.c:546 Call Trace: nv3CalcArbitration.constprop.0+0x255/0x460 drivers/video/fbdev/riva/riva_hw.c:603 nv3UpdateArbitrationSettings drivers/video/fbdev/riva/riva_hw.c:637 [inline] CalcStateExt+0x447/0x1b90 drivers/video/fbdev/riva/riva_hw.c:1246 riva_load_video_mode+0x8a9/0xea0 drivers/video/fbdev/riva/fbdev.c:779 rivafb_set_par+0xc0/0x5f0 drivers/video/fbdev/riva/fbdev.c:1196 fb_set_var+0x604/0xeb0 drivers/video/fbdev/core/fbmem.c:1033 do_fb_ioctl+0x234/0x670 drivers/video/fbdev/core/fbmem.c:1109 fb_ioctl+0xdd/0x130 drivers/video/fbdev/core/fbmem.c:1188 __x64_sys_ioctl+0x122/0x190 fs/ioctl.c:856

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-23266 since 01/13/2026. The exploitability is told to be difficult. 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/01/2026).

The vulnerability scanner Nessus provides a plugin with the ID 303156 (Linux Distros Unpatched Vulnerability : CVE-2026-23266), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.251, 5.15.201, 6.1.164, 6.6.127, 6.12.74, 6.18.13, 6.19.3 or 7.0-rc1 eliminates this vulnerability. Applying the patch ec5a58f4fd581875593ea92a65485e1906a53c0f/52916878db2b8e3769743a94484729f0844352df/526460a96c5443e2fc0fd231edd1f9c49d2de26b/78daf5984d96edec3b920c72a93bd6821b8710b7/9efa0dc46270a8723c158c64afbcf1dead72b28c/3e4cbd1d46c246dfa684c8e9d8c20ae0b960c50a/73f0391e92d404da68f7484e57c106c5e673dc7e 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 (303156), EUVD (EUVD-2026-12907) and CERT Bund (WID-SEC-2026-0790). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

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

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

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 303156
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-23266

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.251/5.15.201/6.1.164/6.6.127/6.12.74/6.18.13/6.19.3/7.0-rc1
Patch: ec5a58f4fd581875593ea92a65485e1906a53c0f/52916878db2b8e3769743a94484729f0844352df/526460a96c5443e2fc0fd231edd1f9c49d2de26b/78daf5984d96edec3b920c72a93bd6821b8710b7/9efa0dc46270a8723c158c64afbcf1dead72b28c/3e4cbd1d46c246dfa684c8e9d8c20ae0b960c50a/73f0391e92d404da68f7484e57c106c5e673dc7e

Timelineinfo

01/13/2026 CVE reserved
03/18/2026 +64 days Advisory disclosed
03/18/2026 +0 days VulDB entry created
06/01/2026 +74 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23266 (🔒)
GCVE (CVE): GCVE-0-2026-23266
GCVE (VulDB): GCVE-100-351570
EUVD: 🔒
CERT Bund: WID-SEC-2026-0790 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 03/18/2026 19:45
Updated: 06/01/2026 00:36
Changes: 03/18/2026 19:45 (59), 03/18/2026 20:58 (1), 03/19/2026 22:10 (7), 03/23/2026 21:38 (2), 03/24/2026 18:55 (1), 06/01/2026 00:36 (11)
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 know our Splunk app?

Download it now for free!