What is CVE-2026-43031?

CVE-2026-43031 is a High severity Linux kernel vulnerability with a CVSS score of 7.5 out of 10, affecting Linux kernel versions from 6.15 onward and patched in 6.18.22, 6.19.12 and 7.0. CVE-2026-43031 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-43031?

CVE-2026-43031 has a CVSS score of 7.5 out of 10, rated High severity. The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-43031?

Yes, CVE-2026-43031 has been patched. Fixed versions include 6.18.22, 6.19.12 and 7.0. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-43031 actively exploited?

CVE-2026-43031 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-43031

High

In the Linux kernel, the following vulnerability has been resolved: net: xilinx: axienet: Fix BQL accounting for multi-BD TX packets When a TX packet spans multiple buffer descriptors (scatter-gather), axienet_free_tx_chain sums the per-BD actual length from descriptor status into a caller-provided accumulator. That sum is reset on each NAPI poll. If the BDs for a single packet complete across different polls, the earlier bytes are lost and never credited to BQL. This causes BQL to think bytes are permanently in-flight, eventually stalling the TX queue. The SKB pointer is stored only on the last BD of a packet. When that BD completes, use skb->len for the byte count instead of summing per-BD status lengths. This matches netdev_sent_queue(), which debits skb->len, and naturally survives across polls because no partial packet contributes to the accumulator.

Package Linux Kernel

Published 2026-05-01

Last modified 2026-05-08

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.5

out of 10

High

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 6.15 and later are affected. Fixed in 6.18.22, 6.19.12, 7.0 and their respective stable series.

Affected from

≥ 6.15

Fixed in

✓ 6.18.22 6.18.x ✓ 6.19.12 6.19.x ✓ 7.0

References

The following references provide additional information about CVE-2026-43031 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Kernel patch commit
https://git.kernel.org/stable/c/2a0323a913109b52bfc9f5ea7b92a1b249e07d3e
Patch
Kernel patch commit
https://git.kernel.org/stable/c/3c3a6b9020c01fde7b22e8550105de0b59904f61
Patch
Kernel patch commit
https://git.kernel.org/stable/c/d1978d03e86785872871bff9c2623174b10740de
Patch

Details

CVE ID CVE-2026-43031

Severity High

CVSS score 7.5 / 10

CVSS version 3.1

Published 2026-05-01

Modified 2026-05-08

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-43031?

CVE-2026-43031 is a High severity Linux kernel vulnerability with a CVSS score of 7.5 out of 10 . It affects Linux kernel versions from 6.15 onward and has been patched in 6.18.22, 6.19.12 and 7.0. CVE-2026-43031 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-43031?

CVE-2026-43031 has a CVSS score of 7.5 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-43031?

Yes — CVE-2026-43031 has been patched. Fixed versions include 6.18.22, 6.19.12 and 7.0. If you are running Linux kernel 6.15 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-43031 actively exploited?

No — CVE-2026-43031 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.