Linux Kernel up to 6.19.5 media divide by zero

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

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.5. It has been classified as critical. The impacted element is an unknown function of the component media. Performing a manipulation results in divide by zero. This vulnerability is identified as CVE-2026-43182. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.5. It has been classified as critical. This affects an unknown code block of the component media. The manipulation with an unknown input leads to a divide by zero vulnerability. CWE is classifying the issue as CWE-369. The product divides a value by zero. This is going to have an impact on availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: media: ccs: Avoid possible division by zero Calculating maximum M for scaler configuration involves dividing by MIN_X_OUTPUT_SIZE limit register's value. Albeit the value is presumably non-zero, the driver was missing the check it in fact was. Fix this.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-43182 since 05/01/2026. Neither technical details nor an exploit are publicly available.

Upgrading to version 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.16 or 6.19.6 eliminates this vulnerability. Applying the patch b6e0529c300e44153fc6f3b565e28163caf1f031/9aae0f31d37a8facd25e37c0f0709ea08de83802/c9af1818387f5c6f543e2e02c40b3038eae86be8/32a21ed2ad743fe2d12af48e627089b921a032c2/a8ff58cc8c7514c278ba0ea2c787d4bf9eeb355d/8ca7df18e7a58a0e5b0ed9eaaa34e16fc5cb9680/679f0b7b6a409750a25754c8833e268e5fdde742 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Divide by zero
CWE: CWE-369 / CWE-404
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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.202/6.1.165/6.6.128/6.12.75/6.18.16/6.19.6
Patch: b6e0529c300e44153fc6f3b565e28163caf1f031/9aae0f31d37a8facd25e37c0f0709ea08de83802/c9af1818387f5c6f543e2e02c40b3038eae86be8/32a21ed2ad743fe2d12af48e627089b921a032c2/a8ff58cc8c7514c278ba0ea2c787d4bf9eeb355d/8ca7df18e7a58a0e5b0ed9eaaa34e16fc5cb9680/679f0b7b6a409750a25754c8833e268e5fdde742

Timelineinfo

05/01/2026 CVE reserved
05/06/2026 +5 days Advisory disclosed
05/06/2026 +0 days VulDB entry created
05/06/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43182 (🔒)
GCVE (CVE): GCVE-0-2026-43182
GCVE (VulDB): GCVE-100-361401

Entryinfo

Created: 05/06/2026 16:32
Changes: 05/06/2026 16:32 (58)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!