CVE-2026-68456

UNRATEDCVSS · not yet scored
—
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:

usb: atm: ueagle-atm: wait for pre-firmware load in .disconnect()

ueagle-atm uses the asynchronous request_firmware_nowait() in .probe(), but does not wait for its completion, not even in .disconnect(); so, if the device is unplugged meanwhile, its teardown runs concurrently with that.

Even though this inconsistency is worth addressing on its own, it has also triggered several bug reports in syzbot over the years (some auto-closed) where the firmware sysfs fallback mechanism (CONFIG_FW_LOADER_USER_HELPER) creates a firmware subdirectory in the device directory during its removal, which might hit unexpected conditions in kernfs, apparently, depending at which point the add and remove operations raced. (See links.)

The pattern is:

usb ?-?: Direct firmware load for ueagle-atm/eagle?.fw failed with error -2 usb ?-?: Falling back to sysfs fallback for: ueagle-atm/eagle?.fw

Call trace: ... kernfs_create_dir_ns sysfs_create_dir_ns create_dir kobject_add_internal kobject_add_varg kobject_add class_dir_create_and_add get_device_parent device_add fw_load_sysfs_fallback fw_load_from_user_helper firmware_fallback_sysfs _request_firmware request_firmware_work_func ...

(Some variations are observed, after fw_load_sysfs_fallback(), e.g., [1].)

While the kernfs side is being looked at, the ueagle-atm side can be fixed by waiting for the pre-firmware load in the .disconnect() handler.

This change has a similar approach to previous work by Andrey Tsygunka [2] (wait_for_completion() in .disconnect()), but it is relatively different in design/implementation; using the Originally-by tag for credit assignment.

This has been tested with:

  • synthetic reproducer to check the error path;
  • USB gadget (virtual device) to check the firmware upload path;
  • QEMU device emulator to check the device ID re-enumeration path;
(The latter two were written by Claude; no other code/text in this commit.)

Links (year first reported): 2025 https://syzbot.org/bug?extid=ce1e5a1b4e086b43e56d 2025 https://syzbot.org/bug?extid=9af8471255ac36e34fd4 2024 https://syzbot.org/bug?extid=306212936b13e520679d 2023 https://syzkaller.appspot.com/bug?extid=457452d30bcdda75ead2 2022 https://syzbot.org/bug?extid=782984d6f1701b526edb 2021 https://syzbot.org/bug?id=f3f221579f4ef7e9691281f3c6f56c05f83e8490 2021 https://syzbot.org/bug?id=84d86f0d71394829df6fc53daf6642c045983881 2021 https://syzbot.org/bug?id=3302dc1c0e2b9c94f2e8edb404eabc9267bc6f90

[1] https://syzkaller.appspot.com/bug?extid=457452d30bcdda75ead2 [2] https://lore.kernel.org/lkml/[email protected]/

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.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 (model v2026.06.15, score date 2026-10-17). 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: 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.

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

August 15, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-68456(1)

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

Patch Availability(8)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 82 are merged into the row they repeat.

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

Frequently asked(4)

What is CVE-2026-68456?
CVE-2026-68456 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: atm: ueagle-atm: wait for pre-firmware load in .disconnect() ueagle-atm uses the asynchronous requestfirmwarenowait() in .probe(), but does not wait for its completion, not even in .disconnect(); so, if the device is unplugged…
When was the CVE record for CVE-2026-68456 published?
The CVE record for CVE-2026-68456 was published on August 15, 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 August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-68456 actively exploited?
CVE-2026-68456 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-68456?
A fix for CVE-2026-68456 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68456 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-68456

Explore →

Is Your Infrastructure Affected by CVE-2026-68456?

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