Linux Kernel up to 6.19.8 Igbvf Driver _tx_map off-by-one

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

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.8. It has been classified as critical. Impacted is the function _tx_map of the component Igbvf Driver. The manipulation leads to off-by-one. This vulnerability is listed as CVE-2026-43445. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.8. It has been rated as critical. This issue affects the function _tx_map of the component Igbvf Driver. The manipulation with an unknown input leads to a off-by-one vulnerability. Using CWE to declare the problem leads to CWE-193. A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: e1000/e1000e: Fix leak in DMA error cleanup If an error is encountered while mapping TX buffers, the driver should unmap any buffers already mapped for that skb. Because count is incremented after a successful mapping, it will always match the correct number of unmappings needed when dma_error is reached. Decrementing count before the while loop in dma_error causes an off-by-one error. If any mapping was successful before an unsuccessful mapping, exactly one DMA mapping would leak. In these commits, a faulty while condition caused an infinite loop in dma_error: Commit 03b1320dfcee ("e1000e: remove use of skb_dma_map from e1000e driver") Commit 602c0554d7b0 ("e1000: remove use of skb_dma_map from e1000 driver") Commit c1fa347f20f1 ("e1000/e1000e/igb/igbvf/ixgb/ixgbe: Fix tests of unsigned in *_tx_map()") fixed the infinite loop, but introduced the off-by-one error. This issue may still exist in the igbvf driver, but I did not address it in this patch.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-43445 since 05/01/2026. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/10/2026).

The vulnerability scanner Nessus provides a plugin with the ID 326222 (EulerOS 2.0 SP12 : kernel (EulerOS-SA-2026-2535)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19 or 6.19.9 eliminates this vulnerability. Applying the patch 7eaeb778bfaa3b2a804f89321c234d59c74569db/0606c24a745bafd1be5d66c48361638cd9cad74b/519051c711dfd239ef6e4b28878efee400a035f9/0a1fc25deabab4efce64610e3c449485c4fa8f5f/fa5ba9867a55e640df0dc79bf0199770fb043f03/30e87ade8d678c25a8546cf38c0b498fa5cb27d3/10b5e65959e955a1c8894e0a5413944b5a70204a/e94eaef11142b01f77bf8ba4d0b59720b7858109 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 vulnerability database at Tenable (326222). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Off-by-one
CWE: CWE-193 / CWE-189
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: 326222
Nessus Name: EulerOS 2.0 SP12 : kernel (EulerOS-SA-2026-2535)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.253/5.15.203/6.1.167/6.6.130/6.12.78/6.18.19/6.19.9
Patch: 7eaeb778bfaa3b2a804f89321c234d59c74569db/0606c24a745bafd1be5d66c48361638cd9cad74b/519051c711dfd239ef6e4b28878efee400a035f9/0a1fc25deabab4efce64610e3c449485c4fa8f5f/fa5ba9867a55e640df0dc79bf0199770fb043f03/30e87ade8d678c25a8546cf38c0b498fa5cb27d3/10b5e65959e955a1c8894e0a5413944b5a70204a/e94eaef11142b01f77bf8ba4d0b59720b7858109

Timelineinfo

05/01/2026 CVE reserved
05/08/2026 +7 days Advisory disclosed
05/08/2026 +0 days VulDB entry created
07/10/2026 +63 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43445 (🔒)
GCVE (CVE): GCVE-0-2026-43445
GCVE (VulDB): GCVE-100-362213

Entryinfo

Created: 05/08/2026 18:24
Updated: 07/10/2026 13:19
Changes: 05/08/2026 18:24 (59), 05/22/2026 03:43 (10), 07/10/2026 13:19 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!