CVE & CISA-KEV Catalog

CVE-2026-46031

MEDIUM
5.5
CVSS v3
NVD

Description

In the Linux kernel, the following vulnerability has been resolved: net: ks8851: Reinstate disabling of BHs around IRQ handler If the driver executes ks8851_irq() AND a TX packet has been sent, then the driver enables TX queue via netif_wake_queue() which schedules TX softirq to queue packets for this device. If CONFIG_PREEMPT_RT=y is set AND a packet has also been received by the MAC, then ks8851_rx_pkts() calls netdev_alloc_skb_ip_align() to allocate SKBs for the received packets. If netdev_alloc_skb_ip_align() is called with BH enabled, then local_bh_enable() at the end of netdev_alloc_skb_ip_align() will trigger the pending softirq processing, which may ultimately call the .xmit callback ks8851_start_xmit_par(). The ks8851_start_xmit_par() will try to lock struct ks8851_net_par .lock spinlock, which is already locked by ks8851_irq() from which ks8851_start_xmit_par() was called. This leads to a deadlock, which is reported by the kernel, including a trace listed below. If CONFIG_PREEMPT_RT is not set, then since commit 0913ec336a6c0 ("net: ks8851: Fix deadlock with the SPI chip variant") the deadlock can also be triggered without received packet in the RX FIFO. The pending softirqs will be processed on return from spin_unlock_bh(&ks->statelock) in ks8851_irq(), which triggers the deadlock as well. Fix the problem by disabling BH around critical sections, including the IRQ handler, thus preventing the net_tx_action() softirq from triggering during these critical sections. The net_tx_action() softirq is triggered once BH are re-enabled and at the end of the IRQ handler, once all the other IRQ handler actions have been completed. __schedule from schedule_rtlock+0x1c/0x34 schedule_rtlock from rtlock_slowlock_locked+0x548/0x904 rtlock_slowlock_locked from rt_spin_lock+0x60/0x9c rt_spin_lock from ks8851_start_xmit_par+0x74/0x1a8 ks8851_start_xmit_par from netdev_start_xmit+0x20/0x44 netdev_start_xmit from dev_hard_start_xmit+0xd0/0x188 dev_hard_start_xmit from sch_direct_xmit+0xb8/0x25c sch_direct_xmit from __qdisc_run+0x1f8/0x4ec __qdisc_run from qdisc_run+0x1c/0x28 qdisc_run from net_tx_action+0x1f0/0x268 net_tx_action from handle_softirqs+0x1a4/0x270 handle_softirqs from __local_bh_enable_ip+0xcc/0xe0 __local_bh_enable_ip from __alloc_skb+0xd8/0x128 __alloc_skb from __netdev_alloc_skb+0x3c/0x19c __netdev_alloc_skb from ks8851_irq+0x388/0x4d4 ks8851_irq from irq_thread_fn+0x24/0x64 irq_thread_fn from irq_thread+0x178/0x28c irq_thread from kthread+0x12c/0x138 kthread from ret_from_fork+0x14/0x28

How to fix

