CVE-2026-90041

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

HID: sony: clean up device list on probe failure

sony_input_configured() adds some controllers to sony_device_list before HID core registers their input devices. input_register_device() can fail after the callback returns successfully. sony_probe() then observes that HID_CLAIMED_INPUT is clear and unwinds, but only stops the HID hardware. The devres-managed sony_sc is freed while its list node remains linked, so the next matching controller traverses freed memory.

Initialize the list node and device ID to inactive states. Make list removal idempotent and run the driver-private cleanup on every probe failure path. This also makes a second cleanup safe when sony_input_configured() already unwound a partial initialization before sony_probe() handles the missing input claim.

Found by 0sec (https://0sec.ai) using automated source analysis; verified against the HID input registration and probe unwind paths.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 21, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

HID: sony: clean up device list on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c65699a3a311198a07659a614fe64d45924839e
generic

HID: sony: clean up device list on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d044d796e2a369c6051c7e83dce88c7baa2494d4
generic

HID: sony: clean up device list on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b4709e4864908bb06c48c500cc8db8d3d55d139

Vendor Advisories for CVE-2026-90041(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-10-05 05:03 UTCEG score recompute
  2. 2026-10-05 05:03 UTCVendor advisory
  3. 2026-10-05 05:03 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 16:39 UTCVendor advisory
  6. 2026-10-04 16:39 UTCGHSA enrichment
  7. 2026-10-04 04:16 UTCVendor advisory
  8. 2026-10-04 04:16 UTCGHSA enrichment
  9. 2026-10-03 15:52 UTCEG score recompute
  10. 2026-10-03 15:52 UTCVendor advisory
  11. 2026-10-03 15:52 UTCGHSA enrichment
  12. 2026-10-03 03:16 UTCEG score recompute
  13. 2026-10-03 03:16 UTCVendor advisory
  14. 2026-10-03 03:16 UTCGHSA enrichment
  15. 2026-10-02 14:53 UTCVendor advisory
  16. 2026-10-02 14:53 UTCGHSA enrichment
  17. 2026-10-02 02:29 UTCEG score recompute
  18. 2026-10-02 02:29 UTCVendor advisory
  19. 2026-10-02 02:29 UTCGHSA enrichment
  20. 2026-10-01 19:51 UTCEPSS rescore
  21. 2026-10-01 14:04 UTCVendor advisory
  22. 2026-10-01 14:04 UTCGHSA enrichment
  23. 2026-10-01 01:41 UTCEG score recompute
  24. 2026-10-01 01:41 UTCVendor advisory
  25. 2026-10-01 01:41 UTCGHSA enrichment
Show 75 more
  1. 2026-09-30 15:04 UTCEPSS rescore
  2. 2026-09-30 13:17 UTCVendor advisory
  3. 2026-09-30 13:17 UTCGHSA enrichment
  4. 2026-09-30 00:54 UTCEG score recompute
  5. 2026-09-30 00:54 UTCVendor advisory
  6. 2026-09-30 00:54 UTCGHSA enrichment
  7. 2026-09-29 09:16 UTCEG score recompute
  8. 2026-09-29 09:16 UTCVendor advisory
  9. 2026-09-29 09:16 UTCGHSA enrichment
  10. 2026-09-28 20:52 UTCEG score recompute
  11. 2026-09-28 20:52 UTCVendor advisory
  12. 2026-09-28 20:52 UTCGHSA enrichment
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 08:28 UTCVendor advisory
  16. 2026-09-28 08:28 UTCGHSA enrichment
  17. 2026-09-27 20:05 UTCEG score recompute
  18. 2026-09-27 20:05 UTCVendor advisory
  19. 2026-09-27 20:05 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 07:40 UTCVendor advisory
  22. 2026-09-27 07:40 UTCGHSA enrichment
  23. 2026-09-26 19:16 UTCEG score recompute
  24. 2026-09-26 19:16 UTCVendor advisory
  25. 2026-09-26 19:16 UTCGHSA enrichment
  26. 2026-09-26 15:59 UTCEPSS rescore
  27. 2026-09-26 06:52 UTCEG score recompute
  28. 2026-09-26 06:52 UTCVendor advisory
  29. 2026-09-26 06:52 UTCGHSA enrichment
  30. 2026-09-25 18:24 UTCVendor advisory
  31. 2026-09-25 18:24 UTCGHSA enrichment
  32. 2026-09-25 05:06 UTCVendor advisory
  33. 2026-09-25 05:06 UTCGHSA enrichment
  34. 2026-09-24 16:42 UTCEG score recompute
  35. 2026-09-24 16:42 UTCVendor advisory
  36. 2026-09-24 16:42 UTCGHSA enrichment
  37. 2026-09-24 14:04 UTCEPSS rescore
  38. 2026-09-24 04:19 UTCEG score recompute
  39. 2026-09-24 04:19 UTCVendor advisory
  40. 2026-09-24 04:19 UTCGHSA enrichment
  41. 2026-09-23 17:54 UTCEPSS rescore
  42. 2026-09-23 15:55 UTCVendor advisory
  43. 2026-09-23 15:55 UTCGHSA enrichment
  44. 2026-09-23 03:32 UTCEG score recompute
  45. 2026-09-23 03:32 UTCVendor advisory
  46. 2026-09-23 03:32 UTCGHSA enrichment
  47. 2026-09-22 16:01 UTCEPSS rescore
  48. 2026-09-22 15:08 UTCVendor advisory
  49. 2026-09-22 15:08 UTCGHSA enrichment
  50. 2026-09-22 02:44 UTCEG score recompute
  51. 2026-09-22 02:44 UTCVendor advisory
  52. 2026-09-22 02:44 UTCGHSA enrichment
  53. 2026-09-21 21:09 UTCEPSS rescore
  54. 2026-09-21 14:20 UTCEG score recompute
  55. 2026-09-21 14:20 UTCVendor advisory
  56. 2026-09-21 14:20 UTCGHSA enrichment
  57. 2026-09-21 13:20 UTCEG score recompute
  58. 2026-09-21 13:20 UTCVendor advisory
  59. 2026-09-21 13:20 UTCGHSA enrichment
  60. 2026-09-21 06:53 UTCEG score recompute
  61. 2026-09-21 06:53 UTCVendor advisory
  62. 2026-09-21 06:53 UTCGHSA enrichment
  63. 2026-09-20 20:16 UTCEPSS rescore
  64. 2026-09-20 18:29 UTCVendor advisory
  65. 2026-09-20 18:29 UTCGHSA enrichment
  66. 2026-09-20 06:06 UTCVendor advisory
  67. 2026-09-20 06:06 UTCGHSA enrichment
  68. 2026-09-19 17:42 UTCEG score recompute
  69. 2026-09-19 17:42 UTCVendor advisory
  70. 2026-09-19 17:42 UTCGHSA enrichment
  71. 2026-09-19 05:18 UTCEG score recompute
  72. 2026-09-19 05:18 UTCVendor advisory
  73. 2026-09-19 05:18 UTCGHSA enrichment
  74. 2026-09-18 19:28 UTCEPSS rescore
  75. 2026-09-18 16:55 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-90041?
CVE-2026-90041 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: sony: clean up device list on probe failure sonyinputconfigured() adds some controllers to sonydevicelist before HID core registers their input devices. inputregisterdevice() can fail after the callback returns successfully.…
When was CVE-2026-90041 disclosed?
CVE-2026-90041 was first published on September 16, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90041 actively exploited?
CVE-2026-90041 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90041?
CVE-2026-90041 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90041?
No fix for CVE-2026-90041 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90041 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-90041

Explore →

Is Your Infrastructure Affected by CVE-2026-90041?

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

Book a Demo →Browse All CVEs