CVE & CISA-KEV Catalog

CVE-2026-63988

MEDIUM
5.5
CVSS v3
NVD

Description

In the Linux kernel, the following vulnerability has been resolved: bridge: Fix sleep in atomic context in sysfs path Since the start of the git history, brport_store() always acquired the bridge lock. Back then this decision made sense: The bridge lock protects the STP state of the bridge and its ports and at that time the function was only used by two STP related attributes (cost and priority). Nowadays, brport_store() processes a lot more attributes and most of them do not need the bridge lock: * Bridge flags: Only require RTNL. Read locklessly by the data path. Annotations can be added in net-next. * FDB port flushing: Only requires the FDB lock. * Multicast attributes: Only require the multicast lock. * Group forward mask: Only requires RTNL. Read locklessly by the data path. Annotations can be added in net-next. * Backup port: Only requires RTNL. Read locklessly by the data path. This is a problem as the bridge calls dev_set_promiscuity() when certain bridge port flags change and this function can sleep since the commit cited below, resulting in a splat such as [1]. Fix this by reducing the scope of the bridge lock and only take it when processing the two STP related attributes that require it. Remove the now stale comment from br_switchdev_set_port_flag(). The SWITCHDEV_F_DEFER flag can be removed in net-next. [1] BUG: sleeping function called from invalid context at net/core/dev_addr_lists.c:1262 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 372, name: bash preempt_count: 201, expected: 0 RCU nest depth: 0, expected: 0 5 locks held by bash/372: #0: ffff88810c51c3f0 (sb_writers#7){.+.+}-{0:0}, at: ksys_write (fs/read_write.c:740) #1: ffff888115ce9480 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter (fs/kernfs/file.c:343) #2: ffff88810b9fd330 (kn->active#37){.+.+}-{0:0}, at: kernfs_fop_write_iter (fs/kernfs/file.c:80 fs/kernfs/file.c:344) #3: ffffffffa59473a0 (rtnl_mutex){+.+.}-{4:4}, at: brport_store (net/bridge/br_sysfs_if.c:326) #4: ffff8881099d2d58 (&br->lock){+...}-{3:3}, at: brport_store (./include/linux/spinlock.h:348 net/bridge/br_sysfs_if.c:345) Preemption disabled at: 0x0 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) __might_resched.cold (kernel/sched/core.c:9163) netif_rx_mode_run (net/core/dev_addr_lists.c:1262) netif_rx_mode_sync (net/core/dev_addr_lists.c:1428) dev_set_promiscuity (net/core/dev_api.c:289) br_manage_promisc (net/bridge/br_if.c:135 net/bridge/br_if.c:172) br_port_flags_change (net/bridge/br_if.c:242 net/bridge/br_if.c:747) store_learning (net/bridge/br_sysfs_if.c:79 net/bridge/br_sysfs_if.c:235) brport_store (net/bridge/br_sysfs_if.c:346) kernfs_fop_write_iter (fs/kernfs/file.c:352) new_sync_write (fs/read_write.c:595) vfs_write (fs/read_write.c:688) ksys_write (fs/read_write.c:740) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)

How to fix

Remediation Available
linuxDebian
Fixed in:7.0.12-1CVE-2026-63988
linux-azure-7.0Ubuntu
Fixed in:7.0.0-1014.14~24.04.1USN-8728-2
linux-gcp-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-7.0.0-1011-gcpUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-7.0.0-1011-gcp-64kUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-7.0.0-1011-oracleUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3
linux-image-7.0.0-1011-oracle-64kUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3
linux-image-7.0.0-1014-azureUbuntu
Fixed in:7.0.0-1014.14~24.04.1USN-8728-2
linux-image-7.0.0-1016-nvidiaUbuntu
Fixed in:7.0.0-1016.16~24.04.1USN-8663-1
linux-image-7.0.0-1016-nvidia-64kUbuntu
Fixed in:7.0.0-1016.16~24.04.1USN-8663-1
linux-image-azureUbuntu
Fixed in:7.0.0-1014.14~24.04.1USN-8728-2
linux-image-azure-7.0Ubuntu
Fixed in:7.0.0-1014.14~24.04.1USN-8728-2
linux-image-gcpUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-gcp-64kUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-gcp-64k-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-gcp-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-1
linux-image-nvidia-64k-7.0Ubuntu
Fixed in:7.0.0-1016.16~24.04.1USN-8663-1
linux-image-nvidia-7.0Ubuntu
Fixed in:7.0.0-1016.16~24.04.1USN-8663-1
linux-image-oracleUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3
linux-image-oracle-64kUbuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3
linux-image-oracle-64k-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3
linux-image-oracle-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3
linux-nvidia-7.0Ubuntu
Fixed in:7.0.0-1016.16~24.04.1USN-8663-1
linux-oracle-7.0Ubuntu
Fixed in:7.0.0-1011.11~24.04.1USN-8728-3

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.12%probability of exploitation in 30 days
2ndpercentile

Low risk: more likely to be exploited than 2% 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.0%-Fix

Common questions

How do I fix CVE-2026-63988?

Published advisories record a fix for 24 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-63988 being actively exploited?

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

How severe is CVE-2026-63988?

CVE-2026-63988 has a CVSS v3 base score of 5.5, rated medium. 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-63988 affect?

Published advisories record a fix for linux (Debian), linux-azure-7.0 (Ubuntu), linux-gcp-7.0 (Ubuntu), linux-image-7.0.0-1011-gcp (Ubuntu), and 20 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-63988
CVE-2026-63988 severity badge

Markdown

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

HTML

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

Check your Linux endpoints for this class of vulnerability

TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.

Patch your fleet freeStart 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-10-08.