Remediation Available
linuxDebian
Fixed in:6.1.176-1CVE-2026-46031
Fixed in:6.12.86-1CVE-2026-46031
Fixed in:7.0.4-1CVE-2026-46031
linuxUbuntu
Fixed in:6.8.0-136.136USN-8567-1
linux-awsUbuntu
Fixed in:6.8.0-1061.64USN-8595-2
linux-aws-6.8Ubuntu
Fixed in:6.8.0-1061.64~22.04.1USN-8595-3
linux-aws-fipsUbuntu
Fixed in:6.8.0-1061.64+fips1USN-8595-3
linux-azureUbuntu
Fixed in:6.8.0-1063.71USN-8606-1
linux-azure-6.8Ubuntu
Fixed in:6.8.0-1063.71~22.04.1USN-8606-1
linux-azure-fdeUbuntu
Fixed in:6.8.0-1062.69USN-8607-1
linux-azure-fde-6.8Ubuntu
Fixed in:6.8.0-1062.69~22.04.1USN-8609-1
linux-azure-fipsUbuntu
Fixed in:6.8.0-1063.71+fips2USN-8608-1
linux-fipsUbuntu
Fixed in:6.8.0-136.136+fips2USN-8574-2
linux-gcpUbuntu
Fixed in:6.8.0-1064.72USN-8567-1
linux-gcp-6.8Ubuntu
Fixed in:6.8.0-1064.72~22.04.1USN-8567-1
linux-gcp-fipsUbuntu
Fixed in:6.8.0-1064.72+fips1USN-8574-1
linux-gkeUbuntu
Fixed in:6.8.0-1059.67USN-8567-1
linux-gkeopUbuntu
Fixed in:6.8.0-1046.50USN-8567-1
linux-hwe-6.8Ubuntu
Fixed in:6.8.0-136.136~22.04.1USN-8619-1
linux-hwe-7.0Ubuntu
Fixed in:7.0.0-28.28~24.04.1USN-8569-1
linux-ibmUbuntu
Fixed in:6.8.0-1061.62USN-8574-3
linux-ibm-6.8Ubuntu
Fixed in:6.8.0-1061.62~22.04.1USN-8574-3
linux-image-6.8.0-1030-nvidia-tegraUbuntu
Fixed in:6.8.0-1030.31USN-8574-3
linux-image-6.8.0-1030-nvidia-tegra-rtUbuntu
Fixed in:6.8.0-1030.31USN-8574-3
linux-image-6.8.0-1033-xilinxUbuntu
Fixed in:6.8.0-1033.34USN-8574-3
linux-image-6.8.0-1046-gkeopUbuntu
Fixed in:6.8.0-1046.50USN-8567-1
linux-image-6.8.0-1058-oracleUbuntu
Fixed in:6.8.0-1058.61~22.04.1USN-8595-1
Fixed in:6.8.0-1058.61USN-8574-2
linux-image-6.8.0-1058-oracle-64kUbuntu
Fixed in:6.8.0-1058.61~22.04.1USN-8595-1
Fixed in:6.8.0-1058.61USN-8574-2
linux-image-6.8.0-1059-gkeUbuntu
Fixed in:6.8.0-1059.67USN-8567-1
linux-image-6.8.0-1059-gke-64kUbuntu
Fixed in:6.8.0-1059.67USN-8567-1
linux-image-6.8.0-1059-nvidiaUbuntu
Fixed in:6.8.0-1059.62~22.04.1USN-8596-1
Fixed in:6.8.0-1059.62USN-8596-1
linux-image-6.8.0-1059-nvidia-64kUbuntu
Fixed in:6.8.0-1059.62~22.04.1USN-8596-1
Fixed in:6.8.0-1059.62USN-8596-1

This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

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

Exploit Intelligence

0.37%probability of exploitation in 30 days
30thpercentile

Low risk: more likely to be exploited than 30% of all known CVEs.

References

Related Vulnerabilities

Other CWE-667 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-10072High7.573%-Fix
CVE-2002-1850High7.517%-Fix
CVE-2009-2699High7.514%-Fix
CVE-2004-0174High7.512%--
CVE-2009-4272High7.511%--
CVE-2020-24606High8.65.2%-Fix

Common questions

How do I fix CVE-2026-46031?

Published advisories record a fix for 166 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.

Is CVE-2026-46031 being actively exploited?

Not that we know of. CVE-2026-46031 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.37% is the estimated probability that it will be exploited in the next 30 days. That is higher than 30% of all scored CVEs.

How severe is CVE-2026-46031?

CVE-2026-46031 has a CVSS v3 base score of 5.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-46031 affect?

Published advisories record a fix for linux (Debian), linux (Ubuntu), linux-aws (Ubuntu), linux-aws-6.8 (Ubuntu), and 162 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-46031
CVE-2026-46031 severity badge

Markdown

[![CVE-2026-46031](https://tridentstack.com/cve/badge/CVE-2026-46031.svg)](https://tridentstack.com/cve/CVE-2026-46031)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-46031"><img src="https://tridentstack.com/cve/badge/CVE-2026-46031.svg" alt="CVE-2026-46031"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-16.