CVE-2026-46031

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
29.2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (6)

Auto-updated Jun 5, 2026
No patch confirmed yet.
generic

net: ks8851: Reinstate disabling of BHs around IRQ handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be8aad558b4675f45b43080f81a9ffdeddea73a5
generic

net: ks8851: Reinstate disabling of BHs around IRQ handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/640a7631d31db87d5fa1b34cea44a99b6e78854b
generic

net: ks8851: Reinstate disabling of BHs around IRQ handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c9fcac3c872224316714d0d8914d9af16c76a6d
generic

net: ks8851: Reinstate disabling of BHs around IRQ handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/518040324067d8efaa2da1992297b7e7bf5640f4
generic

net: ks8851: Reinstate disabling of BHs around IRQ handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21f1707a8e978558dcb11b053855521e32ac0eec
generic

net: ks8851: Reinstate disabling of BHs around IRQ handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1962027a6d223f90df8b372929f9d1a8d321ad6a

Vendor Advisories for CVE-2026-46031(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 78× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 23:49 UTCEG score recompute
  7. 2026-07-11 23:49 UTCVendor advisory
  8. 2026-07-11 23:49 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 23:58 UTCEG score recompute
  12. 2026-07-08 23:58 UTCVendor advisory
  13. 2026-07-08 23:58 UTCGHSA enrichment
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 10:18 UTCEG score recompute
  22. 2026-07-01 10:18 UTCVendor advisory
  23. 2026-07-01 10:18 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 03:24 UTCEG score recompute
Show 75 more
  1. 2026-06-30 03:24 UTCVendor advisory
  2. 2026-06-30 03:23 UTCGHSA enrichment
  3. 2026-06-29 14:21 UTCEG score recompute
  4. 2026-06-29 14:21 UTCVendor advisory
  5. 2026-06-29 14:21 UTCGHSA enrichment
  6. 2026-06-28 20:59 UTCEG score recompute
  7. 2026-06-28 20:59 UTCVendor advisory
  8. 2026-06-28 20:58 UTCGHSA enrichment
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 06:44 UTCEG score recompute
  11. 2026-06-28 06:44 UTCVendor advisory
  12. 2026-06-28 06:44 UTCGHSA enrichment
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 18:30 UTCEG score recompute
  16. 2026-06-27 18:30 UTCVendor advisory
  17. 2026-06-27 18:30 UTCGHSA enrichment
  18. 2026-06-27 05:59 UTCEG score recompute
  19. 2026-06-27 05:59 UTCVendor advisory
  20. 2026-06-27 05:59 UTCGHSA enrichment
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 17:08 UTCEG score recompute
  23. 2026-06-26 17:08 UTCVendor advisory
  24. 2026-06-26 17:08 UTCGHSA enrichment
  25. 2026-06-26 02:32 UTCEG score recompute
  26. 2026-06-26 02:32 UTCVendor advisory
  27. 2026-06-26 02:32 UTCGHSA enrichment
  28. 2026-06-25 13:49 UTCEPSS rescore
  29. 2026-06-25 13:32 UTCEG score recompute
  30. 2026-06-25 13:32 UTCVendor advisory
  31. 2026-06-25 13:32 UTCGHSA enrichment
  32. 2026-06-25 01:17 UTCEG score recompute
  33. 2026-06-25 01:17 UTCVendor advisory
  34. 2026-06-25 01:17 UTCGHSA enrichment
  35. 2026-06-24 14:05 UTCEPSS rescore
  36. 2026-06-23 21:33 UTCEPSS rescore
  37. 2026-06-23 21:33 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 14:56 UTCEPSS rescore
  42. 2026-06-21 01:59 UTCEPSS rescore
  43. 2026-06-21 01:59 UTCEPSS rescore
  44. 2026-06-19 19:26 UTCEPSS rescore
  45. 2026-06-19 19:26 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-18 17:52 UTCEPSS rescore
  48. 2026-06-17 18:43 UTCEG score recompute
  49. 2026-06-17 18:43 UTCGHSA enrichment
  50. 2026-06-17 17:53 UTCEPSS rescore
  51. 2026-06-17 04:21 UTCEG score recompute
  52. 2026-06-17 04:21 UTCGHSA enrichment
  53. 2026-06-16 17:52 UTCEPSS rescore
  54. 2026-06-16 16:07 UTCEG score recompute
  55. 2026-06-16 16:07 UTCVendor advisory
  56. 2026-06-16 16:07 UTCGHSA enrichment
  57. 2026-06-16 01:50 UTCEG score recompute
  58. 2026-06-16 01:50 UTCVendor advisory
  59. 2026-06-16 01:50 UTCGHSA enrichment
  60. 2026-06-15 17:49 UTCEPSS rescore
  61. 2026-06-15 13:31 UTCEG score recompute
  62. 2026-06-15 13:31 UTCVendor advisory
  63. 2026-06-15 13:31 UTCGHSA enrichment
  64. 2026-06-14 21:55 UTCEG score recompute
  65. 2026-06-14 21:55 UTCVendor advisory
  66. 2026-06-14 21:55 UTCGHSA enrichment
  67. 2026-06-14 09:41 UTCEG score recompute
  68. 2026-06-14 09:41 UTCVendor advisory
  69. 2026-06-14 09:41 UTCGHSA enrichment
  70. 2026-06-13 23:00 UTCEPSS rescore
  71. 2026-06-13 21:24 UTCEG score recompute
  72. 2026-06-13 21:24 UTCGHSA enrichment
  73. 2026-06-13 09:08 UTCEG score recompute
  74. 2026-06-13 09:08 UTCVendor advisory
  75. 2026-06-13 09:08 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46031?
CVE-2026-46031 is a high vulnerability published on May 27, 2026. 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 netifwakequeue() which schedules TX softirq to queue packets for…
When was CVE-2026-46031 disclosed?
CVE-2026-46031 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46031 actively exploited?
CVE-2026-46031 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46031?
CVE-2026-46031 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46031?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46031, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46031

Explore →

Is Your Infrastructure Affected by CVE-2026-46031?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.