CVE-2026-99134

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-111886 (ENISA EUVD) · GHSA-jx9p-6hjg-j64x (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:

mac802154: fix data race and NULL deref on local->assoc_dev

local->assoc_dev is shared between the association path and the association-response worker without common synchronization.

mac802154_perform_association() stores the coordinator pointer and waits for a response. Its timeout and error paths clear the pointer and return to mac802154_associate(), which may then free the coordinator object. Meanwhile, mac802154_rx_mac_cmd_worker() may observe the associating bit and enter mac802154_process_association_resp(), which dereferences assoc_dev.

The worker's bit test and the handler's pointer dereference are not atomic with respect to cleanup. Cleanup can clear assoc_dev between them, causing a NULL dereference, or free the coordinator while the response handler still uses the pointer.

The recorded result is exposed to the same window. assoc_status and assoc_addr are written by the handler but read by the association path while the associating bit is still set, so a second response for the same request - a malicious one, for instance - can replace them between those reads and leave the caller with an incoherent status and address pair.

The response handler only needs the coordinator extended address. Replace assoc_dev with a cached address, removing the pointer lifetime dependency. Protect the cached address and the associating bit with a dedicated spinlock. A READ_ONCE()/WRITE_ONCE() pair would not guarantee an atomic __le64 access on all 32-bit architectures.

wpan_dev->association_lock cannot be reused here: nl802154_associate() holds it across rdev_associate(), hence for the whole of mac802154_perform_association() including the wait for the response. A response handler taking that lock would only get it once the association has already given up.

Reset the completion, publish the cached address, and set the associating bit while holding the lock. The response handler takes the lock, rechecks the bit and the cached address, records the response, clears the bit, and only then completes the waiter. Thus cleanup cannot pass the handler between its state check and completion, and the cached 64-bit value cannot tear.

The handler clears the bit before completing, not the woken waiter: otherwise complete() is issued under the lock and a second (e.g. malicious) response can reacquire it before the waiter and replace the result. So a wait that returns success implies the bit is already clear, and the success and negative-response paths return directly. The transmit-error and timeout paths still clear it under assoc_lock, which serializes any racing response against the cleanup while the call returns the error it already selected. Both paths snapshot assoc_status and assoc_addr under the same lock.

Both users run in process context, so a plain spinlock is sufficient. The lock is not held while waiting for the completion.

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
9th
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-99134(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% · 9th 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% · 5th percentile
  24. 2026-10-30 13:42 UTCGHSA enrichmentGHSA-jx9p-6hjg-j64x
  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-jx9p-6hjg-j64x
  3. 2026-10-30 12:50 UTCMITRE cvelistV5
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-28 11:26 UTCNVD update
  6. 2026-10-28 11:01 UTCENISA EUVD ID recordedEUVD-2026-111886 · Source: ENISA EUVD
  7. 2026-10-28 10:47 UTCEchelonGraph re-scored
  8. 2026-10-28 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-99134?
CVE-2026-99134 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: mac802154: fix data race and NULL deref on local->assoc_dev local->assoc_dev is shared between the association path and the association-response worker without common synchronization. mac802154_perform_association() stores the…
When was the CVE record for CVE-2026-99134 published?
The CVE record for CVE-2026-99134 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-99134 actively exploited?
CVE-2026-99134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-99134?
A fix for CVE-2026-99134 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99134 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-99134

Explore →

Is Your Infrastructure Affected by CVE-2026-99134?

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