CVE-2026-63988

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

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:

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)

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 30, 2026

Vendor Advisories for CVE-2026-63988(1)

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

Patch Availability(5)

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:42 UTCEPSS rescore
  3. 2026-08-27 22:25 UTCVendor advisory
  4. 2026-08-27 22:25 UTCGHSA enrichment
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-24 19:09 UTCVendor advisory
  9. 2026-08-24 19:09 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 14:39 UTCVendor advisory
  13. 2026-08-21 14:39 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-18 11:21 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-15 08:03 UTCVendor advisory
  21. 2026-08-15 08:03 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-12 04:46 UTCVendor advisory
Show 49 more
  1. 2026-08-12 04:46 UTCGHSA enrichment
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-09 13:47 UTCEPSS rescore
  4. 2026-08-09 01:30 UTCVendor advisory
  5. 2026-08-09 01:30 UTCGHSA enrichment
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-05 22:13 UTCVendor advisory
  9. 2026-08-05 22:13 UTCGHSA enrichment
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 10:39 UTCEPSS rescore
  14. 2026-08-03 10:36 UTCEPSS rescore
  15. 2026-08-02 18:57 UTCVendor advisory
  16. 2026-08-02 18:57 UTCGHSA enrichment
  17. 2026-08-02 02:27 UTCEPSS rescore
  18. 2026-08-01 04:16 UTCEPSS rescore
  19. 2026-07-30 16:28 UTCEPSS rescore
  20. 2026-07-30 15:40 UTCEG score recompute
  21. 2026-07-30 15:40 UTCVendor advisory
  22. 2026-07-30 15:40 UTCGHSA enrichment
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-29 14:14 UTCGHSA enrichment
  26. 2026-07-28 15:37 UTCEPSS rescore
  27. 2026-07-27 14:14 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 10:57 UTCEG score recompute
  31. 2026-07-26 10:57 UTCVendor advisory
  32. 2026-07-26 10:57 UTCGHSA enrichment
  33. 2026-07-25 14:18 UTCEPSS rescore
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-24 14:18 UTCEPSS rescore
  36. 2026-07-24 14:18 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 03:22 UTCEG score recompute
  40. 2026-07-22 14:08 UTCEPSS rescore
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-21 15:25 UTCEPSS rescore
  43. 2026-07-21 15:25 UTCEPSS rescore
  44. 2026-07-20 17:29 UTCEG score recompute
  45. 2026-07-20 17:29 UTCGHSA enrichment
  46. 2026-07-20 17:08 UTCEPSS rescore
  47. 2026-07-19 17:49 UTCNVD update
  48. 2026-07-19 15:21 UTCEG score recompute
  49. 2026-07-19 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63988?
CVE-2026-63988 is a publicly disclosed vulnerability published on July 19, 2026. 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…
When was CVE-2026-63988 disclosed?
CVE-2026-63988 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63988 actively exploited?
CVE-2026-63988 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
How do I remediate CVE-2026-63988?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63988, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63988

Explore →

Is Your Infrastructure Affected by CVE-2026-63988?

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