CVE-2026-99103

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-112003 (ENISA EUVD) · GHSA-qwjv-757x-9f99 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

workqueue: Fix unbound pool lifetime for pending pwqs

KASAN reports a use-after-free of an unbound worker_pool in node_activate_pending_pwq():

BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120 Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318

CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: 0x0 (flush-8:0) Call Trace: dump_stack_lvl+0x53/0x70 print_report+0xce/0x610 kasan_report+0xce/0x100 _raw_spin_trylock+0x6d/0x120 pwq_dec_nr_in_flight+0x4b4/0xcb0 process_one_work+0x921/0x11a0 worker_thread+0x4d0/0xd20 kthread+0x2de/0x3c0 ret_from_fork+0x3aa/0x620 ret_from_fork_asm+0x1a/0x30

Allocated by task 311: alloc_pwq+0x439/0xca0 apply_wqattrs_prepare+0x75e/0xd10 apply_workqueue_attrs_locked+0x44/0xa0 wq_nice_store+0x350/0x450

Freed by task 0: kfree+0x127/0x3b0 rcu_core+0x523/0x1780 handle_softirqs+0x1b3/0x610

Last potentially related work creation: put_unbound_pool+0x3f3/0x7d0 pwq_release_workfn+0x494/0x8e0 kthread_worker_fn+0x1ff/0x790

Canceling the last inactive work skips pwq_dec_nr_active(), so an empty pwq can remain on pending_pwqs when its refcnt reaches zero. pwq_release_workfn() currently puts the pool before removing that pwq. If this drops the last pool reference, the pool can be RCU-freed while the pwq remains reachable, and node_activate_pending_pwq() may trylock the freed pool->lock.

Remove the pwq from pending_pwqs before putting the pool.

CVSS
—
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.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

October 30, 2026

Vendor Advisories for CVE-2026-99103(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (192 versions)
  • every version up to 7.2.13-1: fixed in 7.2.13-1
—

Data Freshness Timeline

(refreshed 6× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-13 16:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-30 13:40 UTCGHSA enrichmentGHSA-qwjv-757x-9f99
  25. 2026-10-30 13:27 UTCNVD update
Show 8 more
  1. 2026-10-30 12:51 UTCEchelonGraph re-scored
  2. 2026-10-30 12:51 UTCGHSA enrichmentGHSA-qwjv-757x-9f99
  3. 2026-10-30 12:50 UTCMITRE cvelistV5
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-28 11:26 UTCNVD update
  6. 2026-10-28 11:01 UTCENISA EUVD ID recordedEUVD-2026-112003 · Source: ENISA EUVD
  7. 2026-10-28 10:48 UTCEchelonGraph re-scored
  8. 2026-10-28 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-99103?
CVE-2026-99103 is a vulnerability whose severity is not yet rated; its CVE record was published on October 28, 2026. In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a use-after-free of an unbound worker_pool in node_activate_pending_pwq(): BUG: KASAN: slab-use-after-free in _raw_spin_trylock+0x6d/0x120 Read of size 4 at addr…
When was the CVE record for CVE-2026-99103 published?
The CVE record for CVE-2026-99103 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-99103 actively exploited?
CVE-2026-99103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-99103?
A fix for CVE-2026-99103 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99103 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-99103?

